Develop Bugs

[Q] Boot problems

Need a little help with a boot problem. To outline:
1. previously running DevNull 1.1 no problems on PVT1 rooted s-off Desire GSM.
2. Decided to try Redux2 LITE - from this thread http://forum.xda-developers.com/showthread.php?t=1229003 - full wiped and flashed via recovery CWM 2.5.0.7 as usual
3. ROM booted once and then rebooted during account registration. Battery pull - stuck on s-off splash screen
4. ROM booted successfully - used briefly then rebooted to flash battery mod.
5. ROM and recovery will now not boot - stuck on s-off splash screen
I have bootloader and working fastboot with the PC recognising the device inside cmd.
BRAVO PVT1 SHIP s-off
HBOOT 6.93.1002
RADIO 5.17.05.23
So far I have tried wiping:
Code:
fastboot -w
erasing 'userdata'.... OKAY
erasing 'cache'... OKAY
finished
and flashing rom (devnull) via fastboot:
Code:
fastboot update c:\update.zip
error - update package has no android-info.txt or android-product.txt
then erasing again and trying a different rom (oxygen) - same result
then flashing new recovery:
Code:
fastboot flash recovery c:\recovery.img
sending 'recovery'... OKAY
writing 'recovery'... OKAY
finished
fastboot oem genchkpt
recovery does not boot,
Code:
a bunch of code then
FAILED <status read failed <too many links>>
finished
[EDIT] tring this again after "fastboot erase recovery", the process hangs (with the s-off splash screen) at
Code:
<bootloader> ---------------hboot boot time 96886msec
and only prints the fail message above on battery pull [EDIT]
neither does it work if I battery pull then attempt to boot recovery from bootloader.
So I'm out of ideas! Is it time to flash RUU?
Can you actually flash a custom rom zip via fastboot?
Thanks in advance.

solved here:
http://forum.xda-developers.com/showthread.php?p=20444883#post20444883

[Q] Can't flash HBOOT. (status malformed (1 bytes)) Desire otherwise fine.

Edit: this appears to have been an issue with my USB cable. Thanks anyway to kotag82 for all his help.
I am trying to unroot my desire because the power button is broken and I need to send it in for warranty. I currently have CM7 installed, with the Bravo CM7 r2 HBOOT from AlphaRev.
I am trying to flash the stock desire HBOOT but I get this error:
Code:
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I have checked the MD5 of the .img
I don't know what to do next.
Thanks
Edit: also the RUU can't see my phone. I assumed that was because I'm not using Sense so HTC Sync doesn't connect, but it may be relevant.

Did you try to flash downgrade first, cm7/r2 has protection

kotag82 said:
Did you try to flash downgrade first, cm7/r2 has protection
Click to expand...
Click to collapse
I did not, please could you point me in the right direction? I have never heard of that before.

