yashsingh1/xdaforums huggingface dataset:
[HTC Incredible S] John Anderton:
I wrote a post for that somewhere once.. NFI where it is.. will look for it :) Just hang in there.. it's recoverable (if I'm assuming you're in the state you're in) cause I did it myself :)

No, you cannot try to S-OFF from there. It's probably telling you the bootloader has a security issue. The problem is that the mainvers of your phone vs the stock ruu you're flashing don't match. So it formats your phone, installs the HTC locked bootloader and then realizes that it can't install the rest of the ROM so you're left in a zombie state.

Fix is to get your mainver, get a ROM equal or above it and install it. There after, hope a s-off hack works for that mainver (last I checked, revolutionary works for everyone). If you find it, s-off it again and enjoy your sweet success ;)

Let me find the recovery steps I wrote down somewhere on this forum for people in your situation. I've written tons of tutorials around it but I doubt anyone reads them before screwing up your phone. Warning posts are rather pointless if no one heeds them. Solution posts, thankfully do help folks :)

---------- Post added at 11:20 AM ---------- Previous post was at 11:08 AM ----------

I'm assuming you're in the zombie state.. no OS.. bootloader which won't accept any hacks. Your best bet, as I said is to go to a stable stock rom.

you phone might look something like this:

It would probably boot loop through the bootloader. Nothing else will load. Don't worry, it's not bricked (yet) ;)

This is all the info I had on this matter: http://xdaforums.com/showpost.php?p=16684717&postcount=38

To avoid this in the future: Simply put, check your phone's mainver (steps in the first post I linked you to). If your mainver is higher than the mainver of the rom, the rom won't install. Simple as that. If you're S-Off, you can reduce your mainver as well. The primary reason why mainver goes up is because people install radios which have text files which have higher mainvers. I've provided all the information you need in the guide below

http://xdaforums.com/showthread.php?t=1225538

I hope the culmination of these two posts gets you out of your current predicament and keeps you out permanently :)

Let me know if you need any help.

---------- Post added at 11:23 AM ---------- Previous post was at 11:20 AM ----------

Also, think logically. You're approaching this incorrectly. Since you're S-On right now, you can't install a custom rom for now. Just get a stable stock rom then s-off it with revolutionary. Not sure why you're trying to s-off it now and then install the rom.

Get your priorities straight. Phone booting is more important than s-off. if you have an s-off bootloader with no OS, the phone is still useless. So get a stock rom, get the phone up, start revolutionary so it can get proper temp root followed by s-off and then you can install whatever you want :)

If, at any point in my posts, I've misunderstood something, please let me know :)
[HTC Incredible S] santhoshpirate:
You are exactly correct my phone bootloader screen is same as yours except the manufacture date and tim (LOL :) )

How can i get a stable stock rom?
[HTC Incredible S] santhoshpirate:
I tried the correct mainver version Mine is 2.21.1010.4 and downloaded the RUU and installed it through fastboot i got this message

C:\Users\Sumo the Rider>fastboot flash zip C:\android-sdk-windows\platform-tools

\PG32IMG.zip

sending 'zip' (261186 KB)... FAILED (data transfer failure (Too many links)

)

finished. total time: 125.527s

Now what wahat should i do now.. my problem is slight different from yours but where the result is same i was on the process of s-on via fastboot and stuck at security warning in the bootloader screen
[HTC Incredible S] santhoshpirate:
i overcame that FAILED (data transfer failure (Too many links) problem now stuck at

C:\Users\Sumo the Rider>fastboot flash zip C:\PG32IMG.zip

sending 'zip' (261186 KB)... OKAY [ 44.011s]

writing 'zip'... INFOadopting the signature contained in this i

mage...

INFOsignature checking...

INFOzip header checking...

INFOzip info parsing...

INFOchecking model ID...

INFOchecking custom ID...

FAILED (remote: 42 custom id check fail)

finished. total time: 91.077s

What to do now? i cant find a solution for this anywhere!!

plz help me
[HTC Incredible S] santhoshpirate:
i have another question

Can i claim it to warranty stating a USB port broken and software stuck at bootloader due to random reboots.

My phone is in the state as you posted in Your reference photo.

Can i claim it?
[HTC Incredible S] santhoshpirate:
really sorry dude my radio and HBOOt version is different from you

Radio 3805.04.03.27_M

HBOOT 1.13.0000
[HTC Incredible S] John Anderton:
1) Please, DO NOT make 6 two liner posts. Write one post. Edit it. Easier to track. Easier to read.

