Hey guys!! I was thinking about flashing the Blackout Beast Mode 3 to my phone thats runnig viper xl. I just wanted to make sure there're compatible and I also want to know if I have any problems how I would go about getting the stock kernel back. Thanks for your answers as always.
Nevermind I found the answer. No it will not work. Moderaters feel free to delete thread.
ImagioX1 said:
Nevermind I found the answer. No it will not work. Moderaters feel free to delete thread.
Click to expand...
Click to collapse
Yea it will. Flash the camera fix and it should work fine
Of course it wil bro. Flash that shiz and be amazed. I'm running viper 2.1, beastmode at a consistent 1.89 GHz, and this thing is on fire. You won't be disappointed
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Just a note I have had some overheating at times and a lot of slowdown without ocing...Although the slowing down I have a feeling is because of my execcive undervolting which did make my battery awesome though
I run performance. And overvolted :sly:
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Where would I find the camera fix cause I can't do without a camera? I have read several post in the beastmode thread but haven't seen a camera fix.
ImagioX1 said:
Where would I find the camera fix cause I can't do without a camera? I have read several post in the beastmode thread but haven't seen a camera fix.
Click to expand...
Click to collapse
cam fix
absolutelygrim said:
cam fix
Click to expand...
Click to collapse
I found it just before you posted, but thanks anyway. I think i'm going to give up on flashing the kernel though. I thought it could be done through recovery but with 2.20 you must flash through fastboot. I don't even know the commands for flashing or all the steps involved-i'm new at this stuff. Don't want to brick my five hundred dollar phone thats only a month old and don't even have a warranty.
ImagioX1 said:
I found it just before you posted, but thanks anyway. I think i'm going to give up on flashing the kernel though. I thought it could be done through recovery but with 2.20 you must flash through fastboot. I don't even know the commands for flashing or all the steps involved-i'm new at this stuff. Don't want to brick my five hundred dollar phone thats only a month old and don't even have a warranty.
Click to expand...
Click to collapse
You can't brick your phone by flashing a kernel.
If you really want to flash the kernel, do this:
1. Install the SDK (fastboot and adb) and drivers as per the root threads that currently exist
2. Flash BeastMode Kernel
3. While still in Recovery, open a Command Prompt (in Administrator mode) on your laptop
4. Switch to the folder where "adb.exe" and "fastboot.exe" are located
5. type "adb pull /tmp/boot.img"
6. If it fails, the drivers aren't installed properly or you're not in the right folder
7. Reboot your phone to Bootloader by typing "adb reboot bootloader"
8. Run "fastboot flash boot boot.img"
9. Reboot your phone
Make sure you also flash the cam fix.
Phone bootloops.
Will not work on my phone. Successfully pulled the boot.img after flashing in recovery. Then I flashed the boot.img that I pulled in fastboot. Then I reboot the phone and wind up in a bootloop. I then have to reflash the boot.img from viper to get the phone to start.
ImagioX1 said:
Wound up with a boot loop flashing the boot.img on page 166. I'm running Mac to do the fastboot commands and for some reason I cannot pull the boot.img after flashing the kernel.
Click to expand...
Click to collapse
Just drag and drop the boot.IMG out of the zip and put it in the same.directory as fasboot
Sent from my HTC One XL using xda-developers app
absolutelygrim said:
Just drag and drop the boot.IMG out of the zip and put it in the same.directory as fasboot
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
I edited my post after you posted that. I have sucessfully pulled the boot.img after installing beastmode. It is in the same directory as fastboot and it sucessfully flashes. It just bootloops after that.
Anyone have any ideas what the problem might be?
ImagioX1 said:
Anyone have any ideas what the problem might be?
Click to expand...
Click to collapse
Let's try this again
1.) Wipe System
2.) Factory Reset
3.) Flash boot.img from ViperXL (from fastboot)
4.) Flash ViperXL (from recovery)
5.) Boot your phone
6.) reboot into fastboot
7.) flash kernel boot.img on page 166 (from fastboot)
8.) flash kernel zip (from recovery)
After flashing the kernel, your camera will NOT work. You will need to flash the camera fix. I don't know if you have to flash that from fastboot or recovery on 1.14.
cam fix
absolutelygrim said:
Let's try this again
1.) Wipe System
2.) Factory Reset
3.) Flash boot.img from ViperXL (from fastboot)
4.) Flash ViperXL (from recovery)
5.) Boot your phone
6.) reboot into fastboot
7.) flash kernel boot.img on page 166 (from fastboot)
8.) flash kernel zip (from recovery)
After flashing the kernel, your camera will NOT work. You will need to flash the camera fix. I don't know if you have to flash that from fastboot or recovery on 1.14.
cam fix
Click to expand...
Click to collapse
Ok. Will try.
I still get a boot loop. If my phone can't handle 2.1 ghz would that be the cause of the bootloop?
ImagioX1 said:
I still get a boot loop.
Click to expand...
Click to collapse
oh 2.20 firmware..
try the same thing but without the last step
I don't know what they did, if they flashed the boot.img and rebooted, or if they flashed the zip with it
absolutelygrim said:
oh 2.20 firmware..
try the same thing but without the last step
I don't know what they did, if they flashed the boot.img and rebooted, or if they flashed the zip with it
Click to expand...
Click to collapse
Ill try that, but TURGE on the previous page of this thread said flash both.
Related
Hey All,
Long time reader, first time Soft Bricker. I was flashing the Z Kernel 2.0 over Viper, and am now in a bootloop that doesn't let me get into my Recovery (TWRP). I can get into bootloader, though, and run fastboot. I've read the instructions on how to fix this error by flashing the RUU, but I can't find a link to an RUU where there isn't a $12 fee.
Is there another way to do it? I backed up my stock One S from after I rooted.
Help?
Thanks!
MrPickleFicker said:
Hey All,
Long time reader, first time Soft Bricker. I was flashing the Z Kernel 2.0 over Viper, and am now in a bootloop that doesn't let me get into my Recovery (TWRP). I can get into bootloader, though, and run fastboot. I've read the instructions on how to fix this error by flashing the RUU, but I can't find a link to an RUU where there isn't a $12 fee.
Is there another way to do it? I backed up my stock One S from after I rooted.
Help?
Thanks!
Click to expand...
Click to collapse
Open the zip file for viper rom and extract the boot.img file and move it to the folder on your computer where adb.exe is. Then get into the phone into fastboot connect it to your computer and run this command. "fastboot flash boot boot.img"
That should get you back into viper.
dc211 said:
Open the zip file for viper rom and extract the boot.img file and move it to the folder on your computer where adb.exe is. Then get into the phone into fastboot connect it to your computer and run this command. "fastboot flash boot boot.img"
That should get you back into viper.
Click to expand...
Click to collapse
Thanks, going to take approximately 24 minutes while I wait for the Zip to download then I'll post results. Is Viper different in some way? I've flashed probably 50 roms (including an earlier version of Viper) and haven't run into boot.img issues as long as I've flashed a kernel with it. On H-Boot 1.08.
MrPickleFicker said:
Thanks, going to take approximately 24 minutes while I wait for the Zip to download then I'll post results. Is Viper different in some way? I've flashed probably 50 roms (including an earlier version of Viper) and haven't run into boot.img issues as long as I've flashed a kernel with it. On H-Boot 1.08.
Click to expand...
Click to collapse
You can just pull boot.img from your original download of Viper Rom if it's still on your computer. The reason i suggested that you flash the boot.img is because you said you only have access to fastboot and your problems started with you flashed a new kernel. Since the boot.img from the rom will contain the original viper kernel it should reverse your problem.
dc211 said:
You can just pull boot.img from your original download of Viper Rom if it's still on your computer. The reason i suggested that you flash the boot.img is because you said you only have access to fastboot and your problems started with you flashed a new kernel. Since the boot.img from the rom will contain the original viper kernel it should reverse your problem.
Click to expand...
Click to collapse
I didn't download the rom on my computer the first time around, just had it on my phone's "SD Card". So with our snail mail up here have about 10 minutes left on my computer download. Hoping this works!
You da man! Thanks a ton! Hopefully I'll be able to return this favor to someone else in the future.
MrPickleFicker said:
You da man! Thanks a ton! Hopefully I'll be able to return this favor to someone else in the future.
Click to expand...
Click to collapse
Glad it worked out for you. :good:
Hi i'm new to the att htc one x, just rooted, and installed twrp... then flash cleanrom5. I also noticed clean has a kernel, i did not see an install guide, but i've installed kernels before on my captivate. So what i'm wondering if it's as easy as....
1. place kernel on phone storage
2. reboot into recovery
3. install kernel from recovery
4. reboot
If there anything i am missing or if i am completely off could someone please help me out with this?
Thank you :good:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
redpoint73 said:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
Click to expand...
Click to collapse
Would you mind walking me through that process?
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
cannon19932006 said:
Would you mind walking me through that process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
absolutelygrim said:
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
Click to expand...
Click to collapse
I don't see anything about flashing kernels in that thread.
cannon19932006 said:
I don't see anything about flashing kernels in that thread.
Click to expand...
Click to collapse
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery. fastboot flash method http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
edit: btw, what exploit did you use to achieve root? Was it the x-factor exploit?
cannon19932006 said:
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
Click to expand...
Click to collapse
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
redpoint73 said:
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
Click to expand...
Click to collapse
i used x-factor yes, and yes it's 1.14, thank you both for the help.
cannon19932006 said:
i used x-factor yes, and yes it's 1.14, thank you both for the help.
Click to expand...
Click to collapse
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
absolutelygrim said:
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
Click to expand...
Click to collapse
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
cannon19932006 said:
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
Click to expand...
Click to collapse
Well, If cleanROM is using the same Kernel as stock, then you got lucky. If they use the same kernel, no need to flash boot.img.
If they are different kernels and you dont flash boot.img, you are now in a bootloop
lol Universal City
not bad
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
cannon19932006 said:
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
Click to expand...
Click to collapse
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
absolutelygrim said:
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
Click to expand...
Click to collapse
Success, THANKS!
absolutelygrim said:
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery.
Click to expand...
Click to collapse
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
cimenta said:
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
Click to expand...
Click to collapse
Because the new hboot makes it to where you cant flash kernels through recovery. only fasboot
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
cimenta said:
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
Click to expand...
Click to collapse
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
absolutelygrim said:
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
So although ROM zip file contains boot.img when flashing boot.img won't be flashed? That's why we need to flash is separately? Is it important to flash it before flashing ROM?
Thank you.R
I'm also, learning as I go. From reading and multiple failed attempts at flashing ROMs and kernels, I have found the correct way with 1.14 Hboot.
-dl the rom/kernel
-extract only the boot.img file
- save both .zip and boot to your desired folder.
-go into recovery and mount sd card to pc
-transfer .zip file to your phones sd card
-get back into fastboot on your phone
-transfer boot.img to fastboot folder
-from fastboot cmd prompt(if you have win7, open your folder with fastboot in it hold shift+right click and open cmd)
-type "fastboot boot boot.img" without quotes
-go back into recovery and clean cache/delvik
-then install .zip that you copied to the sd card
You should be good to go from there.
If I have left anything out, please feel free to correct.
Sent from my HTC One X using xda app-developers app
ok, so i just rooted my One X (AT&T) running 2.20 using the unlock-bootloader method (only one out there, right? )
i want to flash the latest stable CM10 rom (named cm-10.0.0-evita.zip), but i hear all this stuff about flashing the kernel or the boot.img first before flashing the rom...? i've never rooted/flashed on HTC before, so forgive me if it seems noobish. what i have heard so far is to flash the boot.img from the rom i want to flash while in fastboot from my computer, then transfer the zip to my phone and flash the zip from TWRP. this is what i have picked up from hours of web-crawling, so please correct me if i am wrong
and *sigh* yes, i did use the search bar. i was unable to find any forums relating to my specific question. i did find one, however, under the quad-core tegra One X (the international version) and didn't want to risk bricking my phone because of differences between the AT&T and Int'l versions.
Well. I'm gonna first say you didn't search very hard as there are 100,000 threads asking this same questions. BUT I will be nice today.
Open the cm10.zip and extract the boot.img from it and place them both on your sd card. No need to rezip the rom, just leave it as is.
With your phone in fastboot, open a command prompt in your fastboot folder and type fastboot flash boot boot.img.
Boot into TWRP and flash the cm10.zip
area51avenger said:
Well. I'm gonna first say you didn't search very hard as there are 100,000 threads asking this same questions. BUT I will be nice today.
Open the cm10.zip and extract the boot.img from it and place them both on your sd card. No need to rezip the rom, just leave it as is.
With your phone in fastboot, open a command prompt in your fastboot folder and type fastboot flash boot boot.img.
Boot into TWRP and flash the cm10.zip
Click to expand...
Click to collapse
ok, thanks so much
i figured there were forums for this already but i've been looking for a week and a half and gathering all the information i needed for this moment. sorry to waste your time if it did, and thanks for the generosity i really do appreciate it
Or use flashgui app.. Its in apps and themes.. Download cm10 and gapps from your phone. Open flashgui. Browse and find cm10. Select it and let the app flash it.. IMMEDIATELY after boot into twrp, flash entire rom, once successful immediately flash gapps. Boot system and profit
Sent from my One X using Tapatalk 2
InflatedTitan said:
Or use flashgui app.. Its in apps and themes.. Download cm10 and gapps from your phone. Open flashgui. Browse and find cm10. Select it and let the app flash it.. IMMEDIATELY after boot into twrp, flash entire rom, once successful immediately flash gapps. Boot system and profit
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
thanks for the info, but i already got to flashing it in twrp. i'll keep that app in mind for later, though
dont i "wipe cache/dalvik" after flashing the rom?
ok, please disregard my last post. after restoring my backup (thank GOD i made it ) and re-flashing AFTER i cleared caches and did a factory reset, i am in CM10 thanks for everyone's help, mods this thread can be closed
Say, do you have an AT&T HTC ONE X that was on the 3.18 Jelly bean update that you rooted and unlocked the bootloader? Say you made a backup before you did anything. Did you try to flash a rom and found out that with s-on you had to manually flash the boot.img? Notice how your back-up doesn't work and you are stuck in a bootloop. OOOH SPOOKY!! here is how you get around that.
This is assuming the backup was made while you were still on the original 3.18 update and you have a windows pc.
1. Download the boot.img. Its a boot.img from a stock att 3.18 rom.
2. go to where you have your sdk folder and put the boot.img in the "platform-tools" folder.
3.Get into the bootloader menu (turn off phone and then hold power+down)
4.Press volume down one time to highlight fastboot then press the power button to choose it.
5.Connect phone to computer and wait until red text (FASTBOOT) turns into(FASTBOOT USB).
6. Now open up cmd or command prompt
7.change the directory so that your are in the platform tools folder ( cd " " so on and so forth)
8. once in the platform tools folder and your phone still connected type in : fastboot flash boot boot.img
9.let it do its thing
10. Once done, disconnect, and try to boot again.
You should be past the bootloop and into your backup again!
Eh... What if they flashed AOSP? or 3.4 kernel AOSP? -_-
exad said:
Eh... What if they flashed AOSP? or 3.4 kernel AOSP? -_-
Click to expand...
Click to collapse
AOSP as in a stock rom? Hmmm... I don't think it would matter as long as you flash the boot.img and then flash the backup. I think it would still work.
wizzrah said:
AOSP as in a stock rom? Hmmm... I don't think it would matter as long as you flash the boot.img and then flash the backup. I think it would still work.
Click to expand...
Click to collapse
you should flash the boot.img from the rom your flashing -_-
exad said:
you should flash the boot.img from the rom your flashing -_-
Click to expand...
Click to collapse
What he's saying is if they are trying to go back to their nandroid and it's not working.
Sent from my evita
RollTribe said:
What he's saying is if they are trying to go back to their nandroid and it's not working.
Sent from my evita
Click to expand...
Click to collapse
ooooo I misunderstood. My apologies
exad said:
ooooo I misunderstood. My apologies
Click to expand...
Click to collapse
no its ok lol I mean this is only if you have s-on.
Flashed the latest RUU from HERE, and it boots into the OS perfectly.
Then, flashed Stock GPE from HERE and also tried LolliGPE from HERE. Both will not get past the boot screen, after waiting over 30min's.
In attempts to fix, the latest full firmware, TWRP, full wipe/dirty wipe, and DH's 5.1 firmware have been flashed, then the custom ROM's flashed again followed. Same issue is persists. Each time, trying to flash the RUU back, boots without issue.
Prior to flashing the latest RUU (hboot method, 0P6BIMG.zip), I have ran all the ROM's mentioned and others without issue.
I'm at a loss of what to try next, or why it's hanging. Right now, i'm leaving it for hours at the boot screen, but I doubt this is going to cure anything and only provide a hot phone during the whole time.
The phone is unlocked, S-OFF, and SuperCID.
Any suggestions i'm willing to try.
Update:
Woke up 6+ hours later, and it was still stuck on the boot screen.
Flashed the latest Fluent ROM found HERE, and it boots fine. Then did a full wipe (Cache, Dalvik Cache, Data, System), then the standalone data wipe, and factory reset. Installed GPE from HERE, and it stuck on the boot screen again after waiting 20min's...
Next step i'm going to try is 4.4.4 RUU, then full latest OEM firmware. If GPE doesn't boot still, i'll try DH's 5.1 firmware.
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
kcasner said:
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
Click to expand...
Click to collapse
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
santod040 said:
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That was exactly it, what a relief. Thank you!
kcasner said:
That was exactly it, what a relief. Thank you!
Click to expand...
Click to collapse
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
dottat said:
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
kcasner said:
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
Click to expand...
Click to collapse
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
dottat said:
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Honestly can't recall. I follow; we're on the same page, different lingo.
kcasner said:
Honestly can't recall. I follow; we're on the same page, different lingo.
Click to expand...
Click to collapse
kcasner, I had exactly same issue as you. Could you explain a bit detail on how you get it fixed?
I want to flash DH5.1. Are these correct steps I should following:
1) open DH5.1 zip file, find the boot.img (I found there're two boot.img, stock/boot.img and elite/boot.img, I guess I should use later one)
2) fastboot flash the boot.img
3) boot into recovery to flash DH5.1
4) reboot
Thanks for help!