It has protection(RUU can't overwrite it) download downgrader from alpharev: first flash it reboot and flash stock one
Edit... sorry you can do it without downgrader my bad...
did you try fastboot devices?

Code:
C:\AndroidSDK\tools>fastboot flash hboot bravo_downgrade.img
< waiting for device >
sending 'hboot' (512 KB)... OKAY [ 0.087s]
writing 'hboot'... OKAY [ 0.152s]
finished. total time: 0.239s
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... ^C
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... ^C
C:\AndroidSDK\tools>fastboot devices
HT03FPL01263 fastboot
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.003s
C:\AndroidSDK\tools>fastboot devices
HT03FPL01263 fastboot
"^C" was where it was just hanging for ages and I cancelled the command.
But now downgrade is flashed atleast. But that does mean I'm now stuck in a bootloop.

Hi try this stock hboot, stock.img inside

kotag82 said:
Hi try this stock hboot, stock.img inside
Click to expand...
Click to collapse
Is this more likely to work than the stock hboot on http://alpharev.nl/ ?
I'm slightly hesitant about flashing something I don't know where its from..
Edit, its MD5 is identical. I tried it anyway but I had the same message. "sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))"

this was downloaded from alpharev ages ago, i flashed it 1 hour ago... everything ok, i just renamed it because of im lazy to type it all...and im using rmd recovery too to flash it... see my signature, there is an option flash image in recovery menu... try to flash your original from alpharev to see if it is working... if not try mine... btw it looks like your file is corrupted

I did have a go with it, but had the same trouble. I don't think my download is corrupted because the MD5 matches what it shows on the alpharev website.

have you tried pb99img.zip method?

Ok, I tried with another USB cable and this time was successful. I don't know if that is coincidence or not but I'm happy with it. Hopefully the RUU will work once I restore Sense from nandroid.

Ruu should work now... good luck... did you use original htc usb cable?
just curious..

trying to switch partition tables on HTC desire GSM
Hi all - I've got a similar problem to that which was discussed here.
In my case I've been using my HTC desire with cyanogenmod7 BRAVO N1table partition for nearly a year now. Lately I'm noticing I am running out of space with my huge app appetite so I thought I would change the partition table to the BRAVO cm7r2 (which was not around when I first reset the partition table).
I managed to get fastboot working on my ubuntu 11.10 machine after some strife but I am stuck when it comes to flashing the hboot .img file with fastboot.
I followed the instructions on alpharev.nl and various other sites to no avail...
when I run the command:
fastboot flash hboot bravo_alphaspl-cm7r2.img
the response i get from the terminal is:
sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))
I am sadly quite a n00b when it comes to this stuff and really don't know how to interpret this message... I tried the bravo_downgrade.img file with fastboot flash hboot in a similar fashion and got the exact same error message
I hope the question makes sense and I've not been too verbose...
for further info, on my phone i see the following when I'm in HBOOT USB PLUG mode, from the top:
AlphaRev N1Table
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.1000
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
HBOOT USB PLUG
Any more info required just let me know - Thanks in advance for any help you can offer

something is wrong but try pb99200.zip method, place it in root of your sdcard and start the phone vol- and power buttons together

Sorry forgot to mention - I did try the PB99IMG.zip method... I put it in the root of the SDcard as per the alpharev and your instructions.. I get the error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I read up on this a bit too and I'm having trouble understanding exactly what the error means but it seems I may need to use a GoldCard? Just researching those now... perhaps I will try to make one.
Is there any possibility that my ubuntu fastboot is not working as normal? I have windows 7 dual booted so I thought next I might try running fastboot from there as it seems there is more support for windows in general... could I use a program like androidflasher to flash partition table changes?
Thanks for your super speedy reply!!!

i think golcard is needed i can't confirm as all my sdcard are goldcards
yes you can try android flasher or you can try that via RMD recovery flash image section there just put your image file on sdcard

I just had this problem after flashing cm7r2, but only because I was silly and did these steps in the wrong order:
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
Follow the above after fastboot flash hboot image.img and you should be fine

Bingley said:
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
Click to expand...
Click to collapse
If the command does not give effect, then remove the battery for a while. It had just helped me.

ze7zez said:
If the command does not give effect, then remove the battery for a while. It had just helped me.
Click to expand...
Click to collapse
2012 dude

Do you know where a full description of the solution to the problem of "FAILED status of malformed"?
I added something from each other, which may one day help someone.

[Q] Dead Screen: Recover/clone DInc??

My rooted HTC Incredible screen has died, but otherwise the phone works (I think). I was running MIUI on it. I used Titanium Backup and the MIUI backup utility, but had not used them for a while, so my most recent setup was not saved. I can access the phone via USB/ADB. Is there any way to pull the currentconfiguration off the phone so that I can "clone" it to a "new" Incredible? If so, suggestions are gratefully accepted.
BM99

Tried adb pull * *?

adb shell
cat /dev/mtd/mtd0 > /sdcard/misc.img
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
cat /dev/mtd/mtd3 > /sdcard/system.img
cat /dev/mtd/mtd4 > /sdcard/cache.img
cat /dev/mtd/mtd5 > /sdcard/userdata.img
This will back up all system partitions. use flash_image or fastboot to restore the images.

