Database Develop

Signature Verification Fail in flashing any Blackrose Hboot

I attempted to flash ICS rom for my N1 and I know installation of Blackrose is required.
I attempted to use Blackrose.exe but it doesn't work, then I trun to flash the cutsome hboot by manual in command prompt.
But the problem is I get the signature verfiication failed when I tried to flash any hboot_xxxxx.nb0 files by fastboot.
I have searched some relevant threads but no clear solution was found. (Some threads have posted the similar question but all the replies are problem solved without clear explanation.)
Any anybody can advise me ? How can I pass the signature verification in fastboot ?

hthsolstice said:
I attempted to flash ICS rom for my N1 and I know installation of Blackrose is required.
I attempted to use Blackrose.exe but it doesn't work, then I trun to flash the cutsome hboot by manual in command prompt.
But the problem is I get the signature verfiication failed when I tried to flash any hboot_xxxxx.nb0 files by fastboot.
I have searched some relevant threads but no clear solution was found. (Some threads have posted the similar question but all the replies are problem solved without clear explanation.)
Any anybody can advise me ? How can I pass the signature verification in fastboot ?
Click to expand...
Click to collapse
Are you using RA recovery? While in recovery, select Flash zip from SD card, then select Toggle signature verification to turn off

You can't just flash "improper" HBOOT from fastboot, even if you have unlocked bootloader. HBOOT is still protected. There's a procedure that's needed to flash it, some script, I don't remember exactly what. Please look it up.

taodan: It is not the problem in the recovery, I can't write on the "hboot" in the bootloader
Jack_R1: Yes, that's I wanted to find out......

Try this if you haven't--of course nandroid first
Download latest Blackrose to PC and extract it
Open it and go to the binary folder
Copy the two files below to you fastboot.exe folder. Mine is in tools of my SDK
Do following
1) Boot into fastboot mode on your device, and plug it in to your computer.
2) Boot the exploit: fastboot boot go2.lol
3) Flash the modified hboot: fastboot flash hboot hboot_blackrose.nb0
You need to reboot your bootloader (fastboot reboot bootlloader) and check that it shows Blackrose installed and s-off
You still need to modify the hboot to ICS partition sizes, I use splhexeditor
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
Also, what rom are you coming from. BR won't install over Sense roms
Somewher in thread dev mentions that if you can't install by selecting bootloader unlocked try locked and see if it works. Forget where that was and for what problem it was for.

Thanks a lot ! I can flash ICS rom now !!!
rugmankc said:
Try this if you haven't--of course nandroid first
Download latest Blackrose to PC and extract it
Open it and go to the binary folder
Copy the two files below to you fastboot.exe folder. Mine is in tools of my SDK
Do following
1) Boot into fastboot mode on your device, and plug it in to your computer.
2) Boot the exploit: fastboot boot go2.lol
3) Flash the modified hboot: fastboot flash hboot hboot_blackrose.nb0
You need to reboot your bootloader (fastboot reboot bootlloader) and check that it shows Blackrose installed and s-off
You still need to modify the hboot to ICS partition sizes, I use splhexeditor
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
Also, what rom are you coming from. BR won't install over Sense roms
Somewher in thread dev mentions that if you can't install by selecting bootloader unlocked try locked and see if it works. Forget where that was and for what problem it was for.
Click to expand...
Click to collapse

hthsolstice,
No problem just hit Thanks--

Removing warning bootloader unlocked

hi
i unlocked my bootloader and then i reflash thr original firmware and lock the bootloader succesfully
but the red warning of bootloader unlocked still is present every time i power on my moto x
some help?
thank u
( i tried with a original logo from Moto g but got a weird image with all blured lines)

There's a thread for this. It's not difficult to find.

nhizzat said:
There's a thread for this. It's not difficult to find.
Click to expand...
Click to collapse
/// solved
thank u

danger2u said:
/// solved
thank u
Click to expand...
Click to collapse
How did you solve it because no matter what I do the warning still there .... Thanks

aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy

aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
danger2u said:
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy
Click to expand...
Click to collapse
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.

KidJoe said:
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
Click to expand...
Click to collapse
this was tested and working great on Moto x xt1053
is the same logo as before the unlocked bootloader
i just want to help
if my thread is not helping u can close it

[Q] HELP PLEASE Deleted OS cant install rom

I was trying to install ViperOne and everything went south. I somehow deleted my OS in the process. ADB is not working it only freezes my computer. I was able to ADB Push my viperone.zip but I tried the install and it fail for some reason and now it seems to be in a boot loop please help me with this.

also
i have been read all threads on here and there not really helping. just want to put that out there so i dont get called lazy for not searching.

1. Fix ADB issues.

SaHiLzZ said:
1. Fix ADB issues.
Click to expand...
Click to collapse
not sure of the reason for the freezing om the computer.

MuskRat40 said:
not sure of the reason for the freezing om the computer.
Click to expand...
Click to collapse
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?

alray said:
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.206.1
eMMC-BOOT 2048MB
I rooted my phone with the Hasoon2000 AIO kit
downloaded ViperOne5.5.0 from the link Here on XDA
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library my OS was one of the things to go.
ADB pushed Viper back onto phone tried to install again and failed
tried to reboot and its a loop only thing opening now is fastboot and hboot
recovery flashes on for a sec then its gone.

fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7

MuskRat40 said:
I rooted my phone with the Hasoon2000 AIO kit
Click to expand...
Click to collapse
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
MuskRat40 said:
downloaded ViperOne5.5.0 from the link Here on XDA
Click to expand...
Click to collapse
Did you downloaded the M7 version of viperone or the sprint version?
MuskRat40 said:
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library
Click to expand...
Click to collapse
Take your time and don't rush, you will make things worse.
please answer all my questions:
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
MuskRat40 said:
fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7
Click to expand...
Click to collapse
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?

alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
Click to expand...
Click to collapse
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff

alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?
Click to expand...
Click to collapse
md5?? not sure how to do that

MuskRat40 said:
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff
Click to expand...
Click to collapse
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.

alray said:
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.
Click to expand...
Click to collapse
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.

MuskRat40 said:
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.
Click to expand...
Click to collapse
np, glad it worked
hope you learned this:
don't use toolkit
don't rush
newer roms don't like old recoveries (especially 4.4 roms) So in the future be sure to update your recovery to latest version (or that one specified in the rom thread) before flashing.
hope you'll enjoy your new rom :highfive:

Stock RUU need help

Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome

ubas98 said:
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
Click to expand...
Click to collapse
post the ouput of "fastboot getvar all" except the IMEI and SERIALNO so we can help you determine which RUU you can use if any available for your phone.

M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me

ubas98 said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
Click to expand...
Click to collapse
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?

Seanie280672 said:
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Click to expand...
Click to collapse
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do

ubas98 said:
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
Click to expand...
Click to collapse
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.

Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?

ubas98 said:
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
Click to expand...
Click to collapse
password ? never seen that before, could you post a photo of it ?

Seanie280672 said:
password ? never seen that before, could you post a photo of it ?
Click to expand...
Click to collapse
http://postimg.org/image/ucolu3a83/ here is the img

ubas98 said:
http://postimg.org/image/ucolu3a83/ here is the img
Click to expand...
Click to collapse
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that

Seanie280672 said:
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Click to expand...
Click to collapse
maybe i could use another recovery .if yes anny what is other best recovery?

ubas98 said:
maybe i could use another recovery .if yes anny what is other best recovery?
Click to expand...
Click to collapse
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?

ubas98 said:
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
Click to expand...
Click to collapse
adb push it straight to the sdcard, make sure your phone is plugged into the computer and the rom is in the same folder as adb and fastboot files, then issue this command:
Code:
adb push (name of rom).zip /sdcard/
it will look like its not doing anything but will let you know when its done, then uplug your phone before flashing the rom.
and both TWRP and CWM have their good points, you need CWM to flash AOSP rom's and TWRP to flash sense rom's

Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.

SGSII_LEDnotify said:
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
Click to expand...
Click to collapse
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?

Seanie280672 said:
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Click to expand...
Click to collapse
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.

SGSII_LEDnotify said:
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
Click to expand...
Click to collapse
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.

Seanie280672 said:
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Click to expand...
Click to collapse
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete

SGSII_LEDnotify said:
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
Click to expand...
Click to collapse
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.

Seanie280672 said:
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Click to expand...
Click to collapse
I renamed the zip file because there were spaces in the name causing errors, would that cause a failure when trying to install?
skipping MD5 check: no md5 file found
Error flashing zip '/sdcard/****.zip'
updating partition details
failed

Locked bootloader while trying to unbrick failed rom flash

I'm having a really hard time getting this OP3t to do what I want.
Didn't flash su after trying to manually update to 4.0.2
Constantly tried to flash a new rom, would get stuck at patching system
Tried to use unbrick solution, flashed stock recovery
Upon completion of unbrick solution my bootloader is locked and i cannot get into recovery because md5 checksum fail when booting.
I've tried using the unbricking solution probably 10 times with no change.
I have searched among the threads which have not be helpful enough to solve my solution.
right now it says modem, boot and system failed md5 checksum and just constantly reboots.
Also, phone is not being recognized now in fastboot mode
What do I do???

First of all try to open phone in fastboot mode then connect your cable to pc.
1. Download full stock rom of oos try 4.0.1.
2. use command to lock the bootloader
fastboot oem lock;
3. then flash stock recovery of nouguat 7.0 through fastbootmode .
fastboot flash recovery image.filename.
4. then go to stock recovery and flash full rom zip using adb sideload.
All done and best of luck......
If facing any problem then ask

shubham8166410 said:
First of all try to open phone in fastboot mode then connect your cable to pc.
1. Download full stock rom of oos try 4.0.1.
2. use command to lock the bootloader
fastboot oem lock;
3. then flash stock recovery of nouguat 7.0 through fastbootmode .
fastboot flash recovery image.filename.
4. then go to stock recovery and flash full rom zip using adb sideload.
All done and best of luck......
If facing any problem then ask
Click to expand...
Click to collapse
I'm getting the wont load problem when trying to flash, advice?

Place all the zip file in same folder of adb driver than try to flash it
---------- Post added at 05:58 PM ---------- Previous post was at 05:58 PM ----------
Is your phone booting in fast mode or nkt

shubham8166410 said:
Place all the zip file in same folder of adb driver than try to flash it
---------- Post added at 05:58 PM ---------- Previous post was at 05:58 PM ----------
Is your phone booting in fast mode or nkt
Click to expand...
Click to collapse
NKT? Not sure what that means.
It is going to fastboot however if i list adb devices nothing shows up.
It does respond with bootloader already locked when i try to send that command

Type command fastboot devices
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Then it will show device then only u can procceed further

shubham8166410 said:
Type command fastboot devices
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Then it will show device then only u can procceed further
Click to expand...
Click to collapse
Nothing is coming up when I do that, it just returns to the original command prompt line

Can u able to flash phone in fastboot mode or not

shubham8166410 said:
Can u able to flash phone in fastboot mode or not
Click to expand...
Click to collapse
I was able to use the unbrick method from another computer. Thank you for your assitance