Database Develop

[Q] stuck in boot loop

I rooted and flash my nexus one with a rom that was based on the cm7 nightly. It installed completely and I rebooted. It gets past the static x but loops in the moving x. I've tried so many things over the past 8 hours I need help to get a rom working on this. I tried going through the fastboot. Tried using recovery to update from sdcard and I'm having no luck getting this to work again. Hopefully someone on here knows how to fix my problem so I can get a working rom on my phone. Thanks everyone.

Did u install recovery (amon or clockworkmod?? If you did just dload another rom, wipe and flash again
N1

When I originally did the install I installed clockwork and did a back up. When I go into recovery all I can do is either wipe data, update from sdcard and wipe cache. I'm about ready to pull my hair out. I have no clue what went wrong. I've installed new roms on my old phones and no problems, I follow all the instructions.

nandroid, wipe all, retry flashing.
or restore your nandroid backup.
Looking at "adb logcat" while its booting will pinpoint the error.

I've tried to go through fastboot to use my recovery image but I get failed (remote: signature verify fail). I don't know how to get into nandroid and my computer I can only use the fastboot not adb to use logcat. Is there a way to use the fastboot that doesn't come up with the signature fail. I really don't know what happened. What other ways can I use my recovery image if I can't do it from the physical phone?

Sounds like a bad backup. DId you verify MD5?
If you want to start over..
Download AmonRa Recovery 2.2.1. From thread below...
http://forum.xda-developers.com/showthread.php?t=611829
With phone in fastboot mode and connected to PC via usb:
1. Command Prompt: fastboot devices (make sure device is connected)
2. Make sure recovery image file is in your SDK/tools folder
3. Make sure your working directory is SDK/tools folder
4. Command Prompt: fastboot flash recovery recovery-RA-passion-v2.2.1.img
5. After flash is done, reboot to recovery.
6. Wipe everything.
7. Re-flash your ROM.
You can always go back to Clockworkmod if you want. Just re-flash clockwork recovery.

thanks for the help but I'm still getting the signature verify failed even with the new recovery img.

projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Your getting this error when flashing what?

projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Did you unlock your phone (fastboot oem unlock) or did you just root it?
If you haven't unlocked your phone, perhaps try that then use the previous instructions to flash clockwork or amon recovery image.
link for reference

Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.

Make sure you add to his "Thanks" meter! BTW. That would have been my next suggestion...

projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Make sure you add to his "Thanks" meter! BTW, that would have been my next suggestion...
Sorry for the Double Post

projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Glad to help. I think we've all had those "OMFG HOW DO I FIX THIS" moments.

G1 not starting up

So I tried rooting my girlfriend's G1 and it didn't workout so well, so now I'm trying to fix it for her (I feel terrible, my poor android friend.. I mean my poor girlfriend!) . I rooted it and it was working find, but I wanted to flash a ROM on there. I tried flashing CM5 following the directions on the wiki. I made sure I installed Amon_Ra's recovery and did a nandroid backup. Then I flashed the DangerSPL. 2 things then happened, when I tried starting up the phone it would just hang on the "G1" startup screen until I pulled the battery, and when I went back into recover it switched back to the old recovery I had after root (JFv1.42). So I can't go back. But when I go into Fastboot, the HBOOT is at 1.33-2005, which indicated the DangerSPL was flashed correctly. So should I flash CM5( or 6 or 7) now? I just don't wanna get the phone to a point where it's unusable (unless it is already) =/ Can you guys help me out?

If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.

Your girlfriend G1 still fine.
The CM5 that you have flashed is not compatible with the SPL(HBOOT)/radio combination. (to my understanding) That is why it gets stuck at G1 screen (that had happens to me).
For G1, you can only flash up to CM 6.1 (to my knowledge), Cyanogenmod 7 will not (according to the DEV) works on G1.
You can try other ROM, recommending ezGengerbread, or Gingerbread Yoshi, and also my favorite (I am currently using it.) SuperAosp DM 2.8.2.
You will need to use 2708 SP and 13d radio for the newer ROM.
First load the radio, then the SPL. After both have been flashed (you can check it in the fastboot mode) then flash the ROM that you want.

AndDiSa said:
If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.
Click to expand...
Click to collapse
Where do I put in these commands?

Vulf said:
Where do I put in these commands?
Click to expand...
Click to collapse
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.

BeenAndroidized said:
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.
Click to expand...
Click to collapse
No, it's not adb, it's fastboot, a different program, but you are right, it's a program that runs on your PC. You have to make sure to have fastboot installed. Then open a command window and enter the commands above having your G1 connected to your PC and beeing in fastboot mode (boot with back + power).

@ AndDiSa - Sorry for the short explaination, I should have explain in more detail.

Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now

Vulf said:
Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now
Click to expand...
Click to collapse
Have fun.

So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..

Vulf said:
So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..
Click to expand...
Click to collapse
Hmm, someone post an instruction in one of the forum that I saw yesterday. Not sure which one. It would fix the problem you are having with not see your G1 on ubuntu..

You can solved your problem with unroot like me.even my g1 lost function home & call button.
Sent from my T-Mobile G1 using XDA App

[Q] Problem installing Recovery (out of memory)

Hello everyone,
I've already searched for this problem but I don't find a solution that works for me.
There is my problem :
I have a HTC G1 with COS-DS one day I tried to update de recovery with the beta one. I always have done this using the terminal so :
su
flash_image recovery /sdcard/recovery.img
And then the error starts saying that he had problemas reading 0x0000000 (out of memory), and a last message saying "error writing recovery: No space left on device"...
When I try to flash (that recovery or another one, the problem is the same) with fastboot, he says me that he doesn't have the right signature :S...
How can I solve the problem ?
Thanks in Advance ^^
PS : Rom Manager says that the recovery install successfully but it isn't truth, and Recovery Flasher didn't work too.
Pss : Sorry for my bad english

flash this file in recovery, than do superwipe right after and reboot

re
I don't have any recovery :S When I first tried to install the recovery and get the Read Error my current recovery just stop working..

o wow.. so what happens when you power on holding home+power?

I see the G1 T--Mobile screen and nothing happens :S...

hmmm but you can still get into fastboot?
EDIT: what was your latest radio & hboot?

Hi (thanks a lot for taking your time to help me ! really !)
Yes I can boot into fastboot (but if I try to flash the recovery using that solution I get a signature failed error.
Fastboot Informations :
Dream PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA20000)
CPLD-4
RADIO-2.22.28.25
Before that I was using the firt Radio and Hboot with the extra Ram (I can't remember the version :S)

no problem man lol but dont get too excited bcuz im not really sure what to do.. normally you would do the fr remove when this happens but you went too far and lost your recovery lol im not too familiar with fastboot... do you know of a way to down grade via fastboot? or can you at least boot up into a rom right now or are you wiped? lol

ldrifta said:
no problem man lol but dont get too excited bcuz im not really sure what to do.. normally you would do the fr remove when this happens but you went too far and lost your recovery lol im not too familiar with fastboot... do you know of a way to down grade via fastboot? or can you at least boot up into a rom right now or are you wiped? lol
Click to expand...
Click to collapse
I am using the COS-DS Rom working and booting normaly. So I can fully use Fastboot and my Rom... but if one of the 2 stop working... That can become a big problem :S...
The ironic thing is that I've update my Recovery because I dind't like the old one (ClockWorld installing with Rom Manager) in other to SuperWipe and then try the HTC SenseLX (your rom if i'm not wrong) XD.

ok well try to boot into your rom and download 'oi file manager' from the market than put these 2 files on your sd card!
flashrec
ra-dream
now open file manager and select the flashrec file.. open it then select backup recovery... if it does something or not we will see lol but than try to type in the box: sdcard/recovery-RA-dream-v1.7.0-cyan.img
than the "flash recovery button should light up. Press it and see what happens..

I've already try that (as said in my first post zs) And he says No Commound Found (but I can give it a try again ^^^)

ooo ok no your probably right... did you try downloading 'rom manager' from market than open and select flash clockwork recovery... see if that works..

Already done XD Rom Manager says that "Recovery Succesfully Instaled" but when I try to boot into recovyer (Home + Power Button to boot), I have the same G1 -- T-mobile and nothing more :S

o wow... lol this sucks.. uhhmmm im not sure what else to do.. search xda for threads saying 'No Recovery' or something... im pretty sure someone recently had this issue and solved it.. i dont know what it could be...

When i've searched for a solution I've found this solutions :
1 - Use a software to close all open software and then flash in terminal (Not Working)
2 - Flash using FlashRec (Not Working)
3 - Rom Manager 4 (He says that the install was successfull but it is not truth)
4 - Fastboot (Erase recovery and Flash Recovery file.img) - (Signature Error)
PS : it's funny... RomManager says that My current recovery is Recovery RA Dream v.1.7.0 - Cyan... But it doesn't boot. Now I've flashed with Rom Manager and He says "Current Recovery : ClockWorld 2.5.0.7)... I will try to boot again
EDIT : Not working :S...

ooooooooooo i know whyyyy!!!! fastboot doesn't work for 1.33.0013d lol you need an engineering spl 1.95.2003 thats the one fastboot works on for flashing files

argh zs Is there anyway I could install that SPL without broking anything else (like the rom since if this one brokes the situation could turn into a nightmare to me :S)...

ldrifta said:
ooooooooooo i know whyyyy!!!! fastboot doesn't work for 1.33.0013d lol you need an engineering spl 1.95.2003 thats the one fastboot works on for flashing files
Click to expand...
Click to collapse
... it's not completely true ... you have restricted fastboot capabilities!
look at this thread: you can flash the orange-xxx.nbh using fastboot, then you have a full engineeering spl, you boot into fastboot, flash the recovery (using fastboot), afterwards flash radio and spl (both using fastboot) again ... and you are done, i.e. working recovery, 2708-radio and 0013d-SPL.

o haha ok than nevermind... im not sure what the problem is..

YEAHH My Recovery is back ^^ Thanks a lot !
PS : What is the rom the nbh installed ?
EDIT : I found it XD Android 1.1 THE FASTEST ROM EVER (I'm not being ironic XD) Thanks a lot again !

[Q] i think i messed up

I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me

If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium

Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please

new problem
re edited to top post

Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium

i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?

N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)

homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?

N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot

At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?

N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.

Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!

Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread

bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?

No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip

Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2

Good catch!

Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope

You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img

Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img

[Help] White screen

Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?

Killa_vatt said:
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Click to expand...
Click to collapse
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.

tpbklake said:
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
Click to expand...
Click to collapse
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\

Killa_vatt said:
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Click to expand...
Click to collapse
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???

prunzzz said:
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
Click to expand...
Click to collapse
I have already tried many ways to install many other roms. What will you recommend?

Killa_vatt said:
I have already tried many ways to install many other roms. What will you recommend?
Click to expand...
Click to collapse
what kind of errors did you get when you flashed other roms??

prunzzz said:
what kind of errors did you get when you flashed other roms??
Click to expand...
Click to collapse
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.

Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
have you tried flashing through HBOOT??

prunzzz said:
have you tried flashing through HBOOT??
Click to expand...
Click to collapse
That is done by renaming a file to PG98***?

Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.

tpbklake said:
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
Click to expand...
Click to collapse
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.

Killa_vatt said:
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Click to expand...
Click to collapse
OK, after re-reading your posts, here are some additional tips:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
As for trying to flash 10 different RUU's there ERROR 131 indicates that you have a bad goldcard.

Killa_vatt said:
That is done by renaming a file to PG98***?
Click to expand...
Click to collapse
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Also consider what tpbklake said
HIT THANKS IF I HELPED YOU

tpbklake said:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
prunzzz said:
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Click to expand...
Click to collapse
I mean PG32IMG,forgot that.
I fully wiped everything.
I did not flashed rom's boot.img,thanks! Gonna try it later.

tpbklake said:
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
Thank you very much! I feel dummy now =)
Flashing rom's boot.img fixed all problems. Most of roms works now. Thanked everyone in topic.