Develop Bugs

S-on - How to manually flash?

forgive my ignorance, i'm new in this kind of stuff, and i need some help.
i would like to flash this new kernel by franco (link below) but i'm confused/lost so can someone give me a step by step instruction? i'd really appreciate it i mean a lot! i've already unlocked the boot loader, its showing as s-on
http://forum.xda-developers.com/showthread.php?t=1646883

Flash the modules package in clockworkmod recovery.
To flash the rest you have to have the android sdk installed and you have to put the boot.img file in the same folder as fastboot.exe. From a command prompt you have to navigate to the folder that has those files and use the command "fastboot flash boot boot.img " while your phone is in fastboot.
Sent from my HTC One X using xda premium

thanks... but can you do it in more specific way? like step 1.1.3.4.5...etc..

mikey0105 said:
thanks... but can you do it in more specific way? like step 1.1.3.4.5...etc..
Click to expand...
Click to collapse
1. Download the Fastbbot files
2. Extract it to the root of your drive (C: or D So you should have a "Fastboot files" folder in your C or D drive
3. Now put the boot-r1.img in the Fastboot files folder
4. Start up command prompt (type "cmd" in the search bar) and navigate to the fast files folder. To navigate to the fastboot files folder you have to type "cd\" and then type "cd\Fastboot files".
5. Now boot your phone into bootloader (by holding down power button for a few seconds until it reboots and then press and hold down the volume down (-) button). And then once in fastboot mode select "Fastboot USB" by pressing the power button.
6. Now type the commands "fastboot flash boot boot-r1.img" and that's it.

that's what im talkin' about shadowboy! thanks so much! 1 big thank you button for you.. cheers mate!
EDIT:
oh BTW, i tried opening CMD, then entered the words above but its not opening, it says cannot find path,
i put my files under 1 folder named it "fastboot"

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My mistake it suppose to be "Fastboot" folder not "Fastboot files" folder.

thanks for doing an extra mile to explain this thing to me, really appreciate it.. im starting to learn

No worries.

after it says "finished" i closed the CMD and restarted my phone, so everything is okay after that? it took like 1 second to complete

mikey0105 said:
after it says "finished" i closed the CMD and restarted my phone, so everything is okay after that? it took like 1 second to complete
Click to expand...
Click to collapse
Yes you're done. That's all you have to do.

i forgot to mention, i went to recovery, then installed the modules there via zip file then rebooted the phone
EDIT:
o shoot, is this normal, after rebooting, it wont turn on, i mean, its just showing htc and its been like 4 mins now

mikey0105 said:
i forgot to mention, i went to recovery, then installed the modules there via zip file then rebooted the phone
EDIT:
o shoot, is this normal, after rebooting, it wont turn on, i mean, its just showing htc and its been like 4 mins now
Click to expand...
Click to collapse
No it's not normal. Might have to erase the cache "fastboot erase cache" see if that works

via CMD?

mikey0105 said:
via CMD?
Click to expand...
Click to collapse
Yep via cmd.

heres what ive done, erased cache via cmd >> did the instruction you've given me, then reboot, but still, its just showing the htc logo

mikey0105 said:
heres what ive done, erased cache via cmd >> did the instruction you've given me, then reboot, but still, its just showing the htc logo
Click to expand...
Click to collapse
Instructions:
1 - Enter this command: fastboot erase cache
2 - Flash the boot.img on fastboot with: fastboot flash boot boot—rX.img (replace X by the release number)
3 - Reboot to recovery from the fastboot menu (before booting to system for the first time) and flash the modules package
Those are the instructions from the franco kernel thread..
You should follow those instructions.

i did but its not working now.. im stuck with HTC loading screen

mikey0105 said:
i did but its not working now.. im stuck with HTC loading screen
Click to expand...
Click to collapse
Go and start from scratch is your best bet.

[GUIDE] How to flash " .IMG " files [HOW TO]

So,
I searched the forums for about an hour but i was not able to find a proper guide on how to flash .img files. Mostly, people have problems flashing recovery files.
This might be pretty easy but,...Still,it might help someone.
Here are some simple steps on how to flash .img files onto your Galaxy Nexus.
Let's Get Started
• First of all download this great toolkit by WugFresh from his website.
• Setup the toolkit by installing the Samsung drivers(you must have already installed them).
• Now enable USB debugging on your device by Setting>Developer Options>Android Debugging > [check enable].
• Download ClockworkMod Recovery from here.
• Now Click on Launch (Advance Utilities) at the bottom left corner on the toolkit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
___________________________________________________________
• Now check ' Flash (Permanent) ' .
___________________________________________________________
• Click 'Recovery'
___________________________________________________________
• Now, Select the .img recovery file you've downloaded or you can search the file path given below(in the image) for recovery.img files included in the toolkit.
___________________________________________________________
• Select OK and then your'e Done !.

looks good.. here are the steps for mskips toolkit if you wanna add them
download .img file
place the .img file in mskips toolkits "put img file here to flash here" folder
boot gnex to fastboot mode and connect to pc
open mskips toolkit
choose model number
choose option 11 "boot or flash .img file to device"

at first look i thinked you write the steps for flash a .img..but in fastboot..not in a toolkit.i think that flash in a toolkit is so easy also for a total-noob..because they are made for that!instead of do this type of installation,i'd preferred to see the standard fastboot mode,to encourage people to do it manually ( 30 sec)
sometimes **** happens and with the use of toolkit it's more difficult trace problems,anyways that for the guide!
EDIT at this point,i think this is not bad
to flash a .img files from fastboot,download and do an md5 of the file,copy it in the fastboot folder and in a command terminal from windows after going to the directory of fastboot where you downloaded the file digit: (yours phone has to be in fastboot-mode and with usb-debug ON)
FOR A RECOVERY .img
fastboot flash name_of_file.img
FOR A BOOTLOADER .img
fastboot flash bootloader name_of_file.img
FOR A BOOT .img (kernel+ramdisk)
fastboot flash boot name_of_the_file.img
1.some in the fastboot directory have the file inside nomined fastboot-windows..if it's the case,you have to write always fastboot-windows instead of fastboot in commands..or you can rename it that's more quick.
2.when you have to do with a recovery,if you want to only trying that,you can instead of -fastboot flash- do -fastboot boot-..in this case the phone boots with that recovery but after a reset it reloads the previous
EDIT 2
you can add in yours poll the voice "i don't use toolkit".i think in the end will have lots of vote!

Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus

thegtfusion said:
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+1 fastboot is a lot safer and easier.

Nice. I had my recovery installed via cwm by the way.

thegtfusion said:
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
this.
if you are going to teach people how to flash .img files, do it right, not through a root toolkit. oh, and in no way does this belong in development.

Guides like this are best in General or Themes
Please read rule 15 for a better description of what should be posted where
Thank you for your cooperation
Thread moved
FNM

lawl.
fastboot flash recovery nameofrecovery.img is so hard.

Jesus! What thread have I stepped into!
Beamed from my Grouper.

Zepius said:
lawl.
fastboot flash recovery nameofrecovery.img is so hard.
Click to expand...
Click to collapse
We had someone in IRC when the Gnex first came out flash recovery to the boot kernel.
For those confused,
fastboot flash boot recovery.img
The user couldn't figure out why it only booted to recovery

adrynalyne said:
We had someone in IRC when the Gnex first came out flash recovery to the boot kernel.
For those confused,
fastboot flash boot recovery.img
The user couldn't figure out why it only booted to recovery
Click to expand...
Click to collapse
Lol!
Beamed from my Grouper.

fastboot flash problem

My phone is arc and I installed like this.
1. Xperia Arc S
2. Super Jelly Bean 2.0
But I tried to install fxp209 for easy updating, but I could not flash boot.img.
ths adb driver installed as this picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I tried to install kernel as this.
but the message is only "flashing...", and not end it.
Please let me know what's problem.
Thanks in advance.

Default fastboot flash problem
First question is your bootloader unlocked!!
If yes try flashing like below
How to fastboot a kernel
(1) Download kernel .boot img place in folder Windows/Flashtool/Firmware
View attachment 1787067
(2) Press lightening bolt
(3) Select Fastboot mode
(4) Connect phone in Fastboot mode (Hold Menu Button ) then connect your phone to pc
(5) Choose select kernel to flash in Fastboot on pc
(6) Wait -until finished 10 seconds tops
(7) Done! switch phone on boot to cwm wait for vibrate/blue light press down/up/or back button depending on kernel or age of phone
Also try booting into fasboot manually as above (step 4)
Also if the fxp kernel not working try another compatible kernel there is plenty in the forum

First question is your bootloader unlocked!!
Click to expand...
Click to collapse
He is using CM10 based ROM so I think his bootloader must be unlocked.
To OP: You can try to flash a kernel with a fastboot and CMD like a real man ; D. Google how to use fastboot.

pypcier said:
He is using CM10 based ROM so I think his bootloader must be unlocked.
To OP: You can try to flash a kernel with a fastboot and CMD like a real man ; D. Google how to use fastboot.
Click to expand...
Click to collapse
Lol I knew that But believe me I have seen people try to flash cm based rom's/kernels with locked bootloaders that's why I never presume it is unlocked unless they have stated it in the post that it is unlocked :good:

My phone is "bootloader unlocked".
And I tried to flash at command line, but it didn't finished.

The correct command is fastboot flash boot kernelname.img See the link in my sig for more help.

XperienceD said:
The correct command is fastboot flash boot kernelname.img See the link in my sig for more help.
Click to expand...
Click to collapse
Yes, I did "fastboot.exe flash boot boot.img".

Try again without an .exe extension. Just type fastboot flash boot kernel.img

After command "fastboot flash boot kernelname.img", command line shows;
sending 'boot' <6430 KB>....
Click to expand...
Click to collapse

That's how it's supposed to be. Show us the rest of CMD content after typing that command.

TWRP 3.0.0-0

Hi,
PLEASE VISIT THE CORRECT AND OFFICIAL THREAD HERE. THIS THREAD WILL NO LONGER BE UPDATED.
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Jev

Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?

jevtheboss said:
Hi,
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
-Jev
Click to expand...
Click to collapse
Not sure if -i 0x2970 is needed for fastboot think its only for fastboot oem
No need for battery removal there is a fastboot command ........fastboot reboot......... that does the same thing

dnahc said:
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
Click to expand...
Click to collapse
Hi,
Please could you visit the thread here and ask the question there. I think TWRP 3.0.1 will fix the issue. :good: If not, on the TWRP website, 3.0.2 has been released which is supposed to fix some decryption issues so please wait for the thread (the one I linked to earlier) to be updated

Question Booting GSI's

hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers

stevendeb25 said:
hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
Click to expand...
Click to collapse
I really don't know much about GSI's, but don't you have to disable AVB before flashing one? Basically disabling vbmeta verification and verity (which would require a factory reset afterwards)? Not sure if you've done or tried this, so just throwing it out there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com

Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com

Morgrain said:
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
The bootloader has nothing to do with the bootanimation. If you see the bootanimation, the bootloader has done it's work ages before.

From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Nothing data corrupted
Rebooted back to bootloader
Fastboot reboot recovery
Data reset
=Google logo
Fastboot reboot bootloader
Fastboot flash boot magisk_patched.img
Fastboot reboot
=Bootanimation
ADB ain't enabled in boot.imgs so can't pull logcats to try to see why no boot.
Tried lineage, octativeos, LeOS, phusson, same with all GSI's
P.s phone is intact and easily put back to stock

stevendeb25 said:
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Click to expand...
Click to collapse
As @Lughnasadh said, it looks like you're missing the disabling of AVB by flashing Google's custom vbmeta.img before installing the GSI image.
Note: If your device has adopted Android Verified Boot (AVB), download and flash the following image to disable AVB before flashing a GSI: vbmeta.img
Click to expand...
Click to collapse
As above, see here: https://developer.android.com/topic/generic-system-image#flash-gsi (blue box).

hi thanks for that, flash vbmeta
still stuck on bootanimation.
i have tried a number of gsi's does this error matter when flashing gsi? "Invalid sparse file format at header magic" still installs fine