yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
hi guys..

i have the same device with HTC__Y13 cid and only fastboot mode(device is not power on.) and device is S-on.. i found the HTC_Y13 fw but not flahing..it is zip file..

RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted

modelid: PN0710000

cidnum: HTC__001

cidnum: HTC__E11

cidnum: HTC__102

cidnum: HTC__203

cidnum: HTC__405

cidnum: HTC__Y13

cidnum: HTC__304

cidnum: HTC__032

cidnum: HTC__A07

cidnum: HTC__J15

cidnum: HTC__016

mainver: 1.29.401.16

phone has the same cid same fw...

C:\adb2>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.16

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: SH35SW906695

(bootloader) imei: 354xxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__Y13

(bootloader) battery-status: good

(bootloader) battery-voltage: 4297mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.031s
[One (M7) Q&A, Help & Troubleshooting] clsA:
flash it ... what is your question ?
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
Device not accepting the zip file..i am getting error..

Remote error 99..
[One (M7) Q&A, Help & Troubleshooting] clsA:
it's a decrypted RUU use

fastboot oem rebootRUU

fastboot flash zip ruu.zip

fastboot flash zip ruu.zip

fastboot reboot

make sure the ruu.zip is in the same folder as fastboot and is named correctly

and the phone needs to be plugged in and in fastboot USB when you start
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
i m really did and doing what u say.. but always getting error...

C:\adb2>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 44.656s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 44.922s
[One (M7) Q&A, Help & Troubleshooting] clsA:
then you may need to update just your firmware first
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
How can i find the firmware for this device.?
[One (M7) Q&A, Help & Troubleshooting] clsA:
try this one

https://mega.co.nz/#!GR4DRapb!DuLCgQi2TtunvCn6VvflB0nZgyQ_8BSi_zu0tQUR-no
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
Thanx alot downloading now..
[One (M7) Q&A, Help & Troubleshooting] clsA:
yeah it may not work with your s-on you may have to move up to 4.x.401.x

Firmware >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.9.zip

RUU >> http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
same error..

C:\adb2>fastboot flash zip [B]4.19.401.9[/B].zip
sending 'zip' (43508 KB)...
OKAY [ 3.031s]
writing 'zip'...
(bootloader) adopting the signature contained in this
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.281s
[One (M7) Q&A, Help & Troubleshooting] clsA:
Yeah, before you move on try and factory reset from stock recovery before you try the 4.x firmware and RUU
[One (M7) Q&A, Help & Troubleshooting] alray:
Can't use decrypted ones with s-on ;)

This one is a downgrade in version so can't be flashed with s-on

[MENTION=497218]t-mobile_mda[/MENTION]:

flash the 4.19.401.9 firmware then the 4.19.401.9 ruu.exe (signed) (you can extract the firmware from the ruu.exe)

you will need to flash it using windows 7 since your phone is on hboot 1.44 (will not work on windows 8)

Btw

if

you want s-off, better to achieve it now on hboot 1.44 before updating to a newer version.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Also bootloader needs to be locked/relocked with s-on

Yep have to agree with that part, get s-off while you're still on hboot 1.44
[One (M7) Q&A, Help & Troubleshooting] t-mobile_mda:
hi again..

i m always getting the same errro.r.. i hard resetted it too..

C:\adb2>fastboot flash zip 4.19.401.9.zip

sending 'zip' (43508 KB)...

OKAY [ 3.078s]

writing 'zip'...

(bootloader) adopting the signature contained in this image...

(bootloader) zip header checking...

(bootloader) zip info parsing...

FAILED (remote: 99 unknown fail)

finished. total time: 3.328s
[One (M7) Q&A, Help & Troubleshooting] clsA:
Sorry it was a long day yesterday I made some mistakes forgetting he was s-on.

---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------

Yes thanks too both of you ..I had a long day yesterday

---------- Post added at 07:09 AM ---------- Previous post was at 07:05 AM ----------

Sorry for the mistakes bud

like the guys above mentioned ... you should s-off your phone as soon as you get it booting up normally

