Database Info

[How To] Flash Custom recovery and ROMS after 2.20 root

I'm sure there will be a lot of people running the 2.20 root then not knowing what to do. So follow this guide.
Make sure you have adb and fastboot available to use.
Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Download the ROM you want to run, plus associated gapps to your phone, place them in the download folder (look in the android development and android original development threads)
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
If you have the newer HBOOT 1.14 (you probably do if coming from stock 2.20), boot.img's will have to be flashed separately via fastboot. Extract the boot.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes)
You can then flash the ROM and gapps via recovery and reboot and enjoy.

GuyIncognito721 said:
I'm sure there will be a lot of people running the 2.20 root then not knowing what to do. So follow this guide.
Make sure you have adb and fastboot available to use.
Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Download the ROM you want to run, plus associated gapps to your phone, place them in the download folder (look in the android development and android original development threads)
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
If you have the newer HBOOT, radio and boot.imgs will have to be flashed separately via fastboot. Extract the boot.img and radio.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes) and 'fastboot flash radio radio.img'
You can then flash the ROM and gapps via recovery and reboot and enjoy.
Click to expand...
Click to collapse
Also, this thread will be useful for flash-aholics :http://forum.xda-developers.com/showthread.php?t=1910294

What if I only see the boot.img and not the radio. The rom is CleanRom V5

may I ask which ROM for a stable AOSP experience ? I daresay none of us 2.20 sufferers have been frequenting the ROM sub-forums

JustTheHustle said:
What if I only see the boot.img and not the radio. The rom is CleanRom V5
Click to expand...
Click to collapse
Sorry, I removed the part about flashing radios. You ca't with the newer HBOOT. Only if we had S-OFF.

GuyIncognito721 said:
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
Click to expand...
Click to collapse
Would you mind expanding on that? I'm new to this even though I've had the phone since May. I'm unable to put the phone into bootloader mode by holding power and volume down (phone just boots normally) so I need another way.
Thanks

sandys1 said:
may I ask which ROM for a stable AOSP experience ? I daresay none of us 2.20 sufferers have been frequenting the ROM sub-forums
Click to expand...
Click to collapse
RebelMOD. Jelly Bean and everything works.
Sent from my HTC One XL

Epos7 said:
Would you mind expanding on that? I'm new to this even though I've had the phone since May. I'm unable to put the phone into bootloader mode by holding power and volume down (phone just boots normally) so I need another way.
Thanks
Click to expand...
Click to collapse
More specifically I'm not sure how to connect to the device in cmd. If I run 'adb reboot bootloader' it returns "device offline"
edit - closing/re-opening cmd appears to have solved the problem.

I'm not sure what I did, but I can no longer boot into bootloader mode. When I try now, I see a phone with a red exclamation mark inside a triangle. Does anyone know what I've done wrong or how to fix this? After a minute or two the phone reboots normally.
edit - I re-ran the script for 2.20 root to create a new backup and am now back in bootloader mode.

When i wrote adb rebot recovery it did not work what happened?

so say i want to run the viper rom i just pull the boot.img out of the rom and place it with my fastboot.exe file ( i have that and my adb files from when i unlocked the bootloader in the same folder) and flash it then i boot into recovery and wipe everything and install like normal? i came from a mytouch 4g and it was as simple as putting on the sd card wiping and flashing. this has got me a little worried i may screw up somewhere
another thing, the file is just named boot do i need to rename it boot.img before i flash it?

jrlatta said:
another thing, the file is just named boot do i need to rename it boot.img before i flash it?
Click to expand...
Click to collapse
I'm guessing the filename extension is just being hidden. Did you try typing boot.img in cmd? If that works you know the extension is there.

i went ahead and flashed everything and its finished now, hopefully everything boots, well i just got a snake so i guess so far so good

ImmenseGT said:
When i wrote adb rebot recovery it did not work what happened?
Click to expand...
Click to collapse
FWIW I had to flash TWRP twice. Didn't stick the first time for some reason.
Sent from my cm_tenderloin using xda app-developers app

if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
Click to expand...
Click to collapse
also do I do a factory reset in recovery before I do my fast boot flash boot.img? or do I first flash the boot.img, then reboot to recovery and do factory reset?

Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
Click to expand...
Click to collapse
I believe so. That is what I have been doing.