2) doesn't matter what your radio/hboot is in this case

3) you cannot claim it.

4) It doesn't matter what your manufacture date/time is.

5) Did you read my post? Did you read it completely? Did you read it word to word?

If not, go do it again. Properly. With patience. Read every word like it's the Bhagwad Gita/Quran/Bible/Whatever other book you would probably read carefully.. Follow the instructions down to a T.

Rip the battery out of your phone. Keep it off for 30 seconds. Wait for it..

Put the battery back in. Turn it on. Let it go to bootloader and follow what I did.

Here are my questions. Answer every one of them in a single post in a proper systematic way. If you don't know the answer to anything, go back, read my post. If you still don't understand, try searching the forums and if you don't get it, ask me how to answer my question:

a) What's your phone's mainver?

b) What's the ROM you're trying to push on to the phone?

c) Is it a proper PG32IMG.zip?

d) Is it from a Stock RUU?

e) How did you extract it?

Also, be patience. Post once. Give us a chance to answer. We'll get to your query. I didn't have someone who'd done this before and I didn't have a phone for 3 days. Be patient. Read the forums. Do some research on your own and follow instructions others give you. You'll get it eventually. Don't worry.

Pro Tip: Make sure your phone is goes into fastboot mode properly. Does yours? Is your machine setup properly with the correct HTC drivers and no HTC sync?
[HTC Incredible S] santhoshpirate:
C:\Users\Sumo the Rider>fastboot getvar

INFOversion: 0.5

INFOversion-bootloader: 1.13.0000

INFOversion-baseband: 3805.04.03.27_M

INFOversion-cpld: None

INFOversion-microp: None

INFOversion-main: 2.21.1010.4

INFOserialno: HT13ETD07935

INFOimei: 355301042453962

INFOproduct: vivo

INFOplatform: HBOOT-7630

INFOmodelid: PG3213000

INFOcidnum: HTC__038

INFObattery-status: good

INFObattery-voltage: 4170mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: dirty-8a731c6e

INFOhbootpreupdate: 12

INFOgencheckpt: 0

all: Done!

Im trying to download this ROM

RUU_Vivo_Gingerbread_S_KT_KR_2.21.1010.4_Radio_20. 2805.30.085AU_3805.04.03.27_M_release_194748_signe d

http://www.filefactory.com/file/ccd0...748_signed.exe

Yes it is a proper PG32IMG.zip

Used this method to extract the file

1. Go to the "temp" folder on your PC. If you are on Windows 7 its located in "C:\Users\{Your_User_Name}\AppData\Local\Temp"

2. Use the windows search function in "Temp" folder or dig deep into sub folders to find "rom.zip" file. It'll be around ~250MB in size.

I dunno whether it is a stock RUU

i downloaded it from the form

http://xdaforums.com/showthread.php?t=1033922

I hav installed HTC sync
[HTC Incredible S] dhingra_vinay_in:
well i was in a same situation n i sent it for warranty....i got it repaired within a weak..m from India... n i guess u shud give it a try...as far as it shows s-on i guess the service center would consider it in warranty..try your luck :)
[HTC Incredible S] santhoshpirate:
Oh thnx dude Where are you from? I reside in Tamil Nadu
[HTC Incredible S] dhingra_vinay_in:
am from surat...gujarat !
[HTC Incredible S] tect:
ofcoz it can claim at long as within warranty period
[HTC Incredible S] John Anderton:
Not really. Once you root it, your warranty is void. HTC has no obligation to give you warranty. They won't if they figure out you've hacked it or even attempted to hack it. If they aren't smart enough to realize why this problem exists (which is when you make a mistake while reverting to a stock s-on rom from a s-off rom), they will replace it for you. if they understand technicalities, you're screwed.