cmlusco said:
adb shell
cat /dev/mtd/mtd0 > /sdcard/misc.img
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
cat /dev/mtd/mtd3 > /sdcard/system.img
cat /dev/mtd/mtd4 > /sdcard/cache.img
cat /dev/mtd/mtd5 > /sdcard/userdata.img
This will back up all system partitions. use flash_image or fastboot to restore the images.
Click to expand...
Click to collapse
OK, so I was able to use the commands to back up muy dead phone. I am having a lot of trouble restoring the new rooted/s-off phone with flash_image or fastboot. Can someone recommend a site with step by step set of instructions, write it out here, or a GUI program that will accomplish the same thing?
Thanks,
B

bartman99 said:
OK, so I was able to use the commands to back up muy dead phone. I am having a lot of trouble restoring the new rooted/s-off phone with flash_image or fastboot. Can someone recommend a site with step by step set of instructions, write it out here, or a GUI program that will accomplish the same thing?
Thanks,
B
Click to expand...
Click to collapse
What hboot is the phone on? What problems was fastboot giving you?

cmlusco said:
What hboot is the phone on? What problems was fastboot giving you?
Click to expand...
Click to collapse
The phone was in "Fastboot USB". I used the instructions at wiki.cyanogenmod...Fastboot. The errors I got were:
c:\mini-adb_inc>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)... OKAY [ 1.108s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.123s​
Bart

bartman99 said:
The phone was in "Fastboot USB". I used the instructions at wiki.cyanogenmod...Fastboot. The errors I got were:
c:\mini-adb_inc>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)... OKAY [ 1.108s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.123s​
Bart
Click to expand...
Click to collapse
The new phone is s-off right? What hboot version is it on? Flashing images remotley (from a pc) with fastboot requires either the .77 engineering hboot or one of the new ones unlocked. I would flash the .77 hboot then restore the images with fastboot then flash back to .92 hboot. You can get the hboots here http://dinc.does-it.net/Hboots/

cmlusco said:
What hboot is the phone on? What problems was fastboot giving you?
Click to expand...
Click to collapse
cmlusco said:
The new phone is s-off right? What hboot version is it on? Flashing images remotley (from a pc) with fastboot requires either the .77 engineering hboot or one of the new ones unlocked. I would flash the .77 hboot then restore the images with fastboot then flash back to .92 hboot. You can get the hboots here
Click to expand...
Click to collapse
OK, so I flashed the .77 hboot and now the phone is stuck at the htc incredible start up screen. Tried removing battery and rebooting, etc. No luck.

bartman99 said:
OK, so I flashed the .77 hboot and now the phone is stuck at the htc incredible start up screen. Tried removing battery and rebooting, etc. No luck.
Click to expand...
Click to collapse
If you got the img's to restore with the .77 eng, then you just need to flash back to the .92 hboot and it should boot.

cmlusco said:
If you got the img's to restore with the .77 eng, then you just need to flash back to the .92 hboot and it should boot.
Click to expand...
Click to collapse
Unfortuately no. I am able to get into recovery and so did a restore.
Then I went back into recovery and delete the cache and Dalvik
Then flashed .77hboot again
Did a Fastboot flash of system, userdata, cache, recovery, but was unable to do "boot.img" FAILED (remote: image update error)
re-flashed back to .92 hboot
rebooted Incredible and frozen again at white HTC Incredible screen.
Any suggestions?
B

bartman99 said:
Unfortuately no. I am able to get into recovery and so did a restore.
Then I went back into recovery and delete the cache and Dalvik
Then flashed .77hboot again
Did a Fastboot flash of system, userdata, cache, recovery, but was unable to do "boot.img" FAILED (remote: image update error)
re-flashed back to .92 hboot
rebooted Incredible and frozen again at white HTC Incredible screen.
Any suggestions?
B
Click to expand...
Click to collapse
Did you install the .77 hboot or the eng (engineering) .77? You need the eng one, that will allow the fastboot commands. Then flash back to .92 and it should boot right up.

cmlusco said:
Did you install the .77 hboot or the eng (engineering) .77? You need the eng one, that will allow the fastboot commands. Then flash back to .92 and it should boot right up.
Click to expand...
Click to collapse
I used the ENG .77 (MD5 ends in D1) and then flashed to .92
B

Thats strange. Well im not sure then what to do to get the img's on there. Im not sure why it errors when you flash the img's. I will think on it some more.

cmlusco said:
Thats strange. Well im not sure then what to do to get the img's on there. Im not sure why it errors when you flash the img's. I will think on it some more.
Click to expand...
Click to collapse
It only errors when I try to flash the boot image. I was able to flash the recovery, userdata, and system fine.

bartman99 said:
It only errors when I try to flash the boot image. I was able to flash the recovery, userdata, and system fine.
Click to expand...
Click to collapse
Try erasing boot first " fastboot erase boot " and then try flashing the boot.img

cmlusco said:
Try erasing boot first " fastboot erase boot " and then try flashing the boot.img
Click to expand...
Click to collapse
Nope. Unfortunately it didn't work. I was able to erase the boot, but when I tried to flash the new boot.img, I still got the same error message. I tried a couple of different copies of the same file that I had stored in different places, but still the same error.
I also opened the MIUI ROM zip file (I am using MIUI) and tried to use the boot.img from there to flash. I was able to flash that boot.img, yet the Incredible still is frozen at the white "htc incredible" screen.
Ah well. Unfortunately, with the amount of time I have spent, I could have started from scratch with the base MIUI ROM and cusomized to where I wanted by now:crying:
Thanks for all your help.
B

bartman99 said:
Nope. Unfortunately it didn't work. I was able to erase the boot, but when I tried to flash the new boot.img, I still got the same error message. I tried a couple of different copies of the same file that I had stored in different places, but still the same error.
I also opened the MIUI ROM zip file (I am using MIUI) and tried to use the boot.img from there to flash. I was able to flash that boot.img, yet the Incredible still is frozen at the white "htc incredible" screen.
Ah well. Unfortunately, with the amount of time I have spent, I could have started from scratch with the base MIUI ROM and cusomized to where I wanted by now:crying:
Thanks for all your help.
B
Click to expand...
Click to collapse
No problem, had to try.

Bootloop no Fastboot Permissions

I have an old evo 4g laying around and I wanted to do some work porting my iPhone app over to Android. But when I turn on the device I just get a bootloop of the white evo splash screen. Same situation trying hboot to recovery
My hboot details
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.79.0000
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Apr 14 2010,15:41:34
I'm on a mac heres what I get when I try to remedy with fastboot
Code:
./fastboot devices
HT07CHL11811 fastboot
Code:
./fastboot flash recovery /Users/Robert/recovery.img
sending 'recovery' (2690 KB)...
OKAY [ 0.898s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.899s
reboot works
Code:
./fastboot reboot
rebooting...
any thoughts? As for ROM I have no idea whats on there, I attempted to clear storage in hboot and apply a recovery update with the PC36 img method which yielded
Code:
[1] RECOVERY - OK
Update Complete...
Do you want to reboot device?
I chose yes - bootloop so go to hboot chose boot recovery - bootloop

I am no genius, but your hboot might need downgraded to HBoot_0.76.2000 for fastboot commands to work .

After doing some reading I believe you are correct. Now I am on the hunt for a reliable way to go from .79 to .76 or for an RUU in PC36img form...

Try This link calks post

Thanks, do you know if I can rename the file and update from hboot? I am unable to access recovery or the ROM proper.

Well... found a RUU that matched everything applied it the radio update failed and like a retard I restarted the phone instead of going back to hboot... Now its bricked...

Sorry to hear that man... you still might be able to get back around the brick,just have to get the right thread thread for tips on restore on brick. And if you do get it up and running, I would recommend for a custom recovery to make the peripheral tasks easier. Then you could just concentrate on porting your app instead.

[Q] Fastboot isn't working, neither is recovery...

I want to return my at&t m8 back to stock (currently on stock rooted with one bad mod installed) so I can give the phone to my father. I dont have S-OFF and dont care about resetting the tamper flag. I have tried many methods to do so, the first being fastboot flashing the stock recovery, then fastboot oem lock, rebooting bootloader, then running the AT&T RUU. After i tried this several times, i noticed that the stock recovery never gets flashed even though it reports 'okay':
Code:
fastboot flash recovery recovery.img
target reported max download size of 1830723584 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.789s]
writing 'recovery'...
OKAY [ 0.896s]
Fastboot reboot-bootloader (both the cli command and if you go select reboot fastboot on the phone) also doesn't work, it reboots the phone normally.
Seems weird that the flash doesn't happen and that reboot-bootloader doesnt work, but nonetheless i try another method restoring a stock nandroid from http://forum.xda-developers.com/showthread.php?t=2701376 . I followed the steps, fastboot erase cache --> fastboot flash boot boot.emmc.win --> fastboot erase cache --> reboot to recovery and restore nandroid --> reboot phone. ANNDDD.... somehow I'm still on the same System/ROM as I was before all this. Also worth noting, any files I push with adb are gone after a reboot. Not sure what is going on but any help would be appreciated.

So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]

