yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] savethechicken:
All I did was flash the SPL then Home + Back and then it went back into recovery then I went into console changed my JF1.5 to update.zip exited console.

back to recovery and ALT + S

then when done Home + Back and it rebooted without any trouble I didn't have to pull the battery at all.

Might want to try this.

D/L SPL Name update.zip (also make sure you have the ROM on your Sd)

Boot into recovery

ALT + S when states it is done

ALT + Home (it will reboot into recovery)

Then ALT + X

press Enter

type

mount sdcard
cd sdcard

rename/delete you update.zip file to spll.zip

mv udpate.zip spl.zip

Now Rename your ROM to update.zip same as above just reverse.

type recovery to exit console.

ALT + S

then when done

HOME + BACK

Not liable for anyone not doing this correctly but this is how I did it and it worked fine and this way you dont have to worry about pulling battery prematurely.

-----------------------------------------------

Also for the people that continue to tell the people that have bricked their phones to just flash their ROMS. read the post the two that have seen are NOT getting the option to go back into recovery. They ARE NOT able to hold home + Power to get it to boot into recovery this is becuase some how their Bootloader (SPL) has not been properly installed. Thus they are not able to BOOT into recovery. Unless you have bricked yours in the same manor (not being able to boot into recovery or even Bootloader) and have fixed it. Then dont keep telling them to do the samething. They have already tried it!
[G1 Android Development] paulobrien:
Clicker.apk anyone?

P
[G1 Android Development] djdeviance:
Weird. I'm at work. Renamed spl to update.zip via Linda File Manager. Flashed. Borrowed our demo G1 here at the store. Stuck my sd card in and renamed dude1.1a to update.zip. Put sd back into my phone flashed. Then flashed Prod Sun Theme and all worked fine. =D
[G1 Android Development] paulobrien:
In bootloader, my dream was version 'DREA100 DVT2-1 32B'.

I wonder if this board version is the problem? (suggested by a friend).

Perhaps check before you flash?

P
[G1 Android Development] jonnybueno:
Crazy... I wonder if that rules out bad file integrity as the culprit??? sha1 checks out on both computer as welll as sd card. Could you give us more details about the setup you were using before the brick? What build? A2SD? which A2sd method did you use? Dalvik moved? /data/data moved? Which JF recovery version: 1.41,1.42 or 1.43?

Side thought: Wow Haykuro really is a magician! :D ( here's a jk for all you fanboys) look at the g1's that have disappeared! Glad I waited to see if there were any negatives to using new SPL before applying to the other two phones here.
[G1 Android Development] ei8htohms:
here ya go

filler...filler...
[G1 Android Development] sir*mez:
on both phones I was using jf 1.5 lucid mod. I moved apps and dalvik to the ext2 partition. But funny thing is I did the same thing with both phones. One bricked and one flashed perfectly. So I don't know what went wrong. I did it on 2 phones with everything exaclty the same.
[G1 Android Development] shadowleo85:
ive been flashing roms and updates for like 2 years now... i downloaded the new spl... and updated my g1... it reset once and hangs... and now it is bricked... i have tried to put it in bootloader and recovery mode nothing seems to work... any ideas... no matter what keys i press it just sits at the tmobile screen
[G1 Android Development] free-sidux:
so where is the reason for the bricked phones????
[G1 Android Development] shadowleo85:
i am in the same boat as u... i flashed 2 phones succesful and 1 bricked... and i cannot figure out y... all phones were using the kaykuro hbuild 5.0 and and 2 flashed successfully the third just hangs at the tmobile screen and wont go into bootloader or recovery
[G1 Android Development] osho741:
If you read the rest of this thread you would of noticed about 3 other people with this problem. If your no longer able to boot into recovery or bootloader mode, you now have a bricked phone and there is npthing else that can be done, unless you can still acess the internal memory from adb, not sure if anyone tried that yet. I've heard that you can still ge into internal memory from adb even if its looping. Not sure about this situation though
[G1 Android Development] shadowleo85:
thats what we r trying to find out... because everything on mine worked perfectly for 2 but not the third and they were all identical
[G1 Android Development] shadowleo85:
ummm ok thx
[G1 Android Development] osho741:
I'm sure that was of no help lol. Has anyone tried to push a build into a looping phone with this spl from adb? And did it work? Also, if you can still get to the phone from adb, maybe you can post a log so people can see what's actually happening when the phone is booting.
[G1 Android Development] shadowleo85:
none at all ... i just plugged my phone into my comp and the comp doesnt even recognize it... this sucks... but it is odd that it flashed succesfully on 2 phones and not the third... luckily i know someone in tmo and ill do an in store exchange
[G1 Android Development] cidica:
Just did this on my phone without 1 single hitch. now sitting at a nice 87 meg free and running JFadp1.5 (Lucidmod version) and so far so good :)
[G1 Android Development] sir*mez:
This has already been establish... I don't see why people keep saying the same thing. "This phone can not be bricked." Well it just so happens that it can be. There's no access to anything. No boot, no recovery and no fastboot for adp. So if the brick happens call t-mo like I did and ask for a new one or if you don't have warrenty then your f'ed cause you have to buy a new one!! Then you can use the bricked one as a paper weight...
[G1 Android Development] osho741:
Id be really pissed off if it was me, sorry so many of you have bricks now. Maybe haykuro will read up on this thread and look into it. Not that it does anyone with a bricked phone any good though.
[G1 Android Development] pitecus:
sir*mez, I do have same problem as you