It's really your luck. Probabilistically, folks at HTC's centers in India aren't smart enough (yet). This could change if HTC actually takes efforts to come out with an FAQ and train it's center folk.
[HTC Incredible S] dhingra_vinay_in:
well i completely agree with you John..n may be we should take the benefit of them being not smart....its just to go n try your luck...i did n was lucky enuf for it...
[HTC Incredible S] santhoshpirate:
Hey guys thnx for all ur help went through the whole process again NOW IM S-ON and my phone is also working

Special thanks to JOHN ANDERTON
[HTC Incredible S] x1123:
I have read whole pages of this thread since my phone at exactly the state above by accident :D I'm, downloading RUU for my mainversion version-main: 2.32.1010.1 however radio Installed is different with RUU one my radio version-baseband: 3805.09.03.27_M

root@ubuntu:/home/x/adb-tools# ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.32.1010.1
(bootloader) serialno: HT13ATD00430
(bootloader) imei: 355301042004294
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-51a64cbe
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

I did try to flash radio by goldcard and fastboot : NO LUCKS :confused: I will get try once downloading finish and report

-EDIT-

downloaded RUU 2.32.1010.1 extracted ROM by using "unruu" renamed to PG32M.zip put on goldcard sdcard > boot to hboot > update filed > CID Failed. > Edited Android-info.txt in which this RUU does not have HTC___044 cid > added HTC___044. > boot to hboot > CID Fail message did not come up, but also NO UPDATE :D

Boor to fastboot on adb > flashed and ended with : FAILED (remote: 12 signature verify fail). I need to figure out what is Failed # 12 :)

I think my main problem is combined mainver and Cidnum and radio:

mainver : 2.32.1010.1 (belong to KT_KR -Korean ROM-)

cidnum HTC___044 (belong to WWE)

radio 3805.09.03.27_M (I got from CM7)

Goldcard passed cid check but will not update due to radio is lower than one at the phone, flashed via fastboot failed due to can not trick cidnum or anything else related to bootloader signature check, which I need to learn further.

one good thing : Now I have something for FUN .... :D
[HTC Incredible S] santhoshpirate:
If u r still with warranty...please claim it that " you have applied the OTA update and all in a sudden the device rebooted itself and finally you were stuck at SECURITY WARNING BOOTLOADER they will then hardware reset it and install a new one with a newer radio and the latest bootloader....
[HTC Incredible S] thakur90:
You should say that "I ran out of battery while upgrading.... so its stuck now... "
[HTC Incredible S] santhoshpirate:
ya add that too! :D
[HTC Incredible S] x1123:
seems I made mistake in creating gold card previously, one of this forum member sent me email and convince me to use (again) gold card. I did again by creating gold card and flashed with 1.32.1010.1 rom. all work like charm. booting on korean ROM
[HTC Incredible S] mrnaresh:
how to s-off in HBOOT mode

hi,

iam trying to update (cm10_golfu-build3-wifi-fix.zip) my HTC Desire C

*** UNLOCKED ***

GOLFE PVT SHIP S-ON RL

HBBOT-1.31.0000

RADIO-1.10.98.15

eMM-boot

Jul 12 2012,15:44:30

1. Successfully unlocked.

2. but i can't s-off in HBOOT mode help me

guide me step by step

thanks for your help
[HTC Incredible S] Eternalman:
You are actually on the wrong thread and the wrong forum. Try finding a guide in your own device's forum! :cyclops:

BTW, there isn't any S-OFF from Revolutionary for your device yet.
[HTC Incredible S] piftoffpenguin:
Please share

How did you get past the too many links? I am fighting with my htc one right now on the same error . . . .
[HTC Incredible S] LamboBull:
This is for the IncS. Not the One.

Read the forum before you post.

Sent from my Nexus 5
[HTC Incredible S] piftoffpenguin:
no **** sherlock

And here I thought cars had similar makeups and similar issues so maybe a fix for one could lend a clue to another..... after all they all have batteries, windshields, tires, and alternators..... XD
[HTC Incredible S] AndyYan:
IncS and One obviously don't share "makeups, batteries, windshields, tires, and alternators" :) They only share the brand and the ability to run Sense 5 :D
[HTC Incredible S] piftoffpenguin:
ummm