Epos7 said:
................................oops
Click to expand...
Click to collapse
what?
---------- Post added at 03:24 AM ---------- Previous post was at 03:18 AM ----------
Epos7 said:
I believe so. That is what I have been doing.
Click to expand...
Click to collapse
did you get venom installed ok like that?

Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
also do I do a factory reset in recovery before I do my fast boot flash boot.img? or do I first flash the boot.img, then reboot to recovery and do factory reset?
Click to expand...
Click to collapse
i booted into recovery and wiped everything and then went and flashed the boot image then from bootloader, used the volume keys to get to recovery, booted into recovery and selected the file i wanted to flash let it run and presto it worked, i did not choose to wipe again since i wiped before flashing the boot image because i was afraid it would erase it

Just let you guys know, my toolkit allows you to flash boot.img. Just place the boot.img in the /Data/Kernels folder and press "With this command" and it'll flash it!
http://forum.xda-developers.com/showthread.php?t=1952426

yep working for me too.

Bricked my phone trying to update to 4.2! Help!

Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.

zenkix said:
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
Click to expand...
Click to collapse
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img

RollTribe said:
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
Click to expand...
Click to collapse
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!

zenkix said:
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
Click to expand...
Click to collapse
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?

RollTribe said:
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
Click to expand...
Click to collapse
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.

zenkix said:
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
Click to expand...
Click to collapse
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!

RollTribe said:
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
Click to expand...
Click to collapse
Quick update...I flashed boot.img of the first link (CynogenMod) and my phone got passed the "HTC Quietly Brilliant" screen! But now it seems stuck on HTC One (Beats Audio at the bottom) screen. I'll give it a few minutes...
I'm really worried that I did major damage to my phone in the bootloader and clockwork recovery menus. I literally tried every single option there trying to get my phone to boot earlier.

Oh man...it seems stuck. Maybe I should just flash the completely stock boot.img file. If that works, I will factory reset my phone just to make sure everything is back to how it was before.

Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita

timmaaa said:
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your help man. If what you're saying is correct, does that mean my phone is hopeless? I deleted/wiped everything using the ClocworkMod Recovery menu. When I choose "install zip from sdcard" I get "E: Can't mount /sdcard/" and when I try to mount an sdcard I get "Error mounting /sdcard". I don't think I can flash any ROMs right now unless install zip from sideload is an option (I don't know how sideloading works).

Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita

timmaaa said:
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
Click to expand...
Click to collapse
This sounds like a good plan. I will give it a try tomorrow after work. Thank you guys for your help!

I couldn't sleep...so I followed your steps and my phone is now alive! Thank you!
I think now I need to flash GApps, right? I have this ---> gapps-jb-20130301-signed.zip
Any chance that's the wrong zip file? Do I need a special one for CM10.1?

That's the right gapps zip, it's the most recent one so yeah you're good to flash it.
And no problems, you're welcome
Sent from my Evita

[Q] Sensation will not load past the splash screen...

I am hoping that I can find help out there. My phone will not load past the splash screen.
Over the last few days I have been trying to install a custom rom on my phone. I thought I was on the right track and now I have flashed it but it will not go past the splash screen. I would be grateful for any advice on how to get my phone back functioning. I would even be happy to have it back stock.
So my movements over the last few days have been as follows:
1) HTC DEV unlocked the bootloader
2) Used Hasoon2000's HTC Sensation 4G all-in-one to flash CWM.
3) Then the same tool to copy Prem Root onto the SD card and installed it via CWM.
4) Then used this post here to install JB Miui - http://miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
Then when I rebooted it is stuck on the Miui splash screen.
At every stage I felt like things worked well and now I have that sad feeling in my stomach because I have just realized how vital my phone is.
Any help would be greatly appreciated.

Did u flash boot.img after u flashed the rom? Did u full wipe before flashing the rom? Also with s-on users its recommended to use 4ext recovery and in recovery, enable smartflash.

Where can I find information about boot.img - so that is a no. I am installing 4ext now.

jmcclue said:
Did u flash boot.img after u flashed the rom? Did u full wipe before flashing the rom? Also with s-on users its recommended to use 4ext recovery and in recovery, enable smartflash.
Click to expand...
Click to collapse
ok, so I have been looking at the boot.img part and I found this video: http://www.youtube.com/watch?v=5xVl2dBTnmI
I have followed it but still am not having any luck.
Still very lost.