My G1 only can do displaying stupid G1 image. I have exactly same issue as you.

Anybody can help us? How can I escape from this situation?
[G1 Android Development] sir*mez:
I'm not that pissed cause it didn't brick my phone, it bricked my girls phone. My phone doesn't have warrenty and after bricking my girls phone I went and did it to my phone so if the same would of happened to my phone i'd be f'ed
[G1 Android Development] ei8htohms:
have all of you "brick" owners tried it without the SD card?

It's possible the process damaged the SD card in some way. I had a problem with a bad card awhile back and the phone would simply not operate with the bad card installed, but would boot up fine once the SD card was removed. Try rebooting without the SD card installed and see if you get anything different. Just thinking out loud, but worth a shot...
[G1 Android Development] sir*mez:
Been there, done that... aftermath: still bricked.
[G1 Android Development] wiked1r:
i was having the same problem that the g1 image was just hanging i just kept takin the battery off and try to power up holding power + home and after the 3rd try i was able to flash jf 1.5 and it was able to boot up normally just slow first time like usual
[G1 Android Development] justanothercrowd:
Ok folks...this phone can be bricked. It's easy to brick actually when you are flashing something as important as the SPL.

If you flash a corrupt SPL you are basically F!@#!D.
[G1 Android Development] g2crx:
can some one post a screen shoot of the slp.this is what i have.

DREA100 pvt 32B

HSLP10.95.3000

cpld-4

RADIO-1.22.12.29

OCT 20 2008

thanx

james
[G1 Android Development] shadowleo85:
thats just it... the spl cant be corrupt if it flashed succesfully onto 2 other phones and just not the third...
[G1 Android Development] andrews240:
deeeeee-de-de-deeeeee-deeeeee
[G1 Android Development] sir*mez:
Getting off subject: nice hatch you got there and nice turbo.

Getting back on subject: I'm gonna keep playing with it and see what happens.
[G1 Android Development] g2crx:
NVM didnt notice some one posted already on pg2.well i guess i dont hav eit and is scared to install it.maybe dude will include it on his next update.

@sir*mez Thank You.lol it's a little to big but oh well ;)
[G1 Android Development] osho741:
This is just another wild theory, maybe htc changed something in the g1s they are building now? Of the phones that are bricked, when were they purchased maybe there was a change in hardware/drivers in the last month or so, or something like that?
[G1 Android Development] cidica:
I got my g1 the day it was released (Black version) I'm not bricked and I've already got my phone up and running with this new spl. So do not believe that's the cause.
[G1 Android Development] serialtoon:
I reverted back to the Sapphire SPL cause i dont wanna brick my phone.
[G1 Android Development] sir*mez:
Phone was bought on feb. 14, 2009. Its the white g1. Plus it shouldn't matter. We rooted it and flashed a new system. I had a jf 1.5 and someone else had a h 1.5 and we are both bricked..
[G1 Android Development] Manacit:
Holy crap, it looks like I was really lucky. I didn't think any of it when I flashed my phone, nobody on haykuro's site said their phone got bricked, only that they needed to reflash whatever OS and possibly wipe. I didn't even need to wipe, and my phone works fine :$

Really sucks for everybody who got their phone bricked.

I bought my phone last October right when they were first coming out, if it matters.
[G1 Android Development] alapapa:
you could have slightly different hardware in that phone than launch devices...that's the point the other person was trying to make, i believe