have you relocked the bootloader yet ? If no you should try and flash TWRP and push a rom to the phone and use revone or rumrunner to s-off before moving up to the 4.x firmware
[One (M7) Q&A, Help & Troubleshooting] nkk71:
if you're going to go s-off, here's a good ROM for revone to work nicely on: http://xdaforums.com/showpost.php?p=48955645&postcount=251
[Galaxy S 4 Q&A, Help & Troubleshooting] Dany85:
Hi all,

i tried to flash cyanogenmod unofficial, on the flash an error was comming, now the device dosent start...

when i boot the phone normaly, is comming: firmware upgrade encountered an issue. please select recovery mode in kies & try again.

i tryed to flash the original firmware:

(I9505XXUAMDF_I9505AUTAMD8_AUT)

I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar

but an error in odin is comming:

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Removed!!

<ID:0/006> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/006> Removed!!

please can you help me?
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
Try flashing along with pit file

MKe sure u have the proper file for the same
[Galaxy S 4 Q&A, Help & Troubleshooting] Dany85:
where can i find the pit file?
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
http://xdaforums.com/showthread.php?t=2265477&highlight=stock+firmware

this link has it attached take the correct one u would know better

dont worry i had the same issue on my note 2 a month ago and was wrkng fine after flashing rescue firmware urs wil work too
[Galaxy S 4 Q&A, Help & Troubleshooting] Dany85:
damn, it doeset work for me :(

is it hard brick?

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> boot.img

<ID:0/003> NAND Write Start!!

<ID:0/003> Complete(Write) operation failed.

<ID:0/003> Added!!

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/003> Removed!!

<ID:0/003> Added!!
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
No its not at a hard brick dont worry dont panic thats the best wat to work around

I would say dont use pit file unless its last option and try without that only may be in other pc using other cable some below steps myte also help u

2) Install later Kies.

3) Kill al kies applications (all 4 of them).

disable antivirus or whatever you got there.) Get to Download Mode and push Vol Up.

7) Open Odin.

8) Plug the device to your laptop.

Does it see the device?

If NO:

A) Get another usb cable, are you using ?

B) Try different Odin Versions (download 3 or 4).

C) Try another USB port.

D) Still no luck? reboot the pc and start from step 3.

---------- Post added at 08:30 PM ---------- Previous post was at 08:23 PM ----------

Download 2/3 stock firmware and try installing thru ODIN it should work

Make sure u have all the drivers installed

MAke sure kies is not open or make sure its closed even in background process
[Galaxy S 4 Q&A, Help & Troubleshooting] Dany85:
okay, with odin 1.85 now has worked :) phu... lucky

but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?

only root is going... i'm now flashing root again :)

i think i will wait for an official CWM and official Cyanogen... is to hot for me :P

[MENTION=4616793]123hiten[/MENTION]

thank you very much!! I thought now i have to get out 700$ again... :S
[Galaxy S 4 Q&A, Help & Troubleshooting] samersh72:
Official firmware is not a wiping one. It doesnt flash userdata, it replace system, recovery, and some other partitions.

sent from my Galaxy
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
Great to hear that man

If u flash stock firmware all will remain as its in ODIN but its good if u reset the device after or b4 root

Also take a EFS backup of ur device and be safe
[Galaxy S 4 Q&A, Help & Troubleshooting] Dany85:
i had root before the device bricks... so i rootet it now again, and works good...

yeah, i will backup efs (hope this <- works...)

yah, thank you again...

have a nice day..
[HTC Rezound] Snuzzo:
A quick how-to from a good friend that's been using this since release candidates:

Please try to take any questions/bugs to this thread

http://xdaforums.com/showthread.php?p=41634758

or here

http://themikmik.com/showthread.php?16096-LunarTools-ChitChat-amp-Bugs-Thread
[HTC Rezound] Snuzzo:
For now, the source that's on git is for AOSP roms(place boot.img's on sdcard/lunar). Bare with me while working on getting insecured boots for AOSP to get the scripting to work properly.
[HTC Rezound] Luke1213:
wow wait for this to be stable. cheers!
[HTC Rezound] Neo:
Watching
[HTC Rezound] izzaeroth:
sexy

lookin sexy!
[HTC Rezound] Snuzzo:
First bug found

Problem

When choosing recovery_backup<DATE>.img and today's date is the same recovery doent seem to flash.

Solution

