Database Develop

[Q] fastboot flash doesn't work

I am trying to burn stock ROM images on my Nexus One. I am trying to follow instructions in this tutorial http://forum.xda-developers.com/showthread.php?t=614850 but can't get fastboot to flash my ROM with the images nor erase the userdata partition.
When trying
-> fastboot erase userdata
I get "FAILED (remote: not allowed)" message and when trying
-> fastboot flash userimage.img
I get "sending 'userdata' (837 KB)..." but nothing happens even after 10 minutes... This is the same when trying to flash system and boot partition as well.
I can see my device and reboot it using
-> fastboot devices
-> fastboot reboot-bootloader
My HBOOT version is 0.33.0012 and I have this S-ON (can't quite figure out what this means)...
Any ideas?

When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.

Hollow.Droid said:
When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.
Click to expand...
Click to collapse
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.

smichak said:
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.
Click to expand...
Click to collapse
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?

Did you run 'fastboot oem unlock' first?

Rusty! said:
Did you run 'fastboot oem unlock' first?
Click to expand...
Click to collapse
I am pretty sure my phone is unlocked as I see this open lock icon whenever I reboot it.

Hollow.Droid said:
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?
Click to expand...
Click to collapse
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...

smichak said:
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...
Click to expand...
Click to collapse
There was but I can't put my finger on it at the moment. However I used this exact method a couple of days ago so it's still fresh:
1) Download FRG33 image format from here. Versions above this as far as I know cannot use the PASSIMG.zip method.
2) Rename to PASSIMG.zip and place in the root of the sd card
3) Reboot/boot to bootloader
4) At this point the phone will recognise the zip file and check its contents.
5) When prompted press the volume button to confirm.
This will return you to stock (Minus the recovery but from the sounds of it you don't have a custom recovery image).

You have to extract the FRG33 file and then rename the new file passimg.zip

OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?

smichak said:
OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?
Click to expand...
Click to collapse
Using fastboot, flash the custom recovery of your choice. Using that recovery, flash the custom GB ROM of your choice.

[Q] Can't boot into recovery HTC one

Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image

Have you tried
fastboot erase cache

BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"

ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery

Is fast boot off?

Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium

hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system

C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets

Did you try various recovery (versions) ? May be , you just have corrupted recovery image.

tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results

Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.

tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757

Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.

Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager

tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?

I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.

Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process

tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.

You quoted me, but answered not to me.
Read a post #26 from my link above

Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know

[GUIDE] Returning to 100% Stock for O2-UK Customers

Hi All,
I have merely followed the instructions of other devs here to get my phone back to complete stock O2. I believe this guide could work for other carrier based models as well
Mods - Feel free to post this wherever or make any changes.
These are the steps I took to get back to S-ON, reset the ***TAMPERED*** flag and lock the bootloader. The reason why I post this is because I had several issues getting back to stock, and this is for anyone who is having the same issues
I had several scary messages when going back to S-ON when I thought I was completely stock, which included the "Security Warning" message in bootloader when running fastboot oem writesecureflag 3. I also had a message when booting up the stock ROM in 3.62.206.1 saying "TAMPER DETECTED - REBOOTING after trying fastboot oem writesecureflag 3. Once in bootloader, the tampered message re-appeared and I was S-ON and LOCKED. After running all the steps, I have been able to reboot several times and factory reset without the ***TAMPERED*** reappearing
Step 1: Getting S-off
If you are using bootloader 1.44 - Use Revone http://forum.xda-developers.com/showthread.php?t=2314582
For bootloaders 1.5x you should download the Sunshine app at http://theroot.ninja/
The closer you are to stock ROM/stock kernel the better. To S-off it will cost you a mere $25, but it works in 5 mins and no need for computers/adb commands
Step 2: Remove ***TAMPERED***
After getting S-OFF, reset the ***TAMPERED*** flag and lock the bootloader using the following commands from these posts http://forum.xda-developers.com/showthread.php?p=46183050#post46183050 and http://forum.xda-developers.com/showthread.php?t=2477792 (credit to scotty1223)
To LOCK the Bootloader
To LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
To reset the TAMPER in bootloader
Enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
Step 3: Downgrade your Hboot to 1.44
Download the Hboot 1.44 from http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Before flashing, The android-info.txt file needs modified by clicking into the file (not extracting it) and changing the model ID to whatever your model is. This can be checked by running the command fastboot getvar all and checking the model ID number
Now flash the Hboot. To do this, boot to bootloader screen using the command adb reboot-bootloader
Type the following commands:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
After it finishes, execute the command again to complete the flash:
fastboot flash zip 1.29.401.12_hboot_1.44.zip
Fastboot reboot
Step 4: Run an earlier RUU from 1.29.xxx.xx
We need to run and earlier RUU first. For now, change CID to HTC__032
Download RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed from thanks to crushalot, http://d-h.st/Gt8. This will reset the phone back to complete stock, but not stock for the original CID O2___001. Once the RUU installs, reboot into bootloader and run the following command
fastboot oem writecid O2___001.
Check your bootloader and you should see the phone is still S-OFF and the CID is now for O2.
Step 5: Getting S-OFF again
This is if for some reason the phone has gone back to S-ON. To be honest, I did this step anyways just to be safe. Download, push and flash revone using the commands on the toolkit and ensure that the phone is not ***TAMPERED***
Using Revone, Unlock the bootloader - adb reboot bootloader to check it is unlocked
Step 6: Restoring an earlier backup
Download M7 CWM Nandroid Backup CID O2__102 1.27.206.1 2013-03-30 from crushalot's page on XDA and extract the file to the PC until you have a folder with a date on it and time (2013-03-11.17.58.27)
Make a new folder in your HTC one called clockworkmod. Inside here place a new folder called backup (all lower case). Place the backup here
Also, download http://forum.xda-developers.com/showthread.php?t=2200628 and place onto your SD Card. Once you flash the nandroid backup, go ahead and flash this. It will fix the missing preload apps (calculator, flashlight etc) which happens when unlocking the bootloader, and if these apps are missing can cause future OTA's to fail
Download CWM recovery and rename to CWMTG.img and place in your adb folder. You can also download Hassoon's Toolkit and copy the recovery from there if you like. At this point, ensure your bootloader is UNLOCKED.
From the fasboot menu, type the following
Fastboot boot CWMTG.img
This will boot into the recovery without installing it. Restore the nandroid backup you downloaded earlier and install the preload fix. Reboot
Step 7: Restoring stock recovery, Locking the Bootloader and install updates via OTA
Download the stock recovery for O2 from here http://d-h.st/l1q and flash via fastboot
Once booted up, lock the bootloader using Revone and remove tampered (run the command anyway even if it doesn't say ***TAMPERED***. Check for OTA - The one I got was for 2.24.206.1
Step 8: Returning to S-ON
Verify that the bootloader is LOCKED, not ***TAMPERED*** and hboot is 1.54 with the OS confirming your firmware
Type the command: Fastboot oem writesecureflag 3
Enjoy complete stock and continue with the OTA's
If I helped in any way just click thanks!

Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already

dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
Don't know why the links don't post correctly - 13: http://forum.xda-developers.com/showthread.php?t=2200628

dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?

stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?

stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
stovie_steve said:
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?
Click to expand...
Click to collapse
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.

dispereo said:
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.
Click to expand...
Click to collapse
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see

stovie_steve said:
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see
Click to expand...
Click to collapse
I got to 17 now (had to adjust minor things to get that work, thanks for your help!) and the problem is, my phone obviously doesn't support revone anymore as it doesn't have the permissions. Can I lock manually (with the HTC Dev command?) and I haven't had a ****TAMPERED**** since I installed the RUU.zip, do I still need to do 17. remove the tampered flag ? If so, how to do that with revone not having the permissions?
Almost there... almost there... *nervous*

So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?

dispereo said:
So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?
Click to expand...
Click to collapse
you should set it to LOCKED (not relocked), using either revone or http://forum.xda-developers.com/showthread.php?t=2475914 (or any of the other method available)

Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?

dispereo said:
Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?
Click to expand...
Click to collapse
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3

nkk71 said:
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3
Click to expand...
Click to collapse
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again, as hboot 1.55 was installed. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!

dispereo said:
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!
Click to expand...
Click to collapse
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers

nkk71 said:
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers
Click to expand...
Click to collapse
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...

dispereo said:
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...
Click to expand...
Click to collapse
That usually comes if you have S-Off, I though you said you went back S-On

nkk71 said:
That usually comes if you have S-Off, I though you said you went back S-On
Click to expand...
Click to collapse
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
Click to expand...
Click to collapse
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
Click to expand...
Click to collapse
And someone had the same question here:
http://forum.xda-developers.com/showthread.php?t=2470957
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)

dispereo said:
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)
Click to expand...
Click to collapse
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself

