I got the jist of it since I'm coming over from the MyTouch Slide 4G, I already understand how to flash the boot and what not my question is...
Can I flash the boot.img, and then reboot into recovery wipe and flash the zip for the specific Rom? I see in all the instructions it always says wipe flash zip and then reboot into the loader and update the boot.img. Its not that big of a deal the only reason I ask is because I'm just use to flashing the boot image first and then installing the ROM, So I wanted to see if there's a big deal between doing that.
Related
I've flashed several One S roms with success and I wanted to see if someone could clarify the flashing of the boot.img.
1. If I've done it once, is it necessary that I flash the boot.img each time I flash a new ROM?
2. Some of the ROM pages say that I can skip the boot.img step if I use a TWRP, is that for all One S roms or just the ones which the developers indicate so?
Thanks
The boot image is part of the rom. It contains the kernel and the root file system on which the mmc partitions get mounted.
However, not all devices let you flash the boot image from recovery. (I dont think there is real consensus on the factors: hboot, twrp/cwm, ? but the fact remains that you may not be able to flash boot image from recovery.) So to be safe, it's better to always flash it through fastboot, since this always works.
The best time to do this is right before you boot into recovery to flash your rom, so that the first time it boots is right after you flash your rom.
I flash the boot.img every time even if it isnt necessary . I dont think it is hard to do so better flash safe then fast .
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks
You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.
So here is my problem. Every time I flash a recovery, my rom gets deleted, so I flash another one. But, when I flash a rom, my recovery gets deleted. So I flash recovery again... It's an endless cycle.
So, I either don't have a rom, or don't have recovery.
I have S-OFF with firewater and I am trying to flash skyfall and TWRP.
What the hell is going on? This has NEVER happened with any other phone I have owned.
EDIT: I have fixed the issue. If you too have this issue, please refer to post #3.
1. Are you wiping internal storage?
2. If you aren't wiping internal storage, where are you placing your ROM? Root of internal storage or in the download folder. Or your SD card? TWRP will allow you to access all your folders to find a ROM.
3. How are you flashing your recovery? Adb and the .img file from TWRP work best for me.
Flash TWRP using adb. Phone will boot into TWRP recovery. Do a factory reset WITHOUT wiping internal/external storage. Press install. Find your ROM and install it. Do a dalvik cache wipe. Reboot system. Wait...be patient and you should be good to go.
I also recommend downloading a ROM from your computer and placing it on your sdcard if you have one. Then you have no worries about it being erased. Hope this helps.
Sent from my awe inspiring HTC One M8
ironbesterer said:
So here is my problem. Every time I flash a recovery, my rom gets deleted, so I flash another one. But, when I flash a rom, my recovery gets deleted. So I flash recovery again... It's an endless cycle.
So, I either don't have a rom, or don't have recovery.
I have S-OFF with firewater and I am trying to flash skyfall and TWRP.
What the hell is going on? This has NEVER happened with any other phone I have owned.
Click to expand...
Click to collapse
use fastboot
for recovery : ./fastboot flash recovery recoveryfilename.img
for kernel : ./fastboot flash boot kernelfilename.img
at one point there were incorrect directions flashing TWRP in terminal telling you to send it to the wrong partition
scooterman said:
use fastboot
for recovery : ./fastboot flash recovery recoveryfilename.img
for kernel : ./fastboot flash boot kernelfilename.img
at one point there were incorrect directions flashing TWRP in terminal telling you to send it to the wrong partition
Click to expand...
Click to collapse
This is actually what I did and it fixed it. I forgot to edit OP.
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
you need to root the device and use flashtool by androxyde(Easier and user friendly), first download the rom and put it in internal/external memory and then install thunderzap 4.12 by select bootkk.img and install it in fastboot mode in flashtool, now enter the recovery go into wipe and format options and choose clean to install a new ROM and then flash the pac rom and reboot
Root isn't necessary.
Download PAC ROM, Take boot.img inside the zip.
Flash boot.img via fastboot.
Boot into recovery, wipe data / factory reset.
Flash ROM and GApps.
That's it
NOP, you dont need to root to install a custom rom
felix leiter said:
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
Click to expand...
Click to collapse
you can download the rom, extract it and keep, boot.img file, in fastboot folder, and also keep the downloaded rom zip file in sd card for later use.
than you can use use fastboot commands to flash those boot.img which will install the recovery into your phone, than .
use reboot command in fastboot, it will reboot your phone, take out your cable, using volume up key go to recovery,
there clear all the cache and delvik cache file, then, install your custom rom by selecting from your sd card, it will take a bit of time for first time, so don't worry,
than you are done,