and fastboot, and hboot, and nand, and RUU capabilities . . . the list goes on. If I knew how he bypassed the error it could have given me a damn good idea of where to look for my issue. Especially since he has/had VERY similar symptoms. That's all I was asking for.
[HTC Incredible S] AndyYan:
Nah, if you 1) flash One's bootloader/HBOOT on IncS / 2) replace IncS's NAND with One's / 3) load One's RUU on IncS you'll definitely know what I was saying :D
[HTC Incredible S] piftoffpenguin:
I get that

My point is he ran the same command I did in fastboot, got the same error and fixed it. Maybe however he fixed the error to get past the command failure, I could do the same or something similar to get around my issue as well.
[HTC Incredible S] poondog:
Help, bricked my One. I do not know what you were saying

HAHAHA
[HTC Incredible S] o759:
My htc s710e is s-on.
[HTC Incredible S] ze7zez:
LOCK S-ON -> UNLOCK S-ON -> BlackRose S-OFF -> Revolutionary S_OFF
[Motorola Droid 3] Hashcode:
I was sent this by XDA user: coreless88 who asked me to post this in the dev section (he doesn't have enough posts yet).

** WARNING: I HAVE NOT TESTED THIS PERSONALLY -- USE AT YOUR OWN RISK -- KEEP A BACKUP HANDY **

** THIS ROM IS INSTALLED WITH SAFESTRAP BOOTSTRAP. DO NOT USE KOUSH'S BOOTSTRAP OR YOU WILL SOFTBRICK YOUR DEVICE **
[Motorola Droid 3] coreless88:
Thanks for the help Hashcode!

I got my clearence to Dev forums, so I will try to contribute even more to this community =] .

First of all, as in my quote in the first post, I cannot guarantee this will work in CDMA network, Hashcode will inspect the files and try to integrate the GSM feature to his original release.

You can find a screenshot of my phone working under the GSM network and 3G enabled.

!!!

However, just like any other custom rom, I cannot accept any responsibilities if this rom bricks your phone.

!!!

For installing, just use Hashcode's safestrap, for the rest i think you know the drill.

BUGS:

Videos dont run,

Sound is low,

Bluetooth is broken,

Camera is broken,

Also be aware, notification and ringtone sounds are silent by default, you just need to go to settings menu and choose a ringtone for yourself =] .

Edit: Also as I have only 1 Droid 3 at the moment, I need as much testers as I can find for checking if this works for all Europe SIM Cards.
[Motorola Droid 3] coreless88:
Referved for future use/updates/etc...
[Motorola Droid 3] nikeusfr:
Awesome, very thanks to both Hascode and Coreless88

All work fine in france :-) the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.

I'm test, if you want, all other release in france, on bouygues telecom.....
[Motorola Droid 3] niko99:
thank YOU !! Hashcode and Coreless88
[Motorola Droid 3] coreless88:
No thank you guys, for trying it and giving me an easy breath as it is my very first development attempt!

Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.

Right now bluetooth doesn't work, but GPU and CPU working properly, if not better than before.

Here are some more screenshots, for Quadrant, SpeedTest, and A Samurai Vengance 2 (BTW Game runs incredibly smooth).
[Motorola Droid 3] nikeusfr:
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
[Motorola Droid 3] coreless88:
Hi,

First of all, thanks for your input. I need your opinions to make this better. So here we go,

All notifications and ringtones are silent by default.

You need to get to:

"settings>sounds>ring tone/notification tone" menus and choose your ringtones from there.

Sounds are in this built generally low, because there isn't any proper sound resources prepared with OMAP 4 series of SoC's. I will try to enhance them, but I will need time.

But you can make the phone louder on the speaker by going to:

settings>cyanogenmod settings>sound menu then choose the settings you like the most.
[Motorola Droid 3] DoubleYouPee:
What "general" GSM build.prop tweaks are we talking about here?
[Motorola Droid 3] coreless88:
Hi,

I've added Tweaks for getting stronger reception, making the GSM default network at the boot, tweaks for faster response, etc... You can download the file and look at the system>build.prop (open it via wordpad if you are on windows) and compare it to Hashcode's build.prop.

BTW I am experimenting with audio and video files right now. Post I will post the results when I finish the testing.
[Motorola Droid 3] DoubleYouPee:
Could I apply these build.prop changes my XT862 rom?