LiamRutherford said:
ok, so I have been looking at the boot.img part and I found this video: http://www.youtube.com/watch?v=5xVl2dBTnmI
I have followed it but still am not having any luck.
Still very lost.
Click to expand...
Click to collapse
open rom.zip and search for the boot.img
probably it is located in the kernel folder
place it in the folder where you have adb and fastboot files
now boot your device to the bootloader and connect it to pc via usb(in the hboot screen it should say fastboot usb)
in the folder where you have adb and fastboot files open a cmd window and do this command
fastboot flash boot boot.img
then
fastboot reboot
done

rzr86 said:
open rom.zip and search for the boot.img
probably it is located in the kernel folder
place it in the folder where you have adb and fastboot files
now boot your device to the bootloader and connect it to pc via usb(in the hboot screen it should say fastboot usb)
in the folder where you have adb and fastboot files open a cmd window and do this command
fastboot flash boot boot.img
then
fastboot reboot
done
Click to expand...
Click to collapse
Thanks - this did the trick. Now to hunt out roms.

LiamRutherford said:
Thanks - this did the trick. Now to hunt out roms.
Click to expand...
Click to collapse
as suggested before it is better to have 4ext recovery
and before flashing any rom enable smartflash from it(for S-ON devices)
smartflash it does exactly what i said above

Bootloop (S-ON/No Recovery) :(

Hello,
I have a big problem with my old HTC Sensation.
I tried nearly everything out of other topics, but nothing worked....
The story: Suddenly my Sensation rebooted and from then on it is stuck in an endless bootloop.
The bad thing is, that it was stock/S-ON at this moment.
Informations about the phone:
***UNLOCKED***
Pyramid PVT Ship S-ON RL
HBOOT: 1.27.0000
Radio: 11.24A.3504.31_M
-> I am able to install RUUs (3.33), but after installation i am still in the bootloop
-> I am able to unlock/relock the bootloader
-> I can install a recovery via fastboot, but can't boot into it => bootloop
Maybe you have got a hint to bring the Sensation back to life.
Thank you!

Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!

kevinspl2000 said:
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
Click to expand...
Click to collapse
actually he can't even boot to the recovery in order to flash any rom
so what's the point of flashing the boot.img manually?

You can use Sensation all in one kit v3 to unlock boot loader, read this thread for more detail
http://forum.xda-developers.com/showthread.php?t=1497404
after unlocking boot loader, then go to this thread to download 4EXT recovery then use kit to flash recovery, remember to download image file, not zip file
http://forum.xda-developers.com/showthread.php?t=1377759
boot to recovery, then enable smart flash and flash any cook ROM you want. Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck

stripeqn said:
Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
Click to expand...
Click to collapse
actually first has to wipe and then enable smartflash

Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again

BrainyTheKing said:
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
Click to expand...
Click to collapse
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...

kevinspl2000 said:
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
Click to expand...
Click to collapse
I erased the cache before and after flashing recovery.
No success ...

Pixel TWRP boot loop

So I did the following steps
- Unlocked bootloader
- Booted in TWRP
- Installed TWRP zip from the recovery
- Installed magisk.zip
Everything seemed to work fine, but now it takes forever to boot, an only boots into TWRP, asking for my password.
I cannot seem to boot normally.
Please help, thanks for your time

I think most of the time if you flash the boot.img from whatever stock firmware you are on it should boot right up,,,atleast thats what i did in the past

Daped16 said:
So I did the following steps
- Unlocked bootloader
- Booted in TWRP
- Installed TWRP zip from the recovery
- Installed magisk.zip
Everything seemed to work fine, but now it takes forever to boot, an only boots into TWRP, asking for my password.
I cannot seem to boot normally.
Please help, thanks for your time
Click to expand...
Click to collapse
Archangel said:
I think most of the time if you flash the boot.img from whatever stock firmware you are on it should boot right up,,,atleast thats what i did in the past
Click to expand...
Click to collapse
If you're running a stock ROM, you have to have the full factory image downloaded, and extract the boot.img file. Then, put your phone in bootloader mode and run the following command from your PC: fastboot flash boot boot.img
You will lose TWRP & root, but you will be able to boot. When you go through the process again, reboot after each flash, so you know whether it has worked.

Isnt that basically what I said? Just making sure because you included me on your post?
post-mortem said:
If you're running a stock ROM, you have to have the full factory image downloaded, and extract the boot.img file. Then, put your phone in bootloader mode and run the following command from your PC: fastboot flash boot boot.img
You will lose TWRP & root, but you will be able to boot. When you go through the process again, reboot after each flash, so you know whether it has worked.
Click to expand...
Click to collapse