Rename recovery_backup<DATE>.img to a proper filename. recovery_<name><version>.img and flash the file under the new filename.

Just a small bug found which I will be rectifying very VERY soon.
[HTC Rezound] Snuzzo:
Nearing release as standalone flashables.

https://github.com/Snuzzo/LunarTools/commit/9bd3b14b2f6a23172da957ae893fea9f5bb0f766
[HTC Rezound] Snuzzo:
For those who have been following this; do you see anything that you would like implemented?

Standalone flashables posted in the OP for download.
[HTC Rezound] Snuzzo:
OK so far heroes what i got in a new menu addition...

Pulls boot.img from zip

Flashes it

Creates a recovery script which right now only flashes the zip you chose

Then auto reboots.

May need some assistance with this as it needs to wipe data cache. I probably could do this with a rm command prior to auto reboot.

Thoughts?
[HTC Rezound] izzaeroth:
I like the idea of it just auto booting into recovery only after flashing boot.img

Edit: or maybe have the script prompt if you want to reboot
[HTC Rezound] Snuzzo:
Bug: mismatched boot and rom in a backup

Solution: before using the 4th option to flash a boot.img from zip run your optional nandroid prior.
[HTC Rezound] Snuzzo:
Test builds sent out as extensions to busybox placed in /system/bin.

So far that has been working nicely. If those testers find any softbricks today I won't be releasing.

Next to do:

write a how to even though the menus are rather straight forward.

Add implementation of auto reboot to recovery to finish flashing a zImage from a zip.

Further reduce bootsize buffer for compression of output boot.imgs.

Finalize LunarCmdline.

Write a script to test compliance.
[HTC Rezound] Snuzzo:
Updated OP with a v1 release. Still has some work but 99% of it is completed.

Next to do:

write a how to even though the menus are rather straight forward.

Add implementation of auto reboot to recovery to finish flashing a zImage from a zip. Done

Further reduce bootsize buffer for compression of output boot.imgs. Done

Finalize LunarCmdline.

Write a script to test compliance of other devices.

Footnotes:

1st menu option- Not completely implemented yet. Could be used if wishing to restore a backup from Amon RA/CWM, I have further plans for it

3rd menu option- Use zImage from zip if fresh flashing. Use straight zImage if updating/downdating.

DO NOT PUT INVALID CHARACTERS IN ANY REQUESTED INPUTS! This could lead to unwanted results. Please PLEASE ask questions, don't let curiosity get the best of you.
[HTC Rezound] Snuzzo:
Had to re-upload a fixed AOSP/SDCARD zip. It was attempting to source a file from sdcard2.

http://www.androidfilehost.com/?fid=13858035414129967316
[HTC Rezound] iHateWebOS:
Major thanks, this is a really simple way to make use of cmdline features. :thumbup:
[HTC Rezound] izzaeroth:
ezpz

Gotta say this is a very handy tool to have around. I've flashed a bunch of different roms/boot.img/zimage and its pretty simple, especially after doing it at least once.
[HTC Rezound] live2die:
would this finally be an app to make it noob friendly:p
[HTC Rezound] izzaeroth:
A walk thru is in the works but its pretty straight forward
[HTC Rezound] Snuzzo:
Still got some minor kinks to work. Mainly on the Sense portion. Some of the ported roms are being a pain. The cmdline script runs beatifully. If you're s-off, mainly going to be interested in menu options 1 & 3. Both scripts work brilliantly with s-on and s-off alike without using fastboot.

Next to do:

write a how to even though the menus are rather straight forward.

Clean up some of the script to make it more efficient.

Create a boot.img to command line bootimg.cfg converter.

Add implementation of auto reboot to recovery to finish flashing a zImage from a zip. Done

Further reduce bootsize buffer for compression of output boot.imgs. Done

Finalize LunarCmdline. Done

Write a script to test compliance of other devices. Done
[HTC Rezound] Snuzzo:
Few things cleaned up in the Sense menu script. Got auto parsing of rom near completion. Also started sourcing configs instead of full boot.imgs for command line. Why mess with compression when its not needed, a 1Kb file vs a 6Mb file means you can have 6000 more setups going this route . Getting good, REAL good.

Also you guys can swap configs a lot easier and share them.