Or did you use droid 2 global hacks like someone tried before?
[Motorola Droid 3] coreless88:
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...

Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].

My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.

It will include lots of time, effort, patience and hell of a risk.
[Motorola Droid 3] DoubleYouPee:
Well I would love to use this mod, but because:

Videos dont run,

Sound is low,

Bluetooth is broken,

Camera is broken

I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier) :)
[Motorola Droid 3] coreless88:
Oh!

I completely misunderstand you, I thought you were asking about Hashcode's Cyanogen release. You cannot use these fixes for Motorola roms or any rom that based on a Motorola rom. These fixes and libraries are only for Cyanogen builds, at least thats what I think, as I don't have any development experience with any Motorola rom.

You may try, but that will only make the risk even bigger.

Please be patient, I am trying to fix camera and sound problems right now, and I will try to fix bluetooth in a later date, as I didn't see anyone using bluetooth for ages =] .
[Motorola Droid 3] Willis111:
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?

Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
[Motorola Droid 3] The Solutor:
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.

On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.

So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
[Motorola Droid 3] coreless88:
Hi,

Your thanks are appriciated, and I am sorry for this rom also did not worked for your XT860 =/ . I guess Motorola did everything they possibly can to protect their region based software versions.

I guess the fix will be simple, but I am afraid either Canadian Android developers are rare (BTW I don't think so), or they don't want to develop for / they don't have this device.

Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.

The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
[Motorola Droid 3] The Solutor:
Indeed this is the only reasonable explanation, the same behavior in five ROMs can't be a bug.

Maybe is omething hardcoded in the libril or whatever in the userland, surely is not the radio itself.

XT883 is not affected, so we should try to replace some piece to spot the culprit, BTW this process would be easier when the bootstrap will be fixed to work on XT883, (why doesn't work on that rom is a another nice mystery).
[Motorola Droid 3] DoubleYouPee:
Indeed, a GSM ROM would be great :D
[Motorola Droid 3] Hashcode:
FYI, audio and video codec issues are being addressed in my next build of CM7.

I'm going to give the GSM ROM a test drive and see how the CDMA stuff is affected. As well as look at the differences by file.

Hopefully, i can incorporate coreless88's changes back into the main ROM so that we don't end up with 2 CM7 ROMs (CDMA and GSM).
[Motorola Droid 3] thingonaspring:
@coreless88

GSM works well for me in the UK, tested with vodafone and virgin mobile (MVNO spanning T-mobile and Orange) SIMs with no problems - calls work, data works, no issues.

I used the GSM-patched ROM heavily today (calls/sms, reinstalling apps, syncing mails+calendar, surfing and playing videos with mx video player), and I've found no new bugs outside the known ones (camera rebootloop requiring battery pull, no extSD, native codecs fail).

@people like me who are a bit new to cyanogenmod

Cyanogenmod only includes code released under the very nice Apache open source license. That means the usual google apps/services like calendar/mail sync, market, news etc are all deliberately left out of the ROM.

To get google apps/services installed cleanly, goto this page :-

http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps

and download the latest google apps package for cyanogenmod7.

Use the safestrap installer to install the google apps zip just as you did for cyanogenmod itself - it won't overwrite cyanogenmod, it just adds the google stuff into the /system/app folder.
[Motorola Droid 3] coreless88:
Thank you very much for your input. I am trying hard to fix the codec fails and camera, and I do not think I will try too hard to bluetooth and extSD.
[Motorola Droid 3] rynosaur:
I got the same result flashing it on a VZ D3 . . . . my phone was softbricked until I reflashed stock 890 with RSDlite. Once I did, I rebooted into an exact, but unrooted version of what I had backed up (rooted 890 stock) then wiped in CWM Recovery (I've been using Koush's Bootstrap, but I MIGHT have overwritten its copy with Clockworkmod Recovery Adndroid's version of our recovery--possibly knocking out recovery kernel, permissions, or offset, IDK). Seems the current Koush recovery isn't erasing userdata, and I'm 110% sure that's why the modded CM7 kang caused the phone to bootloop.

My next question is . . . will Hashcode's variant do the same?