EDIT: Mine is a launch device and i was able to apply this SPL w/o issue
[General Questions and Answers] DomSim:
I would like to know if there is a way to use the new slide to answer built into 6.5 WITHOUT having to lock the phone with the built in locking app? I use touchlockpro for locking and prefer to keep this. I can install the s2a apps for the touch pro from the new manila version but this effects the call log though. Anyone figure out a way to do this yet?
[General Questions and Answers] DomSim:
bump for an answer
[General Questions and Answers] Aegishua:
There isn't a way to do that as of yet but im sure if you made a [REQ] thread in the development and hacking section someone might find a solution because this is a very viable option and wouldnt be such a bad idea considering how good the WM6.5 S2A looks but having you're phone locked 24/7 isnt all that great.
[Touch HD Windows Mobile ROM Development] sparkienl:
It is the visual multilang kitchen based on last bepe's tools to build a rom made by Ervius , the other is made by vistang.

The Erviuskitchen is build version 1.82 (with "True" or "False" in color)

Look here *Ervius kitchen _____ for the last Erv.build.

Look here *Vistang kitchen _____ for vistang build

When U use the Kitchen think about this, Debugging and Tweaking you must do how U like it.

Kitchen here: PASSWORD FOR ALL : sparkienl

Ervius kitchen SYS 21056 _____ Ervius kitchen with WM 6.1 SYS 21056

WWE_WVGA_Huashan_EXT_OEMS.7z Read the .txt file

LEO_2.11_External_Packages Leo_1_5_TMOUS_2.11.531.T1_EXT_PACKS

LEO_2.09_External_Packages

DIY-_HD_WM6.5_25001_Kitchen _____ Vistang Kitchen with SYS 25001

Ervius kitchen 21892 _____ Update SYS 21892 and Swype

OS kitchen 23529 _____ Updated Sys 23529 and Manila_Core_2_5_20113030_0

OS kitchen 28205 _____ updated Sys 28205

New Manila _____ Ext packs with Telstra Manila_Core_2_5_20121431_1

New Topaz 2.53 packs _____ Topaz packs out 2.53 different than 2.54

New Manila _____ Ext packs with Manila_Core_2_5_20113030_0

All_New SYS_16 _____ New Sys 22013/21651

Manila Packs _____ Some old Manila packages 2.5

If you want to dump an "unprotected" rom of your choice, put it in the folder/Tools/RomSaved/Ruu_signed.nbh

Click in the visual kitchen under left on the field "Dump nbh/nb/payload", there will be made a new folder in

/Tools/RomSaved/dump with the extracted rom of your choice in it.

Now use the content of this folder as the base of your new kitchen.

I'm a "USER" myself so don't think I can solve all your problems.

I started this kitchen thread to help everybody to build their own rom for the BlackStone.

The blackstone kernel can't handle many modules in the native kernel.

The WM 6.5 native kernel is patched for use with the BlackStone.

Now use the content of this folder as the base of your new kitchen.

Don't use spaces in your kitchen folder name like this "c:\My Kitchen" but use it like this "c:\My_Kitchen".

Don't blame me as you brick your device, you are using this tool at your own risk.

Don't thank me, say thank you to Bepe, Ervius, Da_G and "ALL WHO SHARES" for there nice work
[Touch HD Windows Mobile ROM Development] vjsxda:
thanks man will u update kitchen with new build and OEM:)
[Touch HD Windows Mobile ROM Development] Davidsy:
could some one give a guideline how to cooking from this kitchen ? tks
[Touch HD Windows Mobile ROM Development] sparkienl:
Follow the step by step guide and you are able to build your own rom:D
[Touch HD Windows Mobile ROM Development] be_vigilant:
Hello and many thanks for posting this!

Just built a test rom using this kitchen. Not changed anything.

My rom boots fine and looks good and is nice and fast. But the SD card is not listed in file manager. It seems to be missing from the system all together.

Any idea?

Thanks
[Touch HD Windows Mobile ROM Development] vjsxda:
the kitchens oem seems to be messy when trying to make clean rom i get extra files like BBC player autovolume pls try to clean kitchen :)
[Touch HD Windows Mobile ROM Development] sparkienl:
I connected through active sync and can reach the SD card on my device,

I dumped and extrcted rom 156 wwe in the kitchen and then added the sys and xip from 21232 and 21232 to it .

So all the drivers and so on should be in the kitchen, and I didn't take anything out.
[Touch HD Windows Mobile ROM Development] sparkienl:
@vjsxda

The dump is from 156 rom and the xip and sys are 21231 and 21232 nothing more in it.

Load rom "premium.erv" and then double click on "true" in the first row, the whole way down and enable or disable anything you want to build your own rom.

Save rom under any name you like for futer use.
[Touch HD Windows Mobile ROM Development] be_vigilant:
not sure whats going on then! I ripped a standard 1.57 rom into it and built that and my SD shows up. Yet when I build it from the kitchen you posted I get no SD card.

