It seems to me that HTC Dumlock is the solution to flashing kernels without fastboot... Has anyone had any success doing this? I get a (failed) message when executing it from the app.
You can flash the kernel from recovery (cwm, twrp, etc.), but ... your OneV must be S-OFF. It it's not, then you can do it only by fastboot.
Related
Hi
Now that we have S-OFF and the ability to flash radio.img's from fastboot, I just wondered what follows the flashing?
What I mean is, when you flash a radio via recovery, it flashes, then you have to reboot the device using the recovery menu, it then reboots, does some more flashing, and then reboots again.
Does the fastboot method do the same? Just for future reference so I don't pull the battery (for example) at the wrong time.
Thanks
Stu
No just use the standard fastboot flash command and it should flash straight away, thats why recovery has to reboot because it has to flash from the bootloader....
Sent from my HTC Desire using Tapatalk
attached is a semi-working recovery, you can flash it with "fastboot flash recovery recovery.img".
update: the recovery can flash boot.img's too, if the custom rom uses "dd" instead of "write_raw_image" to flash the boot.img. i hope mike updates his rom
don't use anything except for "install from sdcard"
i take no responibility for any harm to your device or data
it's basicaly a repacked cwm recovery combined with the stock 1.26 recovery kernel/ramdisk with modifications to init.rc
it is intented for developers wanting to toy around with custom roms, until someone makes a real recovery
no support nor updates will be made for this
is it tested or not yet.
I've tested it
ok thanks, since currently there is no other option to unlock bootloader other than htcdev & lack of RUU sources is too risky to flash custom recovery at this point. so technically it will skip zip package signature check? so we can start working on working custom rom.
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
looks nice!
could you maybe share your knowledge about creating this recovery? i'm trying the same for the one s but can't get it packed together correctly...
blubbers said:
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
Click to expand...
Click to collapse
Understand. My concern is no RUU for my device available yet & im afraid to use from other region stock rom Thanks for ur effort.
Do I have to unlock my phone to install this recovery?
moom999 said:
Do I have to unlock my phone to install this recovery?
Click to expand...
Click to collapse
yes, there are only 2 ways of installing a recovery.
fastboot and adb
fastboot requires you to unlock in order to "fastboot flash recovery"
and in order to possibly do it through adb you need root and in order to get root at the minute you need to be able to flash an insecure boot image through fastboot, which again, you need to unlock in order to "fastboot flash boot"
Hi blubbers,
There is a guy on general thread who wants to dump a developer phone. It's s4 not tegra but might help.
http://forum.xda-developers.com/showthread.php?p=24496390
sent from my HTC one X using tapatalk
I have successfully unlocked the bootloader. I flashed the cwm recovery by fastboot with the proper command and the command executed fine. I also erased the cache with fastboot. But when I select recovery from the hboot menu it gets stuck on to screen with the HTC logo with following text in red "this build is for development purposes only do not distribute outside of htc without written permission". I cannot access the cwm menu.
I tried the twrp recovery too but no avail. The same screen comes up.
I searched a bit and found that some have faced the same issue with HTC ONE X and had their problem solved by flashing an interim unofficial cwm built for their device. But I can't find any such interim cwm recovery for HTC ONE V.
Please help.
What command u used to flash??
rohov said:
What command u used to flash??
Click to expand...
Click to collapse
fastboot flash recovery nameoftherecovery.img
In my case it was fastboot flash recovery recovery.img
Nothing wrong on my side. This is not my first time.
And the commands executed without any error.
I even relocked the bootloader and unlocked it again. But, still the problem persists.
anice06 said:
fastboot flash recovery nameoftherecovery.img
In my case it was fastboot flash recovery recovery.img
Nothing wrong on my side. This is not my first time.
And the commands executed without any error.
I even relocked the bootloader and unlocked it again. But, still the problem persists.
Click to expand...
Click to collapse
If you take a ruu and remove the Rom.zip and from that take the recovery.img and flash that, does the phone boot into the stock recovery?
Sent from my HTC Desire S using Tapatalk
HTC One M9 CDMA version,
HIMAWL,
VZW_001,
OPJA30000,
3.10.605.7 firmware,
no rom (incomplete stock rom?)
Stock Recovery (corupted?),
S-Off,
Unlocked,
Software Status: Official (used to be tampered (via sunshine) until loaded backup)
I am currently in a weird state of purgatory with my phone.
Here is the full story:
Unlocked and S-Off via sunshine.
Flashed TWRP Recovery.
Backedup via nandroid (boot, System, Caches)
Flashed several roms and firmwares, ended up messing up my IMEI somehow when playing with cyanogen nightlies and decided to go back to stock.
Reverted to backup i made earlier.
And now here we are.
I have access to the bootloader and download mode/fastboot.
When i boot to recovery (via any method) i receive the message: "Failed to boot to recovery mode. Press volume up or down to back to menu."
When i attempt to fastboot erase recovery, it works.
When i attempt to fastboot flash recovery, it works. (but still fails to boot to recovery)
When i attempt to fastboot flash firmware, it fails: "FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT firmware)" Which i believe is a permissions error?
When i attempt to fastboot flash system, it loops the flash, and claims "Invalid sparse file format at header magi".
As a note, i have used both the newest version of fastboot and the special HTC_Fastboot with the same results.
Any ideas how to get a recovery back?
Clues as to why i can't get into recovery?
Try flashing twrp recovery pre 3.0
Sent from my HTC One M9 using Tapatalk
irocevo said:
Try flashing twrp recovery pre 3.0
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thank you irocevo!
Hello, need your help guys.
So my Whyred bootlooping now. What I did previously was wiping System, Cache, Dalvik & Data before flashing custom ROM -- I know, this shouldn't be an issue. But since I can do fastboot, I tried to flashes recovery. I tried a few (TWRP, RedWolf & Batik), for each the steps were all the same: Via fastboot flash the dummy image to manipulate ARB check, then flash Recovery and finish with boot into recovery.
The phone booting into recovery, I can see the screen of recoveries for few second, then phone bootlooping again.
What should I do?
And for additional information, my phone was unlocked bootloader -- it still unlocked because I can see the Unlocked sign on bootloop screen. I also tried to flash official MIUI rom via fastboot (whyred_global_images_V10.0.6.0.OEIMIFH_20181127) but it was failed because anti roll back -- I also don't understand this because the ARB was supposed not allowing me to downgrade, but why is it also not allowing me to flash the latest ROM too?
I am now stucked in bootloop -- still can do fastbooting, but really have no idea how to flash any rom and get into the system. Really need help help help please
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Rush-er said:
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Click to expand...
Click to collapse
Yes, for redwolf it was the command -- I was short typing but thats the idea.