Database Info

(NEED HELP ASAP) Phone wont boot after updating Bootloader via flashify

I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4

Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC

EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!

I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device

EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway

Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick

rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5

Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.

rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.

Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?

rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*

[Q] ota sideloading aborted

Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance

drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?

kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader

I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.

drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.

I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img

So while sideloading it should I unroot as well?

jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?

drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app

pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.

jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app

No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.

Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?

jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...

If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.

I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.

jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?

I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me

pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?

Problems with downgrading to KitKat

Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.

BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB

Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.

I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.

Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet

BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.

was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.

Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.

BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8

Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.

[Q] Moto G XT1031 Stuck on "Bootloader Unlocked" Screen

Hello there,
Recently I had tried to go back to back from cyanogenmod 4.4.4 to stock 4.4.4, I accidentally flashed a XT1033 4.4.4 version.
Which was successful, but as I have a XT1031 device my phone does not use a sim card.
I then found a correct XT1031 4.4.4 stock firmware, but when I flashed this I had gotten stuck on the Bootloader Unlocked screen.
I tried it again with the same firmware, as well as others I found around, with little success.
I back tracked to the XT1033 version, went into fastboot mode and installed a custom recovery, CWM to be specific.
I then tried to sideload a stock 4.4.4 XT1031 ROM, I managed to get past the bootloader unlocked screen, but my phone then got stuck on "Starting Services" and I also noticed it was still getting detected as XT1033 on my computer.
Once again I tried to flash stock 4.4.4 firmware, again getting stuck at the bootloader unlocked screen.
At this point I'm at a loss how I should proceed or if my phone is even recoverable, I'm not worried about my data (as I backed it up before this whole fiasco, if only I had backed up a ROM too...).
If it wasn't obvious already, I'm not too experienced with all this, but at this point I'm just wondering if I should order another moto g.
Any help is appreciated.
Thanks,
Dan

Dan2QT said:
Hello there,
Recently I had tried to go back to back from cyanogenmod 4.4.4 to stock 4.4.4, I accidentally flashed a XT1033 4.4.4 version.
Which was successful, but as I have a XT1031 device my phone does not use a sim card.
I then found a correct XT1031 4.4.4 stock firmware, but when I flashed this I had gotten stuck on the Bootloader Unlocked screen.
I tried it again with the same firmware, as well as others I found around, with little success.
I back tracked to the XT1033 version, went into fastboot mode and installed a custom recovery, CWM to be specific.
I then tried to sideload a stock 4.4.4 XT1031 ROM, I managed to get past the bootloader unlocked screen, but my phone then got stuck on "Starting Services" and I also noticed it was still getting detected as XT1033 on my computer.
Once again I tried to flash stock 4.4.4 firmware, again getting stuck at the bootloader unlocked screen.
At this point I'm at a loss how I should proceed or if my phone is even recoverable, I'm not worried about my data (as I backed it up before this whole fiasco, if only I had backed up a ROM too...).
If it wasn't obvious already, I'm not too experienced with all this, but at this point I'm just wondering if I should order another moto g.
Any help is appreciated.
Thanks,
Dan
Click to expand...
Click to collapse
Try restoring stock. http://forum.xda-developers.com/showthread.php?t=2542219
ROMs here http://www.filefactory.com/folder/c6cdedc45a775d27/

dominati said:
Try restoring stock. http://forum.xda-developers.com/showthread.php?t=2542219
ROMs here http://www.filefactory.com/folder/c6cdedc45a775d27/
Click to expand...
Click to collapse
Thanks for your input, but unfortunately that actually was the method I was using,
Any other suggestions?

Dan2QT said:
Thanks for your input, but unfortunately that actually was the method I was using,
Any other suggestions?
Click to expand...
Click to collapse
You did all the fastboot commands? Was each command successful?