jball said:
So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]
Click to expand...
Click to collapse
Yes I have root.
Unfortunately anything that has to be done from the phone that isn't in the boot loader or recovery, is not an option at this point because it's in a boot loop (makes it to lock screen and then reboots). Sometimes it stops the loops and works for awhile, so if it does I'll give this a shot. However, is there any other method via adb/Fastboot over USB or TWRP?

Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.

redpoint73 said:
Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.
Click to expand...
Click to collapse
Device id shows when i run fastboot devices . I am Positive the fastboot connectivity is not the issue here. So i am attempting to use the bootalble RUU. Since I am S-On though, I have to relock the bootloader first. When I run fastboot oem lock I get this:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.126s
And then it reboots the phone normally, it goes into its loop, I go back to bootloader, and it still shows unlocked.
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?

cojomojo said:
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?
Click to expand...
Click to collapse
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.

redpoint73 said:
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.
Click to expand...
Click to collapse
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
Click to expand...
Click to collapse
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494

jball said:
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.

cojomojo said:
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.
Click to expand...
Click to collapse
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.

jball said:
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.
Click to expand...
Click to collapse
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.

cojomojo said:
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.
Click to expand...
Click to collapse
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome

jball said:
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome
Click to expand...
Click to collapse
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.

cojomojo said:
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.
Click to expand...
Click to collapse
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
---------- Post added at 10:19 AM ---------- Previous post was at 09:54 AM ----------
@cojomojo
If nothing else works maybe try what I have over in here
http://forum.xda-developers.com/showthread.php?t=2586472

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.
Click to expand...
Click to collapse
Strange, fastboot problems are most often a driver issue. But I agree, if you've tried it natively on Mac and PC, it would seem that drivers is not the cause.
Out of curiosity, what ROM is running on the phone currently?

