I know last time I tried flashing a 4.4 ROM I would get some error because of some weird compatibility thing with CWM or TWRP or something like that. I don't remember which recovery it was that I needed that would let me flash, I'm trying to flash beanstalk
You should flash the boot.img from the rom zip using fastboot, then boot into recovery and flash the rom.
I would advise doing a lot more research of how to flash custom roms and how to fix potential problems before continuing on any further as it will save you time in the future in case of any problems.
Sent from my C6603 using Tapatalk
extract from the zip file boot.img
flash it through fastboot , reboot your phone and go to recovery and then flash the rom
Related
Hi.
I've got a problem. In all of the tutorials I read about how to flash ROM:s, it says that I have to flash boot.img through fastboot, then enter recovery and flash the ROM. I can not do this. When I flash the boot.img, I can not enter recovery or anything, I get stuck in a bootloop and have to restore through flashtool. When I flashed Taylor_Swift's 4.3 ROM, I flashed the ROM first and then the boot.img, it worked, I got up and running, but after that I couldn't enter recovery and therefore not obtain root access, making the ROM almost useless because the lack of the Battery Calibration app. Now I want to flash the PAC ROM, but I'm not sure how to do with the boot.img part. If it's relevant I have the lockeddualrecovery as my recovery.
Help please
Grozos said:
Hi.
I've got a problem. In all of the tutorials I read about how to flash ROM:s, it says that I have to flash boot.img through fastboot, then enter recovery and flash the ROM. I can not do this. When I flash the boot.img, I can not enter recovery or anything, I get stuck in a bootloop and have to restore through flashtool. When I flashed Taylor_Swift's 4.3 ROM, I flashed the ROM first and then the boot.img, it worked, I got up and running, but after that I couldn't enter recovery and therefore not obtain root access, making the ROM almost useless because the lack of the Battery Calibration app. Now I want to flash the PAC ROM, but I'm not sure how to do with the boot.img part. If it's relevant I have the lockeddualrecovery as my recovery.
Help please
Click to expand...
Click to collapse
No special order, really, as long as the kernel (boot.img) is fully compatible with the rom.
I'd flash PAC boot.img first though. Flash boot.img, then enter recovery and flash the zip containing the rom information.
Usually you should flash the boot.img that came inside the rom's zip and it should have a recovery,than you will have to install the rom from the recovery.
Don't forget to factory reset/wipe data inside the recovery.
Sent from my C6603 using xda premium
Unlocked rooted xperiaz..
installed this: http://forum.xda-developers.com/showthread.php?t=2190936
(tried also with cwm)
After entering recovery cwm or twrp i can choose ROM: (tried paranoid android)
I'm on the latest stock firmware btw... 244..
After flashing i only get a red light, and nothing else works.. can get to flas mode and flash stock ROM, but everytime i try a custom rom it fails..
Where am i going wrong? I Know i **** up somewhere, but can't see where...
Try flashing the Kernel from Paranoid Android by itself. Inside the rom's zip there ahould be an image called boot.img. Flash via fasboot on Flashtool.
Now enter recovery and follow the normal procedure.
First of all that link to TWRP is for locked bootloaders. You need to have an unlocked bootloader to install a custom rom
To get recovery just flash the boot.img which is inside the rom .zip folder
Code:
fastboot flash boot boot.img
Then enter recovery and flash the zip then gapps.
I want to flash the following ROM...
Link- http://forum.xda-developers.com/showthread.php?t=2223642
I am having problems understanding the procedure to flash the ROM.
I also want to ask ..are the steps same as flashing other JB or KK ROMs..
1)BOOT TO RECOVERY
2)MAKE A BACKUP
3)WIPE data,system,cache,dalvik cache
4)FLASH THE ROM's zip file
5)reboot to bootloader fastboot and flash boot.img in the ROM's zip file using the command ,"fastboot flash boot boot.img"
6)reboot system
will this work for the ROM menstioned above?
thanks for help......
Yes, normal flash procedure is the right way.
Sent from my Elephone G3 using XDA Free mobile app
To start: 5.1.1 (LMY48M), rooted, with TWRP for recovery
For every 5.x update so far, this has been my procedure using fastboot:
Flash boot.img
Flash radio.img
Flash system.img
After successfully updated, I'd use WugFresh's Nexus toolkit to root and flash TWRP.
I'm a fan of not needing to flash userdata.img, as I don't think that should be necessary given that the OTA wouldn't wipe installed apps and such.
I've read other threads about using fastboot to upgrade and am concerned about the boot warnings, which seem to require a custom kernel to circumvent. My question is: will the above approach still work? Do I need to flash any other files? If I need to flash a custom kernel, where do I get it, how do I flash it (is it just a custom boot.img?), and at which point in the flash sequence should I apply it?
Secondly, has anyone tried gaining root through the Nexus toolkit once upgraded to 6.0?
I'm looking for recommendations so I don't spend hours trying to unbrick my device. Thanks!
You'll also want to flash the 6.0 bootloader and why are you using the toolkit to flash twrp when you can flash it in fastboot along with the rest of the files?
Ah OK, I'll flash the bootloader image as well. Anything else to be concerned with? The toolkit has a feature to root + flash twrp as a feature, so I just use that.
Do the bootloader first, then reboot the bootloader before you flash anything else. There are instructions floating around here some where or you can google nexus 6 flash factory images. You don't have to flash user data as this will format all you data/ apps.
Just download the latest SuperSu zip (2.50) and put it on your SDcard. If you flash as you suggested and then boot directly into recovery, you will still have TWRP. If you don't flash the stock recovery.img to replace TWRP, it will replace on first boot anyway, unless you root imeediately, but you are probably booting to use the toolkit, which replaces recovery only to have to use the toolkit to flash recovery anwyay.
So do your flashes, boot straight into recovery, flash the supersu zip on your sdcard. Done.
Hi everyone, this question was asked already but I just want to make sure that it's safe to flash a 5.1 based ROM over a currently active Marshmallow ROM using TWRP using only the usual wipes? I remember that I had to flash a custom boot image with a PC or something like that in order for the custom recovery to work on my K3 Note, which I received with Marshmallow installed, so I'm not sure if I can hop back to 5.1 if phone never even had it installed. Any advice?
livgrave said:
Hi everyone, this question was asked already but I just want to make sure that it's safe to flash a 5.1 based ROM over a currently active Marshmallow ROM using TWRP using only the usual wipes? I remember that I had to flash a custom boot image with a PC or something like that in order for the custom recovery to work on my K3 Note, which I received with Marshmallow installed, so I'm not sure if I can hop back to 5.1 if phone never even had it installed. Any advice?
Click to expand...
Click to collapse
Yes, IT IS SAFE but there are some points to note:
Every Rom Zip contains a boot.img file which is also flashed when the zip is flashed.
You do not need to replace boot.img in order to install TWRP, but you need it to flash SuperSU.zip to your device or install xposed
Remember You need to wipe data partition (No need to wipe Internal) in order to continue.
Thanks for the reply. I don't know why, but I remember when I was installing TWRP I couldn't boot into it until I flashed a new boot image or something like that. All I could boot into was the stock recovery or something like that. I needed to use SP flash tools and flash something in order to get it to work. So it's safe for me to try 5.1 ROMs? They seem to be more stable than custom Marshmallow ROMs....
livgrave said:
Thanks for the reply. I don't know why, but I remember when I was installing TWRP I couldn't boot into it until I flashed a new boot image or something like that. All I could boot into was the stock recovery or something like that. I needed to use SP flash tools and flash something in order to get it to work. So it's safe for me to try 5.1 ROMs? They seem to be more stable than custom Marshmallow ROMs....
Click to expand...
Click to collapse
You must have flashed the recovery.img ( and also the boot.img) because my root methods mention them.