Ok, so I've read through the LOOK HERE FIRST thread, I've downloaded RSD Lite (can I still use version 5.5?, can't seem to find a link for 5.6), and I downloaded Motorola_PreRelease_Mobile_Drivers_5.2.1_32bit (again can't seem to find or don't know if I need newer drivers, and don't know what to do with the drivers). I also downloaded the derpunlock.sbf (should this file be only 10.2mb's?). I'm assuming qbking77's tutorial vid is obsolete now since the pudding thread is closed, but can I still follow that video?. Can someone point me in the right direction here? I can't brick this phone.
Airwolf79 said:
Ok, so I've read through the LOOK HERE FIRST thread, I've downloaded RSD Lite (can I still use version 5.5?, can't seem to find a link for 5.6), and I downloaded Motorola_PreRelease_Mobile_Drivers_5.2.1_32bit (again can't seem to find or don't know if I need newer drivers, and don't know what to do with the drivers). I also downloaded the derpunlock.sbf (should this file be only 10.2mb's?). I'm assuming qbking77's tutorial vid is obsolete now since the pudding thread is closed, but can I still follow that video?. Can someone point me in the right direction here? I can't brick this phone.
Click to expand...
Click to collapse
10.2 is correct.
I used this file two days ago:
Code:
Start RSD lite
Reboot phone into RSD mode (power+vol down)
Flash derpunlock.sbf
It may require a battery pull to get the phone to properly reboot
Reboot phone into fastboot mode
Open command prompt in the moto-fastboot folder and do the following:
moto-fastboot devices
moto-fastboot oem unlock
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-red-photon3.img
moto-fastboot reboot
Kevets said:
10.2 is correct.
I used this file two days ago:
Code:
Start RSD lite
Reboot phone into RSD mode (power+vol down)
Flash derpunlock.sbf
It may require a battery pull to get the phone to properly reboot
Reboot phone into fastboot mode
Open command prompt in the moto-fastboot folder and do the following:
moto-fastboot devices
moto-fastboot oem unlock
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-red-photon3.img
moto-fastboot reboot
Click to expand...
Click to collapse
Ok, I don't know why this is so difficult to me. I've flashed tons of roms when I had my evo, and I've tried a few locked roms on this phone, flashed via bootstrap, but this unlock process has me stumped. Where do I get the correct derpunlock.sbf if don't have it? Do I have to flash moto-fastboot from my pc?
From here,
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Kevets said:
From here,
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Click to expand...
Click to collapse
I understood that part, but where do I get the derpunlock.sbf? Is it inlcuded in the Root-Unlock-Relock w 198_7sbf?
Airwolf79 said:
I understood that part, but where do I get the derpunlock.sbf? Is it inlcuded in the Root-Unlock-Relock w 198_7sbf?
Click to expand...
Click to collapse
I'm sorry, I misunderstood your first reply. So I do have the correct derpunlock.sbf then. Ok, I'll give it a whirl. Thank you.
Airwolf79 said:
I'm sorry, I misunderstood your first reply. So I do have the correct derpunlock.sbf then. Ok, I'll give it a whirl. Thank you.
Click to expand...
Click to collapse
Where is the "Unlock" folder located?
Airwolf79 said:
Where is the "Unlock" folder located?
Click to expand...
Click to collapse
I'm pretty sure it's in lokifish's unlock relock pack. If I'm not mistaken it's just a folder that holds everything you need to unlock, so it makes it easier on you.
Sent from my MB855 using xda app-developers app
Can somebody please post or point me to a working link so I can download the files necessary to unlock my bootloader. It appears every link I've tried is either broken or the files are not available anymore...
Sent from my MB855 using xda app-developers app
Here is the unlock and fastboot. Link is temporary.
https://www.box.com/s/92d6ac95e13febbe000d
Kevets said:
Here is the unlock and fastboot. Link is temporary.
https://www.box.com/s/92d6ac95e13febbe000d
Click to expand...
Click to collapse
Why temporary?
My personal account. Can't guarantee they'll be there forever.
Sent from my MB855 using xda premium
Thanks guys, I was able to get it unlocked without the unlock folder. I just used my pc's command prompt directed to fastboot in the sdk tools folder. Much appreciated, now rom flashin like crazy time.
Kevets said:
My personal account. Can't guarantee they'll be there forever.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Okay, thanks much.
Airwolf79 said:
Ok, so I've read through the LOOK HERE FIRST thread, I've downloaded RSD Lite (can I still use version 5.5?, can't seem to find a link for 5.6), and I downloaded Motorola_PreRelease_Mobile_Drivers_5.2.1_32bit (again can't seem to find or don't know if I need newer drivers, and don't know what to do with the drivers). I also downloaded the derpunlock.sbf (should this file be only 10.2mb's?). I'm assuming qbking77's tutorial vid is obsolete now since the pudding thread is closed, but can I still follow that video?. Can someone point me in the right direction here? I can't brick this phone.
Click to expand...
Click to collapse
follow like how qbking's video says just instead of the huge sbf file he flashes in the video you just flash derpunlock.sbf simple
Related
I ran the hboot.zip file (jcase & drewrobinso). The flash worked (kinda) as I do have s-off hboot -1.49.2000, but the fastboot menu is still locked? I sure would appreciate some help... When I am in the fastboot menu, my only choice is using the volume rocker to access the recovery menu.
Thanks
What do you mean its locked? No extra options become available when you have an unlocked bootloader. And how did the flash "kinda" work?
Sent using my rooted HTC Droid Eris with Cyanogen Tazz 7.0 OC'd 787MHz
Irieone said:
I ran the hboot.zip file (jcase & drewrobinso). The flash worked (kinda) as I do have s-off hboot -1.49.2000, but the fastboot menu is still locked? I sure would appreciate some help... When I am in the fastboot menu, my only choice is using the volume rocker to access the recovery menu.
Thanks
Click to expand...
Click to collapse
that sounds about right. if you have the pbooimg file on your sd card, the only other option would be to load that.
orkillakilla said:
What do you mean its locked? No extra options become available when you have an unlocked bootloader. And how did the flash "kinda" work?
Sent using my rooted HTC Droid Eris with Cyanogen Tazz 7.0 OC'd 787MHz
Click to expand...
Click to collapse
that is exactly what i mean. fastboot is highlighted in red. is there not a fastboot menu of some sort?
Sent from my ERIS using XDA App
Jp50 said:
that sounds about right. if you have the pbooimg file on your sd card, the only other option would be to load that.
Click to expand...
Click to collapse
that is what is missing.... ty
Sent from my ERIS using XDA App
Irieone said:
that is exactly what i mean. fastboot is highlighted in red. is there not a fastboot menu of some sort?
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
To my knowledge, there is no special menu.
OTOH, you do have a whole new world of possibilities available to you by using the "fastboot" command on a PC. Since the security mode of the bootloader is now "S-OFF", no security checks are performed by the phone on any of the fastboot commands.
In particular, you can erase partitions, flash them, boot images without flashing them to the phone, and even replace the bootloader with a different bootloader (dunno why you would want to do that unless you were returning the phone, or for the purpose of a "roll-back" experiment.)
After downloading the appropriate fastboot executable (available for Windows/Linux/Mac OSX), type
Code:
fastboot --help
for more information.
You can get fastboot for Windows/Linux/Mac directly from HTC if you like; you don't even need the SDK. (About midway down that page, search for fastboot. Note that the fastboot utility is the only thing on this page you should be downloading - everything else is for a different phone).
bftb0
bftb0 said:
To my knowledge, there is no special menu.
OTOH, you do have a whole new world of possibilities available to you by using the "fastboot" command on a PC. Since the security mode of the bootloader is now "S-OFF", no security checks are performed by the phone on any of the fastboot commands.
In particular, you can erase partitions, flash them, boot images without flashing them to the phone, and even replace the bootloader with a different bootloader (dunno why you would want to do that unless you were returning the phone, or for the purpose of a "roll-back" experiment.)
After downloading the appropriate fastboot executable (available for Windows/Linux/Mac OSX), type
Code:
fastboot --help
for more information.
You can get fastboot for Windows/Linux/Mac directly from HTC if you like; you don't even need the SDK. (About midway down that page, search for fastboot. Note that the fastboot utility is the only thing on this page you should be downloading - everything else is for a different phone).
bftb0
Click to expand...
Click to collapse
ty bftb0.....that is the info i needed
Sent from my ERIS using XDA App
Irieone said:
ty bftb0.....that is the info i needed
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Please, please, please make sure you have read and understood all the information about fastboot before you start messing around with it. since the Security is off you can really mess yourself up with Fastboot.
That said, welcome to the world of S-off, where we say, "whats a softbrick?"
trying to unlock my bootloader and im not able to run the fastboot package i have unzipped to my desktop in C:\Users\chris\Desktop\fastboot-package but first try i entered the wrong unique code and have tried numerous times and cant seem to to get it going again gotta be somthing so simple ill slap my mom when i get the answer
hchris24 said:
ill slap my mom when i get the answer
Click to expand...
Click to collapse
Respect your mum!
Just for that............no answer!
For those all so senisitive plenty of respect for my mom its my noobisim not hers help is much is much appreciated
Do you have ADB installed? Try installing ADB then unzipping the fastboot package into that folder. There are really good directions on xda, or google.
But if you get to the point where you fastboot oem unlock. There should be the unique id number there that you use to unlock...
Also try to reflash the pudding and the fastboot oem unlock command.
Sent from my MB860 using Tapatalk
What happens when you try?
Tried all that but unzipping to adb folder only to desktop will try that tomorrow morn when I get home from work and will repost thanks for the reply
I got all the way to the warranty warning screen entered the id but must of entered.it incorrectly it unlock aborting tried again with redoing reflash all over again and problem is when entering.the first command in adb shell it says wrong path specified that's where im stuck now
What I did was extract these files to : c:\atrix
pudding_183.sbf
adb
adbwinapi.dll
adbwinusbapi.dll
fastboot
IHOP_bell.sbf
moto-fastboot
recovery
I'm not sure if I needed every file but I got done by changing my directory to
cd c:\atrix
then fastboot oem unlock
wrote down the code
then fastboot oem unlock (your # here)
fastboot reboot
Make sure you enter it exactly as it shows on the screen, and yes that does include capitol letters.
That's the only tip I can think of.
Sent from my MB860 using XDA App
Thanks for the last two posts ill try all post back in the morn
this is what i get now after moving everything to one folder cd C:\Users\chris\Desktop\fastboot-package is not recognized as internal or external,
operable command or batch file
hchris24 said:
the first command in adb shell it says wrong path specified that's where im stuck now
Click to expand...
Click to collapse
I could be mis-reading this so if I am I apologize however it seems that you are using the wrong program you need to use the fastboot exe not adb which would be the reason for getting the error messages. (if that is the case)
Prolly not your case, but I extracted the files to a folder so when I typed in their destination, the powers that be couldn't see them where I told them to look...
Sent from my MB860 using XDA Premium App
thanks for the help gentlemen i am now unlocked
So I was trying to flash the new .19 radio and forgot that my volume up button is busted. Does anyone know of anyway to get it to flash without needing to push the volume up button?
Copied from another page using-adb "adb reboot bootloader" – This will reboot the device into HBOOT.
Also found some market apps that might work, but haven't tried any of them.
drowe said:
Copied from another page using-adb "adb reboot bootloader" – This will reboot the device into HBOOT.
Also found some market apps that might work, but haven't tried any of them.
Click to expand...
Click to collapse
Thanks for the response, but booting into the bootloader is not that problem. When the bootloader reads the PG05IMG.zip, it requires you to press volume up to confirm you want to flash it, and see as how my volume up button doesn't work, I can't flash it.
orkillakilla said:
Thanks for the response, but booting into the bootloader is not that problem. When the bootloader reads the PG05IMG.zip, it requires you to press volume up to confirm you want to flash it, and see as how my volume up button doesn't work, I can't flash it.
Click to expand...
Click to collapse
Oh, it's those little details that get you! I read on a forum a while back about an easy way to flash radios with adb. As I recall it had several steps and didn't look any easier to me. My memory and Google are failing me now, but I think there is a way to do it. ADB and fastboot? I know you will find it, I see your name on too many good posts!
Found what I was looking for at cyanogenmod forum, looks like you extract the radio .img file from the zip file and then:
adb reboot-bootloader
it should then say 'fastboot usb' in red when done
type:
fastboot flash radio radio-4.06.00.12_7.img
where radio-4.06.00.12_7.img is the name of the image that you have in the directory you ran the command from.
Here is the post I copied from: http://forum.cyanogenmod.com/topic/1232-how-to-flash-new-radio-image/
Hope that helps!
drowe said:
Oh, it's those little details that get you! I read on a forum a while back about an easy way to flash radios with adb. As I recall it had several steps and didn't look any easier to me. My memory and Google are failing me now, but I think there is a way to do it. ADB and fastboot? I know you will find it, I see your name on too many good posts!
Found what I was looking for at cyanogenmod forum, looks like you extract the radio .img file from the zip file and then:
adb reboot-bootloader
it should then say 'fastboot usb' in red when done
type:
fastboot flash radio radio-4.06.00.12_7.img
where radio-4.06.00.12_7.img is the name of the image that you have in the directory you ran the command from.
Here is the post I copied from: http://forum.cyanogenmod.com/topic/1232-how-to-flash-new-radio-image/
Hope that helps!
Click to expand...
Click to collapse
Sweet I will try it out tonight. Thanks for sharing that!
Sent from my ADR6400L using xda premium
Would that work on 2.3.5 version 45.1.190.MB853.UsC.EN.US ?
Bought the phone used, not sure if it got the OTA update.
All I know it's 2.3.5 and the phone hasn't been used since march...
Thx
brunomcf said:
Would that work on 2.3.5 version 45.1.190.MB853.UsC.EN.US ?
Bought the phone used, not sure if it got the OTA update.
All I know it's 2.3.5 and the phone hasn't been used since march...
Thx
Click to expand...
Click to collapse
no clue for sure. you'll just have to try and unlock it. you can't mess anything up by attempting to do so.
" infooem unlock is not implemented "
That's the error message I get when trying to unlock the bootloader.
The guy who sold it to me said that "hadn't updated it in a while".
So I'm not sure if it's SV1 or SV2 in it. How can I check that?
Anyway, think I'll try the process again to be sure I haven't done anything wrong...
Thx
ps:Can't flash the Slim cause my device is lower then 254_13. And can't flash the Ish rom cause probably it was done the OTA update.
Or wasn't it cause I'm 2.3.5 version 45.1.190? I?m a bit confused right now...
MOF 2.3.5. Slim {locked} De-Blur 4.5.1A-1_SUN-254_13
MOF 2.3.5.ish {locked} - Bootstrap Optimized 7/4/12 - Beta For 2.3.5. Users 7/23/12
na7q said:
no clue for sure. you'll just have to try and unlock it. you can't mess anything up by attempting to do so.
Click to expand...
Click to collapse
http://www.motosunfire.com/2-3-5-bl/
I have tried ur website tutorial to unlock the bootloader. Everything works fine until I get to the 1º fastboot comand. It tells me (command write failed(unknown error))
It's a diferent error from the one I got when tried out with the pudding method.
Could that mess up this process right now? How can I roll it back?
Just to be sure, this device is already rooted with superuser installed too.
The way I see the device was already shiped with 2.3.5 (have no longer contact with previous owner). But there's something I'm clearly missing out...
brunomcf said:
" infooem unlock is not implemented "
That's the error message I get when trying to unlock the bootloader.
The guy who sold it to me said that "hadn't updated it in a while".
So I'm not sure if it's SV1 or SV2 in it. How can I check that?
Anyway, think I'll try the process again to be sure I haven't done anything wrong...
Thx
ps:Can't flash the Slim cause my device is lower then 254_13. And can't flash the Ish rom cause probably it was done the OTA update.
Or wasn't it cause I'm 2.3.5 version 45.1.190? I?m a bit confused right now...
MOF 2.3.5. Slim {locked} De-Blur 4.5.1A-1_SUN-254_13
MOF 2.3.5.ish {locked} - Bootstrap Optimized 7/4/12 - Beta For 2.3.5. Users 7/23/12
Click to expand...
Click to collapse
I'm not sure how you can check what you have. You can flash the locked ROMs above regardless. Or any locked ones really. As for it having 2.3.5 on it, it doesn't mean it was shipped with it. It could have been flashed with the only known 2.3.5 SBF that permanently locks it for good just like the OTA update.
Sent from my MB853 using XDA
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
brunomcf said:
http://www.motosunfire.com/2-3-5-bl/
I have tried ur website tutorial to unlock the bootloader. Everything works fine until I get to the 1º fastboot comand. It tells me (command write failed(unknown error))
It's a diferent error from the one I got when tried out with the pudding method.
Could that mess up this process right now? How can I roll it back?
Just to be sure, this device is already rooted with superuser installed too.
The way I see the device was already shiped with 2.3.5 (have no longer contact with previous owner). But there's something I'm clearly missing out...
Click to expand...
Click to collapse
Do you mean the first fastboot command? Do you have files in the right folder? Did you point command prompt to the folder?
Sent from my MB853 using XDA
"Now to see if you can do a ramboot to unlock your device. Run these commands in order.
If that worked then your screen will have the Motorola logo with dual core technology underneath.
fastboot flash rdl.bin RDL3_unlocked.smg"
This step has worked perfectly. But the next hasn't "fastboot oem unlock".
It tells me (command write failed(unknown error)).
I've realized Rom manager Premium 5028 is instaled and flashed into the phone. Tried to reboot recovery but it doesn't work. Tells me "Error 2" I think.
Could Rom Manager be blocking this process somehow? I'll unistall it cause its no good for me at this point...
edit: Just removed the Clockworkmod, and I keep getting the same error.
If the boot loader was unlockable, it wouldn't pass "fastboot flash rdl.bin RDL3_unlocked.smg" command sucessfully right?
brunomcf said:
"Now to see if you can do a ramboot to unlock your device. Run these commands in order.
If that worked then your screen will have the Motorola logo with dual core technology underneath.
fastboot flash rdl.bin RDL3_unlocked.smg"
This step has worked perfectly. But the next hasn't "fastboot oem unlock".
It tells me (command write failed(unknown error)).
I've realized Rom manager Premium 5028 is instaled and flashed into the phone. Tried to reboot recovery but it doesn't work. Tells me "Error 2" I think.
Could Rom Manager be blocking this process somehow? I'll unistall it cause its no good for me at this point...
edit: Just removed the Clockworkmod, and I keep getting the same error.
If the boot loader was unlockable, it wouldn't pass "fastboot flash rdl.bin RDL3_unlocked.smg" command sucessfully right?
Click to expand...
Click to collapse
i think i know the problem! my info was courtesy of teamuscellular. i did not fully verify it.
so try it like this. good luck!
5. fastboot flash rdl.bin RDL3_unlocked.smg
6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock
This will display device unique id if found.
7. Now run the the same command adding your device id.
fastboot.exe oem unlock UniqueIdHere
8. Now issue the command.
fastboot.exe reboot
---------- Post added at 12:18 PM ---------- Previous post was at 12:10 PM ----------
na7q said:
i think i know the problem! my info was courtesy of teamuscellular. i did not fully verify it.
so try it like this. good luck!
5. fastboot flash rdl.bin RDL3_unlocked.smg
6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock
This will display device unique id if found.
7. Now run the the same command adding your device id.
fastboot.exe oem unlock UniqueIdHere
8. Now issue the command.
fastboot.exe reboot
Click to expand...
Click to collapse
let me know if you get anything. be sure all files are in the C:\electrify directory (if that's what you're using). be sure the phone is in fastboot mode.
"6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock"
You mean C:\electrify on command prompt?
I've hit shift + right mouse button and then open command prompt to get into that location
I still get the same error. Starting to think it really got an Rsd or OTA update before coming into my hands.
Just wounder why does it go through step 5 and not the rest of them...
brunomcf said:
"6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock"
You mean C:\electrify on command prompt?
I've hit shift + right mouse button and then open command prompt to get into that location
I still get the same error. Starting to think it really got an Rsd or OTA update before coming into my hands.
Just wounder why does it go through step 5 and not the rest of them...
Click to expand...
Click to collapse
maybe typing the command incorrectly. corrupt files? could be something along those lines.
only have found one person with an unknown error. still looking at that. it's entirely possible you are locked.
here's the error most users get.
"1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb"
That's exactly what I was getting on the phone.
Thought you were refering to the command prompt window.
As it shown the dual core logo, thought I was fine on this step.
Seems that my phone is permalocked, right?
Sorry for wasting your time. Thanks
ps: will try the Peetr’s 2.3.5 Hybrid (Stock/CM7) cause I had no service with none of the Mof's roms. Neither the Sim, or Ish worked ok. Had no wireless service in any of them...
na7q said:
maybe typing the command incorrectly. corrupt files? could be something along those lines.
only have found one person with an unknown error. still looking at that. it's entirely possible you are locked.
here's the error most users get.
"1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb"
Click to expand...
Click to collapse
My beloved rezound has gone kaput.
I had clean rom on my phone until it stopped booting past the white HTC screen.
I decided to flash a new rom on the phone, as I couldn't seem to find the version of clean rom I had before.
My question is: Is there any way to flash the new boot.img from the phone itself? Or is it required to be connected to the computer itself?
To repair my phone it looks like the only thing I can do is re-flash Clean Rom (Because of the boot.img)
Is this true?
Thanks for any help in advance!
mainmanluke said:
My beloved rezound has gone kaput.
I had clean rom on my phone until it stopped booting past the white HTC screen.
I decided to flash a new rom on the phone, as I couldn't seem to find the version of clean rom I had before.
My question is: Is there any way to flash the new boot.img from the phone itself? Or is it required to be connected to the computer itself?
To repair my phone it looks like the only thing I can do is re-flash Clean Rom (Because of the boot.img)
Is this true?
Thanks for any help in advance!
Click to expand...
Click to collapse
You can boot the phone into hboot and flash the boot.img from fastboot on your computer, but you'd be hard pressed to do it without a PC
AshtonTS said:
You can boot the phone into hboot and flash the boot.img from fastboot on your computer, but you'd be hard pressed to do it without a PC
Click to expand...
Click to collapse
Following what procedure exactly? adb devices brings up nothing when the phone is in HBOOT mode. I'm assuming you
don't use the same method as you would with an RUU or radio?
Apologies for my stupidity, I seem to be mixing this up.
(Plus I'm stressed because I have an interview with google tonight )
mainmanluke said:
Following what procedure exactly? adb devices brings up nothing when the phone is in HBOOT mode. I'm assuming you
don't use the same method as you would with an RUU or radio?
Apologies for my stupidity, I seem to be mixing this up.
(Plus I'm stressed because I have an interview with google tonight )
Click to expand...
Click to collapse
You'll need to use fastboot rather than adb (same general procedure tho)
Make sure to highlight the fastboot tab in hboot and press the power button to select it, then on your computer type "fastboot flash boot <path to boot.img>" then when it finishes, "fastboot reboot" and you should be good.
Good luck with your interview
Adb is really great for pushing and pulling files from your system or sdcards. Flashing stuff is great for fastboot.
AshtonTS said:
You'll need to use fastboot rather than adb (same general procedure tho)
Make sure to highlight the fastboot tab in hboot and press the power button to select it, then on your computer type "fastboot flash boot <path to boot.img>" then when it finishes, "fastboot reboot" and you should be good.
Good luck with your interview
Click to expand...
Click to collapse
Well, I seem to be stuck at "< waiting for device >" even when in fastboot :/ Any ideas?
Also, talking to the hiring manager tomorrow, will be with Google soon
mainmanluke said:
Well, I seem to be stuck at "< waiting for device >" even when in fastboot :/ Any ideas?
Also, talking to the hiring manager tomorrow, will be with Google soon
Click to expand...
Click to collapse
make sure your PC has the drivers installed. The ones for fastboot are different but should've been installed with the adb drivers. Check Windows Device Manager for anything that might not have installed correctly.
Also make sure you open the command prompt with admin privileges if you're running vista/7.
You should be able to write a boot image via hboot with a PH98IMG.zip on your sdcard. That way you don't need a computer.