Related
I have my friends att lg thrive 506 and I flashed the clockworkmod recovery for the optimus one and it looked distorted in color. I ignored it and flashed miks cyanogenmod, and it gave me the same problem in color distortion. So I restored a backup I made before flashing cyanogenmod and then I flashed a the clockworkmod for the optimus v (since rom manager gave me a lot of options for ones to flash, and that was the only other lg one.) Then I pushed reboot into recovery from rom manager and it got stuck at the lg splash for about 10 minutes then shut down. Now when I try to turn the phone on I get the same problem.
Is there anything I can do to fix this? If not I have to buy him a new phone full price, and I can't afford that. I'd be fine if it took him back to full stock and wiped all the data, right now the phone is screwed over. Please, any support is appreciated I really need this fixed.
Thanks in advance.
Also if this is in the wrong section, please move it mods.
linuxman008 said:
I have my friends att lg thrive 506 and I flashed the clockworkmod recovery for the optimus one and it looked distorted in color. I ignored it and flashed miks cyanogenmod, and it gave me the same problem in color distortion. So I restored a backup I made before flashing cyanogenmod and then I flashed a the clockworkmod for the optimus v (since rom manager gave me a lot of options for ones to flash, and that was the only other lg one.) Then I pushed reboot into recovery from rom manager and it got stuck at the lg splash for about 10 minutes then shut down. Now when I try to turn the phone on I get the same problem.
Is there anything I can do to fix this? If not I have to buy him a new phone full price, and I can't afford that. I'd be fine if it took him back to full stock and wiped all the data, right now the phone is screwed over. Please, any support is appreciated I really need this fixed.
Thanks in advance.
Also if this is in the wrong section, please move it mods.
Click to expand...
Click to collapse
Can u getting recovery atleast
Sent from my LG-P500 using XDA Premium App
No recovery just does the same thing a normal boot does. I haven't tried but when its turned on and pluged in to my computer, I may be able to use adb shell to view the normal system files but I don't think ill be able to see the critical files, like where the recovery is stored.
I use an HTC phone and know things like rru's let us flash stock roms like this and even revert to stock recovery, do any such things exist for this phone?
CHILL
perhaps u should use a kdz updater? remain calm and search it up. I fixed my phone that way too. Just don't bash your head like I did. :> But I'm not sure if there is one for yer model...........??? Hope this helps anyway...
Whatever you do, don't use any kdz updater. P506 kdz is not published, and p500 kdz will brick your phone.
If you only flashed a bad recovery you can fix it by re-flashing a correct one.
Your options, sorted by difficulty.
(1) remove/reinsert battery and reboot. If the rom boots fine (wacky colors or not), reflash Optimus One recovery from Rom Manager.
(2) remove/reinsert battery; use power+home to get to fastboot; now try (1) again.
(3) remove/reinsert battery; use power+home to get to fastboot. Connect usb and follow this. You'd probably be better off with the recovery here.
Once you fix your recovery, flash deodexed stock rom instead of CM7.
Drivers... -_-
raenye said:
If you only flashed a bad recovery you can fix it by re-flashing a correct one.
Your options, sorted by difficulty.
(1) remove/reinsert battery and reboot. If the rom boots fine (wacky colors or not), reflash Optimus One recovery from Rom Manager.
(2) remove/reinsert battery; use power+home to get to fastboot; now try (1) again.
(3) remove/reinsert battery; use power+home to get to fastboot. Connect usb and follow this. You'd probably be better off with the recovery here.
Once you fix your recovery, flash deodexed stock rom instead of CM7.
Click to expand...
Click to collapse
Well thanks for this, but I can't preform the guide for one reason, drivers. I goto the lg site and get the drivers and I installed them, but I think the drivers are for when the phone can boot. And when I goto device manager, it shows up as android phone (with a ? as the icon)
So would someone be so kind as to share their driver for emergency mode with me? Thanks.
P.S. I am running Windows XP-Service-Pack-3, Intel Pentium 4-3.40-ghz-dualcore, 2048-mb-ram, 32-bit system
Edit:
I used my windows 7 laptop which auto-downloaded the drivers for me, then it worked like a charm, thank you very much.
linuxman008 said:
Well thanks for this, but I can't preform the guide for one reason, drivers. I goto the lg site and get the drivers and I installed them, but I think the drivers are for when the phone can boot. And when I goto device manager, it shows up as android phone (with a ? as the icon)
So would someone be so kind as to share their driver for emergency mode with me? Thanks.
P.S. I am running Windows XP-Service-Pack-3, Intel Pentium 4-3.40-ghz-dualcore, 2048-mb-ram, 32-bit system
Click to expand...
Click to collapse
Try disabling virtual modem.
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
netwokz said:
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
Click to expand...
Click to collapse
looks like I've got my work cut out for me. Glad I have a dual boot with Ubuntu...anyway thanks for your help.
no problem. You might want to post anything further in that thread, you will probably get more help over there. But either way let us know if you succeed.
Sent from my Ice Creamed 3D
w0rdOo said:
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
Click to expand...
Click to collapse
Do you know how many times I tried to brick this thing when I was downgrading? I almost gave up! And you do it by accident? Lucky you
Edit... Sorry bout your luck, hope all goes well.
no luck so far, I opened windows sda13 thru sdk13 and none of them found the device. i guess i'll reboot and try sda13-sdz13 lol.
Just took my phone to a sprint store, after about 30 min the repair guy came back and handed me the phone. He told me he doesn't have the tools necessary to fix it so I need to come back tomorrow, but he said I'm going to have to lose all my data in order to get the phone working again using his method. I hope the emmc_recover works tonight, or tomorrow I'll probably have hboot 1.5 and s-on
Is it possible that emmc_recover won't work because I'm on the engineering hboot?
I just realized I should probably post in the downgrade hboot thread, so I'm doing that now.
EDIT: fixed my phone flawlessly, the only reason it didn't work the first time is I forgot to pull the battery before plugging it in. Thanks again for your guys' help!
Post-trial of ICS Playground
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
rugbykj said:
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
Click to expand...
Click to collapse
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
w0rdOo said:
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
Click to expand...
Click to collapse
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
wikdNoob said:
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
Click to expand...
Click to collapse
The links netwokz provided above showed me that it was a specific release. TwistedUmbrella was experimenting (and I downloaded the experimental ROM, not one of the more "stable" releases) to try to get usb mount to pc to work, and something was wrong in the build I downloaded because it wiped the emmc so I couldn't boot to the phone, recovery, or bootloader. Basically, the ROM bricked my phone in the same way that you're supposed to brick your phone when downgrading from hboot 1.5. Luckily, Twistedumbrella is a great dev who helped people who bricked their devices out. In case you're worried about running into the same issue I did, the build that bricked me is no longer online, as he's updated the experimental and regular download links.
I know it was a specific release because I wasn't the only person who reported this problem. I think it was the 1 am experimental build from 03/22. Anyway, I'm now downloading twistedumbrella's latest experimental. Back to the ROM flashing game
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
emarlatt said:
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
Click to expand...
Click to collapse
I haven't had any sort of issue from running an ICS ROM in boot manager while running a sense 3.0/3.5 ROM as my default OS. This reported brick was caused by one specific release of playground ICS that would have bricked my phone in the exact same way if I just installed it through my recovery instead of through boot manager. Boot manager wasn't at fault here.
This thread was resolved several days ago. Can I close this thread or something? I've never tried to before so idk how to go about doing that...Well in the meantime, I guess I can just hope nobody else decides not to read page one before posting...
Hello.
I have a Motorola Atrix that is not working and I have no clue about the history of the phone. I have no idea how it was messed up, or what was done to the phone.
Currently I see a screen with the M logo on it and the word unlock in the top left corner. I have seen many other people with this phone have had this same issue. I tried doing the common tip of wiping data and cache but nothing worked.
Can anyone help me out here. I dont care what the phone looks like I simply need it to turn on without a hitch and be able to navigate the menus. I could go completely stock and be thrilled. My only problem is that I am a complete beginner and cant figure out what to do or where to find current files. I have done a lot of searching here and a lot of the links seem to be broken, probably because this is an older phone...
Thanks anyone in advance!
PS: Im trying to fix this to turn into ATT for a credit towards a new phone, anyone who helps me solve the problem gets a free meal!
xda_bob said:
Hello.
I have a Motorola Atrix that is not working and I have no clue about the history of the phone. I have no idea how it was messed up, or what was done to the phone.
Currently I see a screen with the M logo on it and the word unlock in the top left corner. I have seen many other people with this phone have had this same issue. I tried doing the common tip of wiping data and cache but nothing worked.
Can anyone help me out here. I dont care what the phone looks like I simply need it to turn on without a hitch and be able to navigate the menus. I could go completely stock and be thrilled. My only problem is that I am a complete beginner and cant figure out what to do or where to find current files. I have done a lot of searching here and a lot of the links seem to be broken, probably because this is an older phone...
Thanks anyone in advance!
PS: Im trying to fix this to turn into ATT for a credit towards a new phone, anyone who helps me solve the problem gets a free meal!
Click to expand...
Click to collapse
Try flashing the 4.5.141 (2.3.6) SBF file via RSD for a full stock experience. This makes the phone "forget" that its unlocked (the unlock at the top left disappears). If you want to keep it unlocked, flash a fruitcake via CWM.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Try flashing the 4.5.141 (2.3.6) SBF file via RSD for a full stock experience. This makes the phone "forget" that its unlocked (the unlock at the top left disappears). If you want to keep it unlocked, flash a fruitcake via CWM.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Where can I find the 2.3.6 file? The ones I have found here are all broken links thus far.. I cant find the most current list I suppose.
xda_bob said:
Where can I find the 2.3.6 file? The ones I have found here are all broken links thus far.. I cant find the most current list I suppose.
Click to expand...
Click to collapse
Here's the post that gives you 4.5.145 (2.3.6). It returns the phone to stock and unlocked, but gets rid of the recovery. You'll need to dig through your system partition to delete the file that forces the stock recovery to show up before flashing a new recovery.
Warning : This may brick your phone . I am not responsible for damaged devices.
OTA IS ONLY FOR AT&T
Here is the OTA update zip
CAUTION!!!!
Some users reported bricks
failed to boot 1
http://db.tt/ATldH97n
And 38P Radio Rom (pulled from ota)
http://db.tt/AkQHXIc8
I dont prefer to flash ota
And the fruitcake
All credits goes to NYG-SBXLII
THIS IS FOR UNLOCKED DEVICES ONLY
BE SURE TO BACKUP BEFORE FLASHING
DONT FORGET TO WIPE USER DATA
Download here http://www.mediafire.com/?yofp249u4bcc26m
Also, here's another way to do it. Either method will work. The method below tells you where the recovery file i mentioned earlier is in the system partition.
I have made a cwm flashable zip for anyone that would like to test the new build. It includes kerrnel, system and webtop. I have tested this on my device and seems to work fine. However i will not be responsable for any bricked devices. flash at your own risk.
i have rooted this build with an older method so su binarys may need to be updated
also you will need to have a way to reflash your recovery there is a recovery-from-boot.p file in /system that will overwrite recovery with a stock one on every boot. it should be a very easy fix just find the file in /system and delete it reflash whatever recovery you like and the problem should be solved (sorry i just didnt have time to fix this)
For non AT&T users if you would like to try this build you can probably use the ramfix or one of faux123's kernnel. I can not tests this so i have no idea if it will work
THIS IS FOR UNLOCKED DEVICES ONLY
BE SURE TO BACKUP BEFORE FLASHING
DONT FORGET TO WIPE USER DATA
Download here
http://www.mediafire.com/?yofp249u4bcc26m
If 4.5.145 isn't what you want, try this link for other versions/carriers
www.das8nt.com/downloads
Sent from my MB860 using xda app-developers app
I have recently rooted my HTC One X+. I made a nandroid as well as an titanium backup. I tried to install this rom cynamogen 11.2 nightly
Unfortunately the installation went wrong due to the following reasons (MD5 file not found). Then I tried to restored my nandroid backup .
This operation was succesfull however after restarting the phone is still stucked on the splash screen (htc quietly brilliant).
I can still have access to bootloader as well as the TWRP 2.6 and restoring again and again !
So what i have to do !
zekinan said:
I have recently rooted my HTC One X+. I made a nandroid as well as an titanium backup. I tried to install this rom cynamogen 11.2 nightly
Unfortunately the installation went wrong due to the following reasons (MD5 file not found). Then I tried to restored my nandroid backup .
This operation was succesfull however after restarting the phone is still stucked on the splash screen (htc quietly brilliant).
I can still have access to bootloader as well as the TWRP 2.6 and restoring again and again !
So what i have to do !
Click to expand...
Click to collapse
I'm having the same problem. Somebody got a solution to this? Bootloader works, Recovery works, it just won't boot, and WinDroid HTC Tookit detects my device, but when I try to flash or run a command it says "A phone has bot been recognized by this toolkit". I unlocked my phone successfully, flashed a recovery, but when I click flash ROM and when I try to push a file I get that error.
EDIT:
I fixed my issue using Kubuntu. I'm sorry mate, if you use Windows I can't help you there. That's why I never really like Windows it's a retarded and flawed OS. Linux? Not so much. Get Linux and you can practically fix the issue yourself, if no one comes up with a solution for Windows.
Did you flash the boot.img ? ...
Thread cleaned,
Guys back on topic please. Do not flame other users on a public forum. If you have an issue with a users post, report it to us and we will deal with it.
Many thanks,
Ghost
similar stuff going on here
I tried to flash the latest venom kernel having already done this when i first got the phone back in 11/12 or 1/13 somewhere round there.
I hadnt read all the instructions and hadnt updated the loader or recovery. now its stuck on boot screen. I can get to recovery. unfortunately the only zip thats on the phone is the new (wrong one). The windroid sees a number and recognises that its in recovery but is unable to do anything with it, no adb side load push pull, nowt. I just happened to buy a micro usb host cable. I was wondering if there are any commands that I could put into terminal that would allow it to see a memory card or any help at all..
Daryll99 said:
I'm having the same problem. Somebody got a solution to this? Bootloader works, Recovery works, it just won't boot, and WinDroid HTC Tookit detects my device, but when I try to flash or run a command it says "A phone has bot been recognized by this toolkit". I unlocked my phone successfully, flashed a recovery, but when I click flash ROM and when I try to push a file I get that error.
EDIT:
I fixed my issue using Kubuntu. I'm sorry mate, if you use Windows I can't help you there. That's why I never really like Windows it's a retarded and flawed OS. Linux? Not so much. Get Linux and you can practically fix the issue yourself, if no one comes up with a solution for Windows.
Click to expand...
Click to collapse
Hi mate, can you plz tell me how you got ure problem solved with linux ? thx
lha18 said:
Hi mate, can you plz tell me how you got ure problem solved with linux ? thx
Click to expand...
Click to collapse
I extracted the "boot.img" file from the zip file of my desired ROM, then I open terminal, booted my phone into Fastboot and typed "fastboot flash boot boot.img".