dominati said:
You did all the fastboot commands? Was each command successful?
Click to expand...
Click to collapse
Yeah, each of them gave me an "[OKAY]". I tried multiple ROM's too.
As of right now, the only one I could actually boot up on my device, was an XT1033 Brazillian 4.4.4 version (which boots successfully, but I can't use because it's not compatible with my device).
I might try to flash to that firmware, then re-install the XT1031 cyanogenmod I was using and restart the whole process.
I've tried a lot of different things at this point, so I'm willing to do whatever now.
-Dan

Same thing happened to me. In fact I ended up flashing xt1032 on my xt1031. Good thing is if it goes to the screen when loading to starting services and just keeps trying and trying then just look for the NON-HLOS.bin and fgn.mbn files for xt1031 and flash through fastboot. Basically those files are your radio. Or what you can do as well if you want to is to look for the radio flash zip file and flash it through custom recovery. Find the radio and kernel flash zip file and it should work as well. Those two files are here on XDA somewhere so you'll have to look for those. If your gonna use custom recovery route I found that twrp works better. I've had problems with cwm and philz.

christopher68369 said:
Same thing happened to me. In fact I ended up flashing xt1032 on my xt1031. Good thing is if it goes to the screen when loading to starting services and just keeps trying and trying then just look for the NON-HLOS.bin and fgn.mbn files for xt1031 and flash through fastboot. Basically those files are your radio. Or what you can do as well if you want to is to look for the radio flash zip file and flash it through custom recovery. Find the radio and kernel flash zip file and it should work as well. Those two files are here on XDA somewhere so you'll have to look for those. If your gonna use custom recovery route I found that twrp works better. I've had problems with cwm and philz.
Click to expand...
Click to collapse
Good call! I flashed the XT1032 GPE onto my device and it worked great!
Question for you though, would my wifi speeds be affected by using this firmware and would using the NON-HLOS.bin and fsg.mbn from the XT1031 firmware make any difference?
Thanks!,
Dan Anderson

Dan2QT said:
Good call! I flashed the XT1032 GPE onto my device and it worked great!
Question for you though, would my wifi speeds be affected by using this firmware and would using the NON-HLOS.bin and fsg.mbn from the XT1031 firmware make any difference?
Thanks!,
Dan Anderson
Click to expand...
Click to collapse
It shouldn't affect your WiFi. If you flashed the right kernel for your device then you won't have a problem. So if you downloaded the kernel for xt1031 and flashed it to a xt1031 then your WiFi will be fine. If you need help to get the radios then go on to google and type in xt1031 radio zip. First link will give you all the radios and kernels and recovery for each moto g model. The zips on that link are to be flashed through custom recovery. Find your device and then send it over to your device and flash. A lot of custom recovery will let you send files in recovery mode.

Have you tried downloading the xt1031 firmware again? May be a bad download. I have never had an issue returning back to stock on the boost variant.

I have the same problem
I have the same problem on the xt1031 just stuck into the screen unlocked bootloader and dont turn on please help mee!!

I need help converting xt1032 back to xt1031
I accidentally flashed xt1032 rom on my boost xt1031 unable to use it as a phone anymore is there anyway I can fix it I currently running GPE 5.1 I want to know if i can flash a xt1031 rom on it to fix it but everything I tried messed up and I would be stuck on a bootloader unlocked screen please help

jwj2ssp said:
I accidentally flashed xt1032 rom on my boost xt1031 unable to use it as a phone anymore is there anyway I can fix it I currently running GPE 5.1 I want to know if i can flash a xt1031 rom on it to fix it but everything I tried messed up and I would be stuck on a bootloader unlocked screen please help
Click to expand...
Click to collapse
Have you tried flashing stock firmware?
http://forum.xda-developers.com/showthread.php?t=3110795
Sent from my XT1031

ATTACK said:
Have you tried flashing stock firmware?
http://forum.xda-developers.com/showthread.php?t=3110795
Sent from my XT1031
Click to expand...
Click to collapse
I have tried flashing stuck many times it either get stuck on bootloader unlocked screen or It boot loops into fastboot I dont know if im doing everything right or im missing something Im going to try the rom from the link you sent me and see if it works thanks in advance

[Q] Stuck at boot screen

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!