nkk71 said:
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself
Click to expand...
Click to collapse
I might have done that, even though I thought I left that out. However, my bootloader says ***** relocked ***** , that's all. It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on, I didn't have to do anything. i was wondering about that because you specifially mention it in your walkthrough but for me it disappeared automatically right at the start of the procedure.)

dispereo said:
I might have done that, even though I thought I left that out.
Click to expand...
Click to collapse
No way to go S-On without doing it yourself, no big deal, as long as you can unlock again.
dispereo said:
It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on
Click to expand...
Click to collapse
In theory, as long as you have stock ROM and stock recovery, the tampered should not show up, even if unlocked (S-On or S-Off), however for some, it did stay, even under those conditions. no real idea why. repeating myself: tampered should go away as soon as you have stock recovery.
dispereo said:
i was wondering about that because you specifially mention it in your walkthrough
Click to expand...
Click to collapse
Not my guide, it's @stovie_steve guide. I'm just visiting :cyclops:
So if you want to start over again, you need to get unlocked, flash a ROM compatible with your current firmware, which has root, and use rumrunner to get s-off.
I'm off for tonight see you guys around....

[Q] fastboot boot recovery.img on hboot 1.56

Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.

ergosteur said:
Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.
Click to expand...
Click to collapse
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.

nkk71 said:
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.
Click to expand...
Click to collapse
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.

ergosteur said:
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.
Click to expand...
Click to collapse
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?

nkk71 said:
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?
Click to expand...
Click to collapse
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.

ergosteur said:
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.
Click to expand...
Click to collapse
do go back to warranty you need to set phone to LOCKED, which is only possible with S-Off.
the fastboot oem lock command will set your bootloader to RELOCKED, so they would know you've unlocked it.... so stock recovery is the least of your worries if you want to ever go 100% back to stock.
stick with TWRP 2.6.3.3 or higher, but not 2.7.0.0 which seems to have problems with adb (and if i remember correctly charging when phone is off... though it could be a different one)
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
or 2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
EDIT: forgot to tell you why TWRP: it's compatible with 4.4 ROMs, CWM doesn't seem fully updated yet
Happy flashing :laugh:

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