No idea whats going wrong! I will try extracting the kitchen again.
[Touch HD Windows Mobile ROM Development] sparkienl:
To make your own clean kitchen put any not protected ruu_signed.nbh in the folder /Tools/RomSaved.

Click in the kitchen on the button "Dump nbh/nb/payload" and a new dump of the kitchen will be created in the folder /dump with all the folders like /Ext, /Oem, /Sys, /Rom from the extracted ruu_signed.nbh in it.

Then add any build xip and sys in the /Rom and /Sys folder and make your own build rom with the OS you want
[Touch HD Windows Mobile ROM Development] sparkienl:
Use this as your base kitchen and copy the 21231 or 21232 folders /Rom and /Sys from the kitchen I posted, in your base kichen and start building your rom:D
[Touch HD Windows Mobile ROM Development] vjsxda:
pls can i request u for OEM 1.59 plus can u make registry mods likes fixes for battery:) in ur nxt release :)
[Touch HD Windows Mobile ROM Development] xmsnx:
sparkienl thanks for your kitchen, is it possible to cook an unprotected rom? If so how?
[Touch HD Windows Mobile ROM Development] sparkienl:
wrong answer

When you do not check the xip,oem and sys fields Under Hide in the top left corner of the kitchen Ervius says you can rebuild your rom.

I tried but it didn't worked for me:D

Sorry wrong answer from my side

Ervius did made a version were you could check a field "unprotect" but it worked not out the wright way so he took it back.

The fields I mentioned above you can use when you build your own rom and you don't want to make any changes to this parts, you can hide them and so use this parts as they are before.:D
[Touch HD Windows Mobile ROM Development] xmsnx:
Ok that doesn't seem to work for me either :(

Any chance you would re-release this kitchen, with your sys, xip etc? :D

http://xdaforums.com/showthread.php?t=438456
[Touch HD Windows Mobile ROM Development] baituo:
Problem...just did a test. Build rom using the "Real 6.5 AKU" option, my HD just stuck at smart mobility screen. While not choosing 6.5 AKU option, rom is good to boot, but the 1st boot screen is WM 6.1, then it comes a WM6.5 screen. Phone running a bit sluggish, and system settings like Device Information, G-Sensor, TouchFlo, cannot be launched. I am on HardSPL 1.56. Anyone having the same problem?
[Touch HD Windows Mobile ROM Development] be_vigilant:
Hello

I had exactly the same problem.Everything was sluggish,no SD card was shown some apps didnt work like the ones you mentioned.

I had to use a tool called recmod on the browsing folders. As soon as I did this my next rom build was super fast and speedy with no sluggish performance at all.

My SD card was shown correctly and the apps that wouldnt work now work OK.

---

I then decided to make my own Kitchen using the 1.57 Base instead. Ported the new SYS and XIP in and my rom is working first go.

Sweet.
[Touch HD Windows Mobile ROM Development] sparkienl:
:D

That's because your the XIP doesn't contain a "native 6.5" nk.exe (kernel) and it can't handle as many modules as a real 6.5 kernel would. Therefore, you can only check that box on a Touch Pro ROM for now.:D

As you can check in this thread from ervius http://xdaforums.com/showthread.php?t=469420 the man behind this kitchen many problems are solved here.
[Touch HD Windows Mobile ROM Development] sparkienl:
http://xdaforums.com/showthread.php?t=469420 post 839 you can read the whole story. :D

The blackstone kernel can't handle as many modules as the native kernel of the ralph (which is where I assume you got that latest 6.5 release).

So what you have to do is "flatten" some of these modules. In other words, you have to turn them back into regular files. You can do that with recmod.exe found in the \tools folder. I would start with all the files in browsing, browsingcore and browsing IE. You coudl also not include "myphone" or "skybxo" and "windows live" which has a crapload of modules. If it boots without including those, then you're good. Just turn them all into files
[Touch HD Windows Mobile ROM Development] sparkienl:
See first post and start building your own rom:D
[Touch HD Windows Mobile ROM Development] sparkienl:
Thanks for the flowers, when ever you have somthing usefull just post it and I will insert it in the kitchen :)
[Touch HD Windows Mobile ROM Development] Mikenif:
Everytime i try to build a rom platformrebuilder.exe gives me a runtime error because it gets terminated in a unusual way.

does anyone know what could be the cause and how to fix this?

(im using the latest kitchen)
[Touch HD Windows Mobile ROM Development] sparkienl:
Before I upload a new kitchen, I build a rom with it first, flash it to the HD and when it boots and I can make a phone call it's uploaded to rapidshare.

So try to build it with premium.erv (my build).

The OS on my laptop is W7 and the kitchen is in the root of C drive.