Next to do:

write a how to even though the menus are rather straight forward.

Clean up some of the script to make it more efficient.

Create a boot.img to command line bootimg.cfg converter.

Sourcing of auto recovery parsing.

The compliance script is near complete.

Notes:

Please if your current rom returns an unknown/number with the new version that hasn't released yet, post it here and what rom you are currently running. I will research it.
[HTC Rezound] Snuzzo:
New versions up!!!!

http://www.androidfilehost.com/?fid=22979706399752501

COMBINED BOTH TO ONE VERSION!!!

Next to do:

write a how to even though the menus are rather straight forward.

Create a boot.img to command line bootimg.cfg converter.

Sourcing of auto recovery parsing.

The compliance script is near complete.
[HTC Rezound] Snuzzo:
Lunartools made its way into our unofficial builds maintained by Flyhalf205!!! Watch for them soon!

Next to do:

write a how to even though the menus are rather straight forward.

Create a boot.img to command line bootimg.cfg converter. Canned; no need for it anymore.

Sourcing of auto recovery parsing. Will never work right.

The compliance script is near complete. Will be posting later.
[HTC Rezound] Luke1213:
so that means further versions of CM10 by flyhalf will include lunartool!
[HTC Rezound] Snuzzo:
Yup. Currently working on cleaning up the standalone version. So far Ive found the Sense version to not reboot to recovery when the ui prints state that it is/is supposed to.
[HTC Rezound] Luke1213:
i typed su, enter, then type menu, it comes to lunar menu. i type cmdline, it says cmdline not found.
[HTC Rezound] Snuzzo:
cmdline wont be found in the standalone. Not only that not many kernels for our rez utilize it.
[HTC Rezound] Snuzzo:
Quick how-to added to post #2. It's more-less a breif explanation of each option. Here's a copy of it.
[HTC Rezound] Snuzzo:
Got the initd portion done. No new release yet. Compliance script isn't quite completely done yet.
[HTC Rezound] TyWillems19:
I am an S On user and I was filled with extreme amounts of joy after reading this thread. You may even say I felt a bit manic from it all. Anyway, I am definitely going to test this out today and flash a CM10 ROM. Thank you so much, I'll let you know how the flash goes :)
[HTC Rezound] Snuzzo:
If you have questions before using it, post away. Either this thread or the bugs thread.

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Snuzzo:
http://www.androidfilehost.com/?fid=22979706399754394

NEW VERSION IS UP!!!

Check post 1 for a compliance script and post the output.log or a screenshot here or in the bugs thread.

- save test to your internal/external storage
- launch terminal emulator
- sh <path-to>/test

Added Initd options; cmdline will be implemented once more kernels come to support it.

Left to do;

Who knows .... I might have a surprise.
[HTC Rezound] TyWillems19:
So I am clearly confused. I downloaded the zip and extracted it to my SD card. I open up the terminal and type in su to get permissions and now I don't know what to do. Could you help guide me to be able to use option 4? Thank you in advance.
[HTC Rezound] Snuzzo:
Flash the zip not extract. :)
[HTC Rezound] TyWillems19:
Flash it? Like in recovery? Sorry I'm not the most knowledgeable.
[HTC Rezound] Snuzzo:
Yes. It's a rom mod.

Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
[HTC Rezound] TyWillems19:
Success!

Thank you very much for your directions I was able to get it figured out and successfully flashed a ROM S-On without connecting to a computer.

I wrote up a quick guide for other S-On users who wish to use this procedure for flashing ROMs on their Rezound devices.
[HTC Rezound] Snuzzo:
v1.4 is up!

-Added prompting for all storage options. It will still use "lunar" as the working directory on the option chosen

-Auto rom parsing should work 99% of the time

-Added Initd so you guys can start using it on any kernel of your choosing as long as your rom support init.d scripts(We now have something appealing to the S-Off guys).

Left to do:

It's a surprise..... :)
[HTC Rezound] Snuzzo:
Users who have downloaded v1.4; please trash it. I have something to fix. I WILL FOLLOW UP!
[HTC Rezound] Snuzzo:
v1.4 is back up and live. I had to fix prompting for storage options and recovery backup compression.
[HTC Rezound] greencat2:
I flashed the file and can get to the menu. I tried option 3 (I want to update the settings on the kernel). I thought I could use the kernel in the zip file for the rom. Got the error that the file is not a valid AnyKernel ZIP.

