I htcdev unlocked my phone with the all in one Htc one x program. It all worked fine but i accidentally flashed an htc one x kernel on my sensation! Ive seen people say to just install a new one but when i do that it says an error about the boot.img. Help please!! SON btw
Reatret said:
I htcdev unlocked my phone with the all in one Htc one x program. It all worked fine but i accidentally flashed an htc one x kernel on my sensation! Ive seen people say to just install a new one but when i do that it says an error about the boot.img. Help please!! SON btw
Click to expand...
Click to collapse
Download a ROM, extract its boot.img then use fastboot command:
fastboot flash boot boot.img
Oh and p.s dont use tools designed for other phones in future - why you needed one to htcdev unlock is beyond me though, the instructions are perfectly clear on the htcdev.com website
Jonny said:
Download a ROM, extract its boot.img then use fastboot command:
fastboot flash boot boot.img
Oh and p.s dont use tools designed for other phones in future - why you needed one to htcdev unlock is beyond me though, the instructions are perfectly clear on the htcdev.com website
Click to expand...
Click to collapse
Its a lot easier that way, I found. Anyways, could you pleaselink me to a stable working rom? I dont trust myself on finding one. and what do you mean by "use fastboot command: fastboot flash boot boot.img"
Reatret said:
Its a lot easier that way, I found. Anyways, could you pleaselink me to a stable working rom? I dont trust myself on finding one. and what do you mean by "use fastboot command: fastboot flash boot boot.img"
Click to expand...
Click to collapse
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Jonny said:
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Click to expand...
Click to collapse
Is there a way to get the adb/fastboot files on a bricked phone? :C
lefiese wilful
Jonny said:
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Click to expand...
Click to collapse
Oh nevermind! I got it down, I am downloading ViperS Rom, i understand all your instructions now!! I am very confident this will work, ill reply with results.
Jonny said:
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Click to expand...
Click to collapse
By the way, the exact error is 'assert failed: write_raw_image("/tmp/newboot.img","boot")'
Reatret said:
By the way, the exact error is 'assert failed: write_raw_image("/tmp/newboot.img","boot")'
Click to expand...
Click to collapse
Yep, because you are S-ON, the script cant write to the boot partition which is why the fastboot flash boot boot.img workaround is needed
Jonny said:
Yep, because you are S-ON, the script cant write to the boot partition which is why the fastboot flash boot boot.img workaround is needed
Click to expand...
Click to collapse
Do you know where the boot.img is located? I downloaded CoreDrod Sensation and cant seem to find it.
boot.img is located
try to explore or double click the ROM you download ROMname.rar boot.img must in the archive.
Reatret said:
Do you know where the boot.img is located? I downloaded CoreDrod Sensation and cant seem to find it.
Click to expand...
Click to collapse
I dont know where its located in every ROM, just a few. My Sense 3.6 ROM boot.img is located in Extras/Kernel/ but most are just in the root of the file - I do things a little different because of the way my customizations in Aroma Installer work
Related
I was trying to flash faux kernel via recovery but i got the status 7 error so i guess the problem is that because iam s-on so plz anybody knows how to flash a custom kernel with s-on.
yus99 said:
I was trying to flash faux kernel via recovery but i got the status 7 error so i guess the problem is that because iam s-on so plz anybody knows how to flash a custom kernel with s-on.
Click to expand...
Click to collapse
Flash the boot.img from the zip via fastboot.
You can find the instructions here: http://forum.xda-developers.com/showthread.php?p=25587345
Make sure you use the boot.img from the zip & not the one from the guide.
HI
So just to make sure these are the steps:
Put the"boot.img" in your "C:\Android" (or wherever your adb and fastboot are located)
Shift right click in the white space on that folder
Select "Open command window here
Type in: adb
Type in: adb reboot-bootloader
Your phone will reboot, wait until you see a white screen which says "FASTBOOT USB"
Type in: "fastboot flash boot boot.img"
Wait until it's done flashing
Type in: "fastboot reboot"
One more thing i didnt see the boot.img in the zip of the kernel there are three folders:
1- kernel
2- META-INF
3- system
In the kernel folder there are these files:MKbootimg,dd,unpackbootimg,zImage,mkbootimg.sh,modclean.sh
What to do I am so confused
yus99 said:
So just to make sure these are the steps:
Put the"boot.img" in your "C:\Android" (or wherever your adb and fastboot are located)
Shift right click in the white space on that folder
Select "Open command window here
Type in: adb
Type in: adb reboot-bootloader
Your phone will reboot, wait until you see a white screen which says "FASTBOOT USB"
Type in: "fastboot flash boot boot.img"
Wait until it's done flashing
Type in: "fastboot reboot"
One more thing i didnt see the boot.img in the zip of the kernel there are three folders:
1- kernel
2- META-INF
3- system
In the kernel folder there are these files:MKbootimg,dd,unpackbootimg,zImage,mkbootimg.sh,modclean.sh
What to do I am so confused
Click to expand...
Click to collapse
thats a recovery flashable zip
you can flash that via recovery only
as you are SON ...better have 4EXT recovery
there ..just enable smartflash in 4EXT-> tools and then flash the kernel package
EDIT:
this thread explains the reason for error 7 and the probable fix
http://forum.xda-developers.com/showthread.php?t=1556620
hi
just one more thing do i need to uninstall my current recovery to install the 4-ext one or just install it.
yus99 said:
just one more thing do i need to uninstall my current recovery to install the 4-ext one or just install it.
Click to expand...
Click to collapse
just install it either via fastboot
fastboot flash recovery recovery.img
recovery.img from here (its rc3 ...and latest is rc5 btw)
or
via 4EXT updater app available in sensation development thread
I'm newbie in the Android world. I'm now rooting my HTC IncS using this guide (http://forum.xda-developers.com/show....php?t=2118187) and now stuck at step 3 which is unlocking bootloader. In this area I'm stuck where command prompt and fastbooting is included.
I'm not moving on steps unless I fastboot my IncS before I connect so I can do the step 8 and so on htcdev.com ...
What to do? I need how to fastboot my IncS. Thanks for the help.
The link is broken, but this is how fastboot is used:
1. Go to the fastboot folder and press shift+right click, then select open command prompt here
2. type in: "fastboot flash boot boot.img" where the boot.img is the file, you put in the folder before. It can also be kernel.elf, so then you type: fastboot flash boot kernel.elf
Thank you for the reply. :good::good::good:
But can you help me more? I have already flash my recovery and when I select recovery from the bootloader, it doesn't open the window where I will install the .zip files. It always turn on everytime I do it. Is there a step I did wrong?
Here is the guide I'm referring.
http://forum.xda-developers.com/showthread.php?t=2118187
[SOLVED] (not sure how to tag as solved in the title, if mods can do that please or tell me how)
Flashed Clockwork Mod Recovery following these instuctions
droidviews.com/2013/install-clockworkmod-recovery-on-motorola-droid-razr-hd-xt925gsm/
Installed Rom manager.
Booting into recovery results in robot on his back with the triangle and exclamation point animation and stays there unless I
force reboot by holding the power button. Phone boots to stock rom or fastboot just fine.
Tried reflashing CWM just in case.
I am rooted via motochopper
Unlocked bootloader via motopocalyspe.
I factory reset my phone prior to all this so there are only a few apps installed, also SuperSU installed.
Rogers version XT925
Anyone else have this issue or know how to fix it?
Are you using the cmd 'fastboot flash recovery recovery.img'
?
Sent from my Desire HD
ykdr-scott said:
Are you using the cmd 'fastboot flash recovery recovery.img'
?
Sent from my Desire HD
Click to expand...
Click to collapse
Thanks for the quick reply; yes that is the command I used to flash the recovery image to my phone.
check see if your recovery image is in the same directory as your fastboot eg Cmd > cd C:/fastboot flash recovery recovery.Img
I always paste my files directly into cd C:/ .
If you have them in a folder in c it would be ' cd C:/folder name here fastboot flash recovery recovery.img
Sent from my Desire HD
ykdr-scott said:
check see if your recovery image is in the same directory as your fastboot eg Cmd > cd C:/fastboot flash recovery recovery.Img
I always paste my files directly into cd C:/ .
If you have them in a folder in c it would be ' cd C:/folder name here fastboot flash recovery recovery.img
Sent from my Desire HD
Click to expand...
Click to collapse
They are in the same folder, in the mean time I actually found another thread with the same problem. I guess I didn't search hard enough the first time before posting. I found a 1 click installer for CWM/TWRP that fixed my issue. I'm guessing I may have just had a bad recovery img or something.
http://forum.xda-developers.com/showthread.php?p=42255792#post42255792
links to the thread with the 1 click installer.
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Go to bootloader and run "fastboot devices" and see whether your device gets detected or not? If it does, then flash the factory images. System and boot img files would do the job.
If it doesn't then you need to fix the adb, fastboot issues first. Follow these threads:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
If you have an OTG cable with you, you can directly flash the rom from a usb stick!
tangosierra_ said:
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
You havent got fastboot installed.
Go to teh link in my signature.... Then go to section 1b, 1
usb/otg
Dixi1801 said:
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.[/QUOT
Download any compatible rom to a usb/otg..mount from TRWP and your good to go..Happens to me once..Just download any compatible roms just to bring up your phone..
Click to expand...
Click to collapse
Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
remove all old drivers and restart
install http://forum.xda-developers.com/showthread.php?p=42407269&__utma=248941774.1031819907.1403635167.1403781687.1403790944.7&__utmb=248941774.1.10.1403790944&__utmc=248941774&__utmx=-&__utmz=248941774.1403790944.7.7.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
shhbz said:
remove all old drivers and restart
install http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
Click to expand...
Click to collapse
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
rootSU said:
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great and flash-all.bat script does not work evrytime so just wanted the guy to be sure the he type the commands in right direction instead getting error cant find and stuff
shhbz said:
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great
Click to expand...
Click to collapse
1b1 in the link in my signature.
Minimal is fine but you have to manually add to environment variables or cd to the directory but that's all done with the 15 seconds one.
Sent from my Nexus 5 using Tapatalk
Thanks for the help guys.
RootSU, you saved me haha, was sat at work stressing trying to sort the mess I made out!
I'm all stock now... But the screen keeps going off because of the proximity sensor haha -_-
Thanks again though. Can always count on a Yorkshireman
The important thing is to remain calm and know it can be fixed
Sent from my Nexus 5 using Tapatalk
Does this sound like an ok process for me to upgrade without losing data? I have a Nexus 5 with stock recovery and currently non-rooted. No modifications to the system that I am aware of.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Do I need to flash the system.img and/or the bootloader.img too?
Matthewlawson3 said:
Does this sound like an ok process for me to upgrade without losing data? I have a Nexus 5 with stock recovery and currently non-rooted. No modifications to the system that I am aware of.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Do I need to flash the system.img and/or the bootloader.img too?
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
Elluel said:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Generally speaking, is their a proper order for commands or does it matter? I noticed your command order is a little different from what I did when flashing in the past from one previous version of android to the next version.
Matthewlawson3 said:
Generally speaking, is their a proper order for commands or does it matter? I noticed your command order is a little different from what I did when flashing in the past from one previous version of android to the next version.
Click to expand...
Click to collapse
There is no order. The same things are flashed, the end result is the exact same.
Elluel said:
There is no order. The same things are flashed, the end result is the exact same.
Click to expand...
Click to collapse
So technically speaking I could flash in order and receive the same result?
Matthewlawson3 said:
So technically speaking I could flash in order and receive the same result?
Click to expand...
Click to collapse
I just said there is no order and it doesn't matter, you quoted the post that just said this lol.
Elluel said:
I just said there is no order and it doesn't matter, you quoted the post that just said this lol.
Click to expand...
Click to collapse
Oh, so I did. Thanks for the help!
"1. Extract the radio image to platform-tools folder"
Why this is necessary? Yesterday I flashed 5.1 using sdk's fastboot tool and I didn't do that. Was it wrong? My nexus model is D821 and it was stock 5.0.1. I'll be very grateful If you could guide me to do it right!
btw I followed this tutorial https://www.youtube.com/watch?v=5ka5dnPghzI
Thank you for your help!
gonzalobasterra said:
"1. Extract the radio image to platform-tools folder"
Why this is necessary? Yesterday I flashed 5.1 using sdk's fastboot tool and I didn't do that. Was it wrong? My nexus model is D821 and it was stock 5.0.1. I'll be very grateful If you could guide me to do it right!
btw I followed this tutorial https://www.youtube.com/watch?v=5ka5dnPghzI
Thank you for your help!
Click to expand...
Click to collapse
Radio is optional. On the Nexus 5, you can use any radio on any version of Android.
there is no reason to extract them to the platform-tools folder or to rename them. If you have fastboot in the cmd window just drag the img file into the cmd window after the command and it will have the correct path. So, fastboot flash boot (drag boot image here).
wangdaning said:
there is no reason to extract them to the platform-tools folder or to rename them. If you have fastboot in the cmd window just drag the img file into the cmd window after the command and it will have the correct path. So, fastboot flash boot (drag boot image here).
Click to expand...
Click to collapse
..and if you have adb/fastboot set up PROPERLY, you don't even need to open your cmd/terminal specifically in platform-tools.
It really doesn't matter, the result is obviously going to be the same. People will do whatever seems to be easiest for them.