Happy cooking:D
[Touch HD Windows Mobile ROM Development] EpiphanyNL:
How do you start the kitchen on W7? I always get the message that I need administrator rights to start the application.. Even though I am administrator, even when I start the application as Administrator.

Do you have an x86 or x64 version of W7?
[Touch HD Windows Mobile ROM Development] Mikenif:
Im trying to translate wm6.5 to dutch. could it be caused by the change of language files?

My kitchen is in the c root of my vista system and i am using the premium save
[Touch HD Windows Mobile ROM Development] sparkienl:
I'm using W7 x86 as administrator, just dubble click on Erviuskitchen.exe and start the kitchen.:cool:
[Touch HD Windows Mobile ROM Development] sparkienl:
Use premium.erv as starter.

Make small changes at the time, start building, when it ends try flash and when it boots make the following change.

When you make a lot of changes its impossible to find the error.:)
[Touch HD Windows Mobile ROM Development] ANDYx1975:
You're using a bad file which can't be handled by the kitchen...try to replace the files step by step...then you will find this corrupt file...then it will work:D
[Touch HD Windows Mobile ROM Development] Bysio:
hello, new build 23004

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

:)
[Touch HD Windows Mobile ROM Development] sparkienl:
New kitchen in 1st post, updated erviuskitchen (true/false in color by ervius).

Also Rhodium and Topaz packages included.

Happy cooking :D
[Touch HD Windows Mobile ROM Development] bobsbbq:
Hello, I had a chance to look at your kitchen and it looks very good. I assume the NueTools are not applied by default? I have a couple of suggestions and I will post the files later when I find them.

1. Use Dummy FWUPDATE. This will save some space.

2. Remove Uldr partion. I do this manually it is hard to tell if this is done without a report file. I know the new kitchen is supposed to do this but I can't tell if it is. done manually it reduces the os.nb.payload file by 3mb.

I will post the Dummy FWUPDATE soon.
[Touch HD Windows Mobile ROM Development] sparkienl:
The NueTools are applied by me as default, I just inserted them in the kitchen as folder/files when they make changes, they can redo it.

cu sparkienl :)
[Touch HD Windows Mobile ROM Development] Mikenif:
Guys thanks for the help.

Ive managed to build a dutch 6.5 rom although its got 1 pain in the a.. bug.

I cant compose a sms. If i press the composebutton in the manila smstab i end up in the outlook choose a account screen. And when in chome it opens the outlook sms inbox but in both cases if i try to open a new sms or reply it wont open the screen thats supposed to come up.

Am i missing a component?

Does anyone know what package is responsible voor the compose sms screen?

Any help would be greatly appreciated
[Touch HD Windows Mobile ROM Development] sparkienl:
Compare your build rom with the htc rom to see which files you didn't include in yours.
[Touch HD Windows Mobile ROM Development] sparkienl:
New kitche with sys 21921 in 1st post

happy cooking
[Touch HD Windows Mobile ROM Development] bobsbbq:
Another thing I noticed was the gray background when using your Kitchen without modifications. I think if you upgrade the DPI and Lang files this will correct this problem.
[Touch HD Windows Mobile ROM Development] texture:
Hi Bob,

Do you find this dummy package?

I don't find anywhere :(
[Touch HD Windows Mobile ROM Development] bobsbbq:
Sparkienl has it now. I guess it will be in the kitchen.
[Touch HD Windows Mobile ROM Development] texture:
Ok,thank you :)
[Touch HD Windows Mobile ROM Development] sparkienl:
Yes I will include it in the next kitchen :D
[Touch HD Windows Mobile ROM Development] EpiphanyNL:
@Mike: Tried it with the packages you recommended, no luck though :(

Now trying with older tmail.exe and poutlook.exe
[Touch HD Windows Mobile ROM Development] IoDa00:
Hi, Since I can't download the latest version because I don't have premium account in rapidshare, can someone share some links where i can download new versions. Thanks
[Touch HD Windows Mobile ROM Development] rickytr23:
which one i may have the one ur looking for
[Touch HD Windows Mobile ROM Development] sparkienl:
upload in 1st post updated sys 21889 :)
[Touch HD Windows Mobile ROM Development] EpiphanyNL:
Think I solved my bug.

I added NetCF from the SYS folder again, and hack, the stupid thing works :confused:
[Touch HD Windows Mobile ROM Development] IoDa00:
The 28205 version.

thanks
[Touch HD Windows Mobile ROM Development] balaji.admin:
Anybody has the following packages? If so can you share it.

Dshow_2_0_19163429_00

concurrence_Mgr_1_2_18192826_0002

Shared_Modules_1_01_19162825_00

/Balaji.