Is option 3 the choice to update the kernel and where do I get a zip of valid kernels?

Thanks
[HTC Rezound] Snuzzo:
What zip package are you attempting to flash from?
[HTC Rezound] greencat2:
I am using a zip that you posted awhile back in the chit chat forum. I think it is called eclipticrez zip
[HTC Rezound] Snuzzo:
Theres alot of scripting involved in that zip and also it's not an AnyKernel installer, Its sourcing full boot.img's. Please flash that in recovery.
[HTC Rezound] greencat2:
Ok - thanks - what kernels should I be using? Should I flash Version 9 again and choose Lunar? I know that sounds like a dumb question since the tool is called Lunar Tools - does it only work on the Lunar Kernel?
[HTC Rezound] Snuzzo:
Name was only derived from. It's where I initally got the idea. This is a rom mod, even though it is kernel related. An AnyKernel recovery flashable kernel zip is, for all intents and purposes, one that doesnt have a boot.img in the zip and does not rely on aroma.
[HTC Rezound] Luke1213:
still can not figure out how to flash boot.img using this. i rename it to boot_CWMTouch6.0.3.2.img, place it in /sdcard/lunar, then enter terminal, type su, then menu, then i choose option 2. it says syntax error
[HTC Rezound] Snuzzo:
I thought I posted the fix ... Grrrrr
[HTC Rezound] jagrave:
I used this the other day at work and actually flashed a ROM with a computer!! I don't know what kind of magic this is, but its AMAZING! :D

The only problem I had, and I'm 100% sure its user error, is that I tried to flash a new recovery, the CWM one. It all went well I thought, but when I tried to boot into recovery there wasn't one there. it would hang on the white screen for a few minutes then just boot into the rom. I tried to flash the one that you put in the example of how to name it, and I named it exactly how it was in that. I then used fastboot to flash CWM and when I booted into recovery I would get a black screen. So then I fastboot flashed Amon Ra(which is what I had originally), and I kept getting those errors where it can't access this or that, but the file exist type thing. I wasn't sure what to do b/c I tried flashing it several times so I finally decided to use the firmware update zip and steps that Brenuga(I think that is how you spell his name) posted, that everyone was using to get the new Hboot and radios, and then flashed Amon Ra and it worked. I'm assuming I might have originally gotten a bad download and it corrupted things.

P.S. I've flashed three different roms with this and every time it works perfect. I'm super glad you made this, makes S-ON so much easier. :)
[HTC Rezound] Snuzzo:
Regarding your recovery.img issue; did you have fastboot on or off at the time? Dependent on your reply I will get with my tester and confirm. Also, confirm you had it named "recovery_CWM_6.0.3.1.img"? These are small things that need to be worked out, there will still be some minor kinks. Like say nandroid backups, make sure you backup BEFORE using option 4.

Also some aroma roms are compatible, Viral OTA rom for instance. If you use option 4, you must also select stock+ in aroma. Ineffabilis Deus, nothing special needed. Nearly any of the aosp roms. If it can source a boot.img from the root of the installers zip, it is compatible.

In option 3, if choosing a zip it will detect you as s-off if the dev uses auto detection and you must reboot to recovery immediately after if not done automatically.
[HTC Rezound] Snuzzo:
Looking for a minimum of 3 s on testers who have some adb/fast boot knowledge( if soft bricks occur). Please pm me.
[HTC Rezound] Snuzzo:
GUI RC1 is up. It still includes a commandline version if you wish to invoke it.

initd & cmdline are still in command line stage, use them through terminal emulator or scripts manager.

Please if any questions over the next week or 2, [MENTION=4626451]d.kozzer[/MENTION] has been so kind enough to help assist you while I am on a personal hiatus. THANK YOU D! MEANS ALOT!

PS REMEMBER THIS IS VERY BETA AND MAY POTENTIALLY HAVE SOME BUGS! Use at your own risk. If you softbrick it is easy to restore using a rom/nandroid, a backed up recovery, and some patience through fastboot.