Related
Hi all ...
Excuse me for my bad english, i'm french ....
I have a big problem with my nexus one.
I would like to flash the latest cyanogen Nightly but since the V243 i have a error 7 when the phone try to update the boot.img ....
After a long search on the web , i found that the problem is probably that i have a bad sector on my boot partition.
to Fix this problem i have to update my bootloader with the Hboot 0.35 ....
My question are how can i update my bootloader ???? i have tried to flash the PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_signed.zip in Clockword recovery but it say that the package is bad ...
Please help ... thx
Extract the hboot.img from the ROM ZIP.
Reboot to bootloader.
Execute:
"fastboot flash hboot hboot.img".
You need fastboot set up for this. Read Wiki to know, how to set it up.
No need to unlock the bootloader, the IMG is original and signed.
thanks for your answer
but i don't have a hboot.img on the package only a hboot_8x50_0.35.0017_100610.nb0 .
when i tried to fastboot flash hboot hboot_8x50_0.35.0017_100610.nb0 it doesn't work ..
Where can i find this hboot.img ?
I have rename hboot_8x50_0.35.0017_100610.nb0 at Hboot.img
When i try to fastboot flash hboot hboot.img i have the following error
C:\android\tools>fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY [ 0.087s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.210s
By the output I see that your bootloader indeed is still locked.
Oh well, since the simple way didn't work - here's a very long, but certain way:
Download UniversalAndRoot.
Reboot to recovery.
Make a FULL NANDROID BACKUP.
[executing "unroot/restore your Nexus from Wiki, PASSIMG method]
Rename your Korean ROM file to PASSIMG.ZIP
Put it on SD card in root directory.
Reboot to bootloader.
Press whatever needed to flash the PASSIMG.
[end of PASSIMG method]
DO NOT LOGIN TO ANY SERVICE!
Execute: "adb install universalandroot.apk" (replace with the actual APK filename)
Root the phone
Install custom recovery (use flash_image guide from Wiki)
Reboot to recovery
Restore nandroid backup you've made.
After all that, you'll have your HBOOT changed, and the ROM with your data as they were.
Its original korean rom, i think you cant flash it because:
1)Bootloader still locked. Korean nbh signed with key came from KT so there is nothing surprsing it says "Signature verify fall"
2)Custom recovery from RAmon wouldnt flash it too. I have no idea why, but seems like flash original roms just forbidden in RAmon's custom recovery. Dont know about Clockworks one
Where are you device came from?
If its an american one, download latest full american rom and flash it.
I hope it would help.
Another, shortest way: unlock your bootloader and flash whatever you want
I see that most CM7's require the new hboot. I have flashed, pushed, fastbooted, just about anything you can do with ADB and am quite comfortable with it but i can't find anywhere the instructions on just "how to" flash the new hboot to the N1. Is it as easy as placing the zip on the sd and flashing through recovery or is there more to it? I even tried looking in the Wiki and it showed the newest hboot but not how to flash. Thanks in advance!!
I thought it was possible to flash from recovery but after some digging around i'm not so sure now. Best to check with somebody who has done this
I flashed new hboot using cw recovery just this morning. No worries.
Thanks for the reply!
fastboot flash hboot whatever_hboot_you_want.img
Hi, am trying to flash my HBOOT, downloaded d6096cac5e9f.signed-hboot-0.35.0017.zip and currently trying to flash but getting this error:
Code:
$ ./fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
The phone is unlocked and fastboot can see the device, any ideas?
braingravyuk said:
Hi, am trying to flash my HBOOT, downloaded d6096cac5e9f.signed-hboot-0.35.0017.zip and currently trying to flash but getting this error:
Code:
$ ./fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
The phone is unlocked and fastboot can see the device, any ideas?
Click to expand...
Click to collapse
I think what they are saying is you can flash that .zip through clockwork and not worry about fastboot. Try that and let me know if that works for you.
just disable verification check and then flash. worked for me
Just in the process of rooting the phone... just rooted it and about to install RA recovery.. guess I'll flash it through that
Just tried to flash in RA Recovery got the following:
Code:
Install:d6096cac5e9f.signed.hboot-0.35.0017.zip?
Press Trackball to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (8 files)
E: Verification failed
Zip verification failed!
Zip isn't signed correctly!
Installation aborted.
Surely if the thing is signed then there shouldn't be a problem with the signature?
Check the md5 on the file...
Sent from my Nexus One using XDA App
Hi,
the md5sum is coming back with:
Code:
b0669d79f3ace07fdd3e1c03d88d2c68 d6096cac5e9f.signed-hboot-0.35.0017.zip
tah318 said:
just disable verification check and then flash. worked for me
Click to expand...
Click to collapse
Try this in AR recovery and see if you can flash then.
In AR recovery main menu select flash zip, then in that menu under "select zip" is toggle verification. Select that once and you will get a warning that unsinged zip can corrupt. then you can choose "select zip" and flash the hboot zip from the sd card.
Jack_R1 said:
fastboot flash hboot whatever_hboot_you_want.img
Click to expand...
Click to collapse
I don't think that's correct. It should be: fastboot flash misc whatever_hboot_you_want.img
Sent from my Nexus One using XDA App
braingravyuk said:
Hi,
the md5sum is coming back with:
Code:
b0669d79f3ace07fdd3e1c03d88d2c68 d6096cac5e9f.signed-hboot-0.35.0017.zip
Click to expand...
Click to collapse
Thanks for the tip, just wondering if anyone can confirm the md5sum, there isn't one shown on the sticky for kernels and radios.
Cheers
braingravyuk said:
Thanks for the tip, just wondering if anyone can confirm the md5sum
Click to expand...
Click to collapse
That's the correct value. Note that the d6096cac5e9f is the prefix of the sha1 checksum.
efrant said:
I don't think that's correct. It should be: fastboot flash misc whatever_hboot_you_want.img
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Im 100% sure its fastboot flash hboot whicheverhboot.img
your way may or may not work but this way does
deleted...
HI
Im trying to upgrade my nexus to gingerbread stock according to the guids in the dev section
I understand that u need hboot 35 in order to do so.
im currently using hboot 0.33.0012
and stock rooted froyo 2.2.2 with unlocked bootloader
as i enter fastboot on my phone and try the command
fastboot flash hboot hboot.img
I get the following output
sending 'hboot' (512 KB)... OKAY [ 0.085s]
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 0.279s
does anyone know why do I get "remote : not allowed"?
thanks!
edit: can I skip this step or do I must upgrade hboot?
and can I upgrade it with a zip through the latest amon ra recovery?
edit2: I found an update zip containing only the hboot ver 35 and when I try to flash it
it says its unsigned and installation aborted...
should I try cancelling sign checking through recovery or is it too risky?
come one guys I really need some help here...
I have the same issue, never been able to solve it.
You can find a zip to the .37 hboot, I think in one of the GB 2.3.3 threads. (IIRC, it was craigacgomez's) If you are getting an unsigned error, turn off the signature verification in your recovery. I used the same zip, and all was fine. If you can't find the zip file, let me know. I most likely still have it.
UPDATE: here is the link craigacgomez provided for the flashable, zip hboot. http://android.clients.google.com/packages/ota/passion/d6096cac5e9f.signed-hboot-0.35.0017.zip
If it still fails, turn off signature verification.
Are you sure your bootloader is unlocked? People usually get those errors when it is locked, or they are trying to flash a .zip file instead of an.img file.
Using recovery is fine to flash HBOOT. Link to the .zip is in my signature.
Solved
I managed to solve the problem by finding a flash zip file. like mentioned above, before the comment was written.
and I took off the signature check myself, without knowing that itll go through fine
except from that the radio upgrade, and gingerbread installation went fine, finally I have 2.3.3 on my phone!!
thnks a lot anyway. I still wonder what is the cause for this error, as my bootloader is unlocked for sure, and I even tried
fastboot oem unlock
one more to be sure (which failed, as it stated that it is already unlocked)
I was getting the same error trying to flash to the .37 hboot from fastboot. My bootloader has been unlocked since I took the phone out of the box.
You guys were at the fastboot screen, right?
Sent from my Nexus One using XDA Premium App
Yea, I have used fastboot a few thousand times. Was found by fastboot devices. Just gave errors every time I tried to flash it. The zip worked fine though. Never had any problems flashing anything else through fastboot.
Yeah, I figured I was grasping at straws, but thought I'd ask anyway...
Sent from my Nexus One using XDA Premium App
my phone is stock, can access bootloader manually ok (power button and volume down button), but does not access recovery, red triangle and exclamation mark! when trying to access recovery.
Can recovery be installed on a stock phone? I wish to backup my default rom before rooting and moding.
You need to flash a recovery.img I recommend TWRP or Clockwork touch. Search it up here :3
i get this error when trying to flash recovery.img via fastboot.
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.489s
i need recovery installed to backup default rom before i unlock!
is there another way to backup rom on unrooted unlock phone?
found ultimate backup tool for windows..
http://forum.xda-developers.com/showthread.php?t=1844032
stevengw said:
i get this error when trying to flash recovery.img via fastboot.
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.489s
i need recovery installed to backup default rom before i unlock!
is there another way to backup rom on unrooted unlock phone?
found ultimate backup tool for windows..
http://forum.xda-developers.com/showthread.php?t=1844032
Click to expand...
Click to collapse
So is everything ok with you now ? Or do you still need help ?
that problem comes when either bootloader is unlocked or you do the wrong command fastboot flash recovery [then name of desired recovery.img]
whoamigriffiths said:
So is everything ok with you now ? Or do you still need help ?
Click to expand...
Click to collapse
I was unable to get ulitmate backup tool to work, "adb server out of date." errors.
I'm sure(or at least hoping) this has been answered elsewhere, but after 6 hours of searching I'm in desperation mode. Here's where I'm at:
Brand new Sprint M8 HK edition
cid: SPCS_004
version_main: 1.54.654.13
modelid: 0P8B70000
radio: 1.05.20.0321_2
Rooted with SuperSU, TWRP 2.8.1 (2.8.3 won't work, gets stuck on loading recovery), S-ON
I thought I could flash http://forum.xda-developers.com/showthread.php?t=2706441 without being S-off, and stupidly did not make a backup. Flashing appeared to go fine, but after rebooting the phone goes straight to the bootloader. I can still access TWRP, and have tried to flash multiple ROM's/Firmware to get the phone in any working config, but no matter what I do I can't get anything to flash.
If I try to flash 1.54.654.9 Full Firmware from RUU from http://forum.xda-developers.com/showthread.php?t=2729173 I get the FAILED (remote: 99 unknown fail) error. Research said to lock the bootloader, which I did, but then I get the FAILED (remote signature verify fail).
The ultimate goal is to get stock android running on the M8(recently lost my Nexus 5 which I loved), but at this point I'd take any working OS so I can simply use the phone.
I've been using fastboot to flash as I don't have ready access to a microSD card reader.
Any help would be greatly appreciated, and met with BTC tips.
Download the ROM from the link below. Make sure you do a full wipe in recovery first. Then flash the ROM.
https://www.androidfilehost.com/?fid=23329332407590598
The full firmware you're attempting to install won't install because you're S-on and you cannot downgrade firmware while S-on. If this doesn't work you'll need to relock your bootloader and flash the latest RUU from the link you posted (software version 3.31.654.2).
Magnum_Enforcer said:
Download the ROM from the link below. Make sure you do a full wipe in recovery first. Then flash the ROM.
The full firmware you're attempting to install won't install because you're S-on and you cannot downgrade firmware while S-on. If this doesn't work you'll need to relock your bootloader and flash the latest RUU from the link you posted (software version 3.31.654.2).
Click to expand...
Click to collapse
Thanks for the reply. Downloaded the ROM you linked, got the following:
$ sudo fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49586 KB)...
OKAY [ 3.070s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 3.071s
Is that expected?
Yes, that's expected, because that's not how you flash a ROM.
Can you push the ROM to your phone and then try flashing it via recovery? You mentioned not having a microSD card reader but I presume you have a microSD card, correct? If so push the ROM to the card, do a full wipe in recovery (Dalvik cache, cache, data & system), then flash the ROM.
Magnum_Enforcer said:
Yes, that's expected, because that's not how you flash a ROM.
Can you push the ROM to your phone and then try flashing it via recovery? You mentioned not having a microSD card reader but I presume you have a microSD card, correct? If so push the ROM to the card, do a full wipe in recovery (Dalvik cache, cache, data & system), then flash the ROM.
Click to expand...
Click to collapse
Thanks for trudging along with me, still learning here. I pushed the ROM you linked to my sdcard via adb, did a full wipe, and went to install:
Installing ' /sdcard/firmware.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat " /system/build.prop": No such file or directory
E:Error executing updater binary in zip '/sdcard/firmware.zip'
Error flashing zip '/sdcard/firmware2.zip'
I was able to flash the GPe ROM successfully using this method, but my phone still reboots to bootloader...
Odd.
At any rate, you're going to need to update your firmware, otherwise you won't be able to properly run the GPE port to begin with.
Thanks again. I was able to recover to stock image with the RUU you suggested. Do you have any suggestions/links for ROMS with stock android? And do you have a BTC address?
You can take a look at the thread in the link below (the first post, actually).
http://forum.xda-developers.com/showthread.php?t=2729173
I don't have a BTC address.