jball said:
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
Click to expand...
Click to collapse
I am trying to check to see if maybe fast boot is on. I suppose it is a possibility, now I just need the phone to stay on long enough to check.
redpoint73 said:
Out of curiosity, what ROM is running on the phone currently?
Click to expand...
Click to collapse
Running stock rooted, with one mod installed (wifi tethering). It is the 50% of the problem because it is causing the reboot loop i mentioned earlier.
******* Update **********
"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick. Thanks to all sticking with helping me out here, even as we approach 3 pages

@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be

jball said:
@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be
Click to expand...
Click to collapse
Will do for sure. Thanks for your help! I'm thinking I might try and get the phone on long enough to try flashify or something. Maybe try and get s-off???

Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it, does it state so in the bootloader screen?
If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.

ashyx said:
Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it? If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.
Click to expand...
Click to collapse
Bootloader says unlocked... so I assume it is unlocked. I suppose I could go through the unlock process again, but it definitely says "unlocked". Also TWRP flashing/restoring/anything does absolutely nothing. And I have tried 3 cables and 2 computers.
*** CLARIFICATION ****
I can get into TWRP fine, and I can restore, flash ROMS, whatever... BUT even though they report okay with 0 errors, everything stays the same, i.e. nothing in TWRP actually works. Same with Fastboot.