yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Incredible 2] vlsi99:
Hello:

I have a rooted InC2 , Android 2.3.4

Hboot 6.13.1002 (not sure how I went from 0.98 to this version after S-OFF)

I need to return the phone because the earpiece does not work

Need back to stock (Android 2.3.4 Hboot 0.98)

I have the zip file for v2.3.4 but it is bypassing flashing the Bootloader.

My question is where can I get the Hboot 0.98 for INC2 and remove revolutionary?

I found a procedure for HTC Desire S where someone created a an EngBoot.img loader that you flash by using

" fastboot flash hboot engHBOOToverARX.img "and this version allows you to upgrade the next version

using the same command for the Hboot you want.

Then, I assume you can flash stock with the zip file

Has anyone done this ?

Is the hboot for HTC Desire the same as INC2? Can I use these files?

I know there some dd commands that can be used (I understand the risk) but I don't have Hboot 0.98 for INC2 , if the procedure above does not work for INC2, where can I find Hboot 0.98 and the dd procedure to flash it?

Can some one help me ?

thank you very much
[Verizon Droid Incredible 2] Letitride:
My educated guess is that you're flashing one of the newer custom DI2 Rom here (ported from 2.3.6 or 2.3.7 or based on the Chinese Rom) and it changed your HB too. As I recall when this sub-forum was very active then, WiFi and 3G data also become unresponsive or "buggy" at times. In any event, you should read this link carefully & follow the steps -

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

The reference RUU file, if you cannot find it on VZW's linked website as it is a discontinued model, here is a working link that you can follow, housed on one of my Dropbox account, it is the original untouched one, clean & all. - skip to post #7 - http://xdaforums.com/showthread.php?t=2427581

I do not recall whether it specifically restore the HB to the earlier one, but everything else will be OEM/stock fresh, ready to activate - as if it's just unboxed. Besides, techs will most likely not be checking yours for HB verison as long as it boot up normally and appeared working, assuming that you are returning it for repairs/exchange and within the warranty coverage period.

Good luck !
[Verizon Droid Incredible 2] vlsi99:
I want to be sure I understand you instructions, I will perform these commands below . Should I flash the zip indicated or are you saying the last step "fastboot flash zip " I should replace the zip file for another from one of your links??

In post #7 there are 2 links :

To this file which is an executable

RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed

Will this executable generate a zip file?

the other link :

is a zip file All_Stock_PG32IMG.zip Or should I use this zip

adb shell rm -r /data/local/tmp/*

adb push zergRush /data/local/tmp/zergRush

adb push misc_version /data/local/tmp/misc_version

adb shell chmod 777 /data/local/tmp/zergRush

adb shell chmod 777 /data/local/tmp/misc_version

adb shell /data/local/tmp/zergRush

adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'

adb reboot bootloader

fastboot oem rebootRUU

fastboot erase cache

fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip

fastboot reboot

Will this reflash Hboot to 0.98

and basically remove S-OFF correct?

thank you
[Verizon Droid Incredible 2] Letitride:
Ok, the RUU...signed file that is in one of my Dropbox account now (next 72 hours or so) is the *.exe file from VZW, it will NOT generate a Zip file and it does NOT run inside ADB. Just download it to your preferred drive/subfolder. Connect your DI2 and assuming the HTC drivers were installed and it recognized yours (as it should) - click on the RUU file name and it should launch, with VZW's disclaimers and warnings, etc. - read & click thru it, and proceed - AT YOUR OWN RISK, of course. It will take 5 to 10 minutes to flash, when it's done - follow the prompts & reboot the phone. EVERYTHING, everything will be wiped clean & sysem reset, UNrooted - back in stock form as shipped.

If there are errors for whatever reasons, it might failed and stop proceeding with the flashing.

THE PG32IMG.zip file from Condemned will NOT change/restore your bootloader to HB98 or HB97, it will only restore the ROM portion to factory stock conditions and is for rooted devices with working CWM/TWRP recoveries installed - since it is in ZIP file format.

So, backup & save your settings with TB and CWM Backup first, save them to a safe location (i.e. USB or standalone external drive, etc.) before proceeding with the more basic PG*.zip file if you just wanted to get a feel for restoring it to stock looking rom. Running the RUU file in *.exe format will reset and wipe everything completely - you will lose ROOT and custom recovery will be gone too, and you should also see HB9x restored as part of the process - I just don't recall, but it will otherwise be 99%+ stock in general. The outsourced tech geeks at VZW's service counter will most likely not be looking to see if you've "messed" with the bootloader to disallow your repair claims or warranty coverage.

Good luck & please post your outcome/results - and/or if you run into other problems in the process.
[Verizon Droid Incredible 2] vlsi99:
Sorry, I got confused because this link http://xdaforums.com/show....php?t=1298990 has the instructions I posted and I thought I needed to execute. However, it seems all I have to do is run the executable to be stock.

I am just curious what are those commands for in the above link?

thank you very much
[Verizon Droid Incredible 2] vlsi99:
I may have misunderstood you.. running the executable just re-flashed ROM still S-OFF and @ hboot 6.13.1002

I though I saw the message flashing Hboot and it completed successfully. Did I miss a step?

thanks
[Verizon Droid Incredible 2] Letitride:
I see, okay - so you have the stock ROM on the device but it's still S-OFF with HB 6.13.1002 .... I went back to the older posts as it's been a while.

Well, if you feel you must get it to stock conditions, then I would say you need to run the ADB scripts as some users did have problems and it took more than one attempt to get it to work - http://xdaforums.com/showthread.php?t=1298990&page=17

Check that you have only HTC drivers installed and other USB device drivers uninstalled from the PC (running Vista or Win7, correct - or XP ??)

reboot the computer and connect DI2 with the micro-USB cable, and make sure that all the files needed are in the same sub-folder, including the RUU file as you've downloaded. Turn off your anti-virus & firewall temporary - restore them/ON afterward.

Log into command prompt as administrator on the PC, run the adb scripts - and as it continued, you should see the progress and/or error messages across the screen.

Let's try that - also look at, starting from post #161 from the linked post above.

Please advise as to your results afterward or whether you are still S-OFF with the same HB. Thanks.
[Verizon Droid Incredible 2] vlsi99:
fortified wardaid

Android 2.3.3 S-OFF same boot 6.13.1002 :crying:

One concern, if I do something else where S-OFF is removed and it does not leave me at Stock 2.3.4 , will still be able to use the executable to get back to Android 2.3.4 (with S-ON this time)?

Another comment that may or may not be related , through all these flashing sequences that I have tried , if a new radio is re-flashed, I get into the loop reboot mode and I need to reflash version

1.09.01.0312_vivow_Radio_PG32IMG.zip to stop it.

Any other ideas to remove S-off?

thank you
[Verizon Droid Incredible 2] Letitride:
See this hosted link to a full collection of RUU / roms for the DI2, including those outside US and overseas - please only consider using the last 7 at the bottom as you scroll down, the final 3 might be the older ones (2.3.3 ??) - I've never used this link's files to reflash our DI2, but the download links are working and MD5's provided to verify its integrity upon d/l completion. Use at your own risks & discretion. http://www.androidruu.com/index.php?developer=Vivo_VivoW

The x.0312 radio isn't the newest one, if I am not mistaken - the x.0320 radio is the newest official VZW release for the DI2 & compatible with Gingerbread roms. The older ones x.0622 or x.0722 and there was another one in between 0.1111 radio - these might be causing problems with the newer Roms. Most of the custom Rom offered here usually (but not always) as a matter of practice, does not change or re-flash to a newer radio unless it specifically stated so in the instructions - so I would just keep extra copies named with its version available, and rename it to PG32IMG.ZIP before moving it onto the mSD card to flash from the Bootloader in case of boot-looping. Just be careful as flashing a non DI2 radio will permanently brick your device.

Our DI2 are on SkyRaider (2.3.4) and runs great with the .0320 radio (the 0.312 radio was used earlier.)

More reading for you - http://xdaforums.com/showthread.php?t=1751796 - with the TACOROOT method, it will downgrade and result in S-ON, prior to running Revolutionary to get S-OFF again with additional steps. Consider this as it sounded like you are comfortable with using ADB.

If you manage to get S-ON somehow via other discovered means, flashing the *.exe again should not affect S-ON/OFF setting.

Generally speaking, if you managed to get the device back to 99% stock look & functioning, and there is no water damage or physical breakage due to accidental dropping, etc. - you shouldn't have any problems with warranty repair or exchange at VZW - I have yet to come across hearing/reading about anyone being denied a claim for updating the radio, HB or kernel, etc. Just bring/send it back to nearly as stock as possible, move/delete anything "unusual" that might be on your mSD card (i.e. empty subdirectory of CWM or Titanium Backup, etc.) and I think you will be fine.
[Verizon Droid Incredible 2] vlsi99:
One question, the *exe you first gave me had a radio 1111 with 2.3.4 , however it had the bootloop problem. The last downgrade to 2.3.3 that I did had another radio that also caused the bootloop problem. My fear is that if I accomplish S-ON and use any *exe to go back to stock 2.3.4 , I will have the bootproble without a way to reflash the radio 302 since I am S-ON at that point.

Is there a way to fix the bootloop problem with S-ON?

Is this make sense to you?

Just to be sure , doing this below, downgrades only the Hboot or also does S-ON, Reading the post is a procedure for phones that S-ON with a particular Hboot and FW version below certain number. Are you recommending this just to downgrade Hboot?

DOWNGRADE TOOL

Versions: HBOOT .98, firmware below 6.01.605.05

This will not work with firmware version 6.01.605.05! Use the tacoroot method!

This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.

Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.

Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.

It is more like a challenge now..but may be I should send the phone back with 2.3.4 and S-OFF. I will appreciate if you can answer my questions above.

thanks again
[Verizon Droid Incredible 2] Letitride:
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.

A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.

Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.

At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
[Verizon Droid Incredible 2] vlsi99:
I am at 2.3.3 ,radio 302 , K 2.6.35.9 (from my last downgrade attempt). Since your *.exe brought me to 2.3.4 (with 1111 radio) , I will re-flash this and put radio 302 back. I have already done this so it is pretty safe. I did not find a *exe RRU with 5.10.605.9 with radio 302.

I have CSW

Doe sit make sense?

thank you so much for all your help
[Verizon Droid Incredible 2] vlsi99:
curti was

Ok here is how to S-ON and go back to v2,3,4 only if your phone works with radio 1111, IMPORTANT ---< You need to try this version with S-OFF first in case you get into booloop and can re-flash the radio 312

Follow this link

http://www.iball99.com/2013/04/htc-incredible-2-gingerbread-rooted-stock/

Revert to Stock Froyo

Re-flash Hboot 0.97 ---<At this point you are S-off but the next stock flash will take you back to S-ON

Update back to Gingerbread ----< WARNING assuming you don't get into booloop with radio 1111

Otherwise, I assume you can't recover from with S-ON and bootloop mode?? Is this true??

I did not try to reflash stock because my phone gets into bootloop with radio 1111.

But I was able to downgrade and re-flash Hboot 0.97 . I only need a to find a zip or ^exe with radio 312 ;)

I really appreciate your help!!
[Verizon Droid Incredible 2] Letitride:
Thanks for the info - for the time being, my motto is "if it ain't broke, don't mess with it or change it" but I'm downloading those patches via my Linux server to offline storage, just in case that I want to or need it later on, once I'm done with using the DI2 as my daily device, LOL - less than 2 months left on my contract & seriously considering Nexus 4 now the price drop - whether there's a Gen II or now, just to team up with the beloved Nexus 7 running JB 4.3

If I am going to play - and mine doesn't bootloop with the 1111 radio (nor the 722 or 622 radios based on Froyos) - flash the stock RUU files - it's been a while in dealing with those *.nb0 - once it's back to S-ON and locked bootloader with stock recovery, it's much harder to recover if the Rom run into a continuous looping. Our warranty has expired long ago and I don't plan on selling these on *Bay with its low resale/market value, so just going to keep it as a backup even if I'm going to switch to GSM services - 3G CDMA coverage is barely working inside our house but thankfully for Fios, I have ultra fast broadband coverage 85% to 90% of the time that smoked the best 4G LTE out there today.

I dont' recall either, whether one of the GB RUU from VZW has the 312 radio included in the *.exe download, it could've been an OTA file on a stock Rom, but the 1111 radio was definitely in one of the stock RUU in the link - the discussions on where the developers (AndyBone, CS or Nit's) pulled the 312 radio were "buried" in their development Rom's, if only I have time to dig thru them.

Sounds like your DI2 is where you wanted it to be in restoring to stock form, good luck in getting the warranty exchange or repair done. Regards ! :cool:
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] crazydaftunk:
My s4 keeps giving me keeps saying "SD card safe to remove" for no reason and doesnt let me mount my sd card. Someone please help!!
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Ingenium13:
Your SD card is probability failing. Do you have a different sd card you can try? Or try removing it from your phone and putting it in your computer (assuming you have an adapter) and see if you have similar issues.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] w7excursion:
Mine does the same thing. I soft reset and it mounts.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] clip3009:
Same thing happened with mine after downgrading to stock in odin
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] xxaddictedxx:
i got that same error right before my 32gb took a dive on me.....make a backup of your sd card somewhere just to be on the safe side.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] fgr:
You don't mention anything about your setup, but I used to have that happen with some early versions of some of the custom kernels.

Try flashing the stock kernel if your on a custom one.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] deadenz:
What Xposed framework module do you use? Nottach or Wanam?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Venom0642:
Wanam and Xblast

Sent From My Galaxy S 4 SAMSUNG-SGH-I337 Running On New Deadly Venom v8.0.0
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] rebel1699:
I use Nottach
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] [Face]TigerBite:
Using Nottach but didn't realize there were even alternatives. Nottach is buggy for me seems if I use certain settings that it doesn't like it just turns off all changes, then I have to reset, and redo all settings again, guessing which one I'm not supposed to use... is Wanam or XBlast any less buggy?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] rebel1699:
Dont know. Nottach works great for me. After you make changes, only do a soft boot, not a full boot. The one thing that does not work that I have found, is image behind notification window. The reason is it requires a full reboot, ergo, losing the setting. Also, it does not retain the setting after full boot like other things. At least with the other settings, after you do a full reboot and the settings revert, you can just open the xposed installer app, hit softboot, and when finished all your settings will be back in effect.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Andrew149:
just tried wanam and all the features everything works on mf3! even the theming! WOAH
[MDA II, XDA II, 2060 General] sclarke:
Hi there, im wondering if anyone has had a similar problem with their xdaIIi. Ive had it about 3 months, i updated to the latest o2 firmware etc a few weeks back and other than removing the o2 active ui, everything is standard.

Software wise, i havnt installed anything new in the past month or so and can see no reason for the problem, what happens is this:

- when using the phone, i.e starting to write a message, run a game, anything.. it restarts within between 1-2 minutes of use.

- when left alone, i.e just sitting in cradle or on the desk, it restarts every 10-20 minutes on its own.

I have no idea why its doing this, have tried removing the sd card but the problem remains and i dont know what to do short of wiping it and starting again.. any help much apreciated, thanks.
[Nexus 7 (2013) General] troy2062:
I've been experiencing a strange phenomenon in relation to the touchscreen on my new Nexus 7. It is essentially impossible to capture in video and difficult to accurately describe, so I apologize for any frustration in comprehending my description.

If I open the Play Store (for example) and gently flick to produce a slow automated scroll, the store page will scroll completely smoothly (aside from the usual few dropped frames as images load). However, if I place my finger on the screen and manually scroll through the page by the same amount at the same speed, it visibly stutters. The stutter produced is not absolutely horrible and some people may not even directly notice it, but it is just enough to make manual input feel sticky. On webpages filled with text where stutter will exacerbate even minor ghosting, it is particularly annoying.

The issue is present globally within the OS, although there are certain games which implement further input smoothing and seem to get rid of it. I was somewhat apprehensive about posting this thread, as it an issue which may be too subtle for many people to directly replicate (assuming I do not simply have a defective device, that is) without an exact understanding of what they are looking for and some may think I'm being "too picky".

To further clarify, I am aware that many people have had multi-touch and phantom input issues on this device, but those are not what I am referring to. I have experienced no multi-touch nor phantom input issues whatsoever.

Has anybody else encountered this issue or should I simply organize a replacement? If it is a software issue, I am perfectly willing to wait for Google to rectify it in a future update.
[Nexus 7 (2013) General] ethanfel:
got the exact same issue with the two i ordered. Sometimes unlicking is a pain or drag and drop an icon to a screen. I"m waiting to get an update. If the next one is the same. i send them back ;)
[Nexus 7 (2013) General] frozst:
I thought this was solved in the last update.
[Nexus 7 (2013) General] CPmillenia94:
Yup, This is the exact issue I am so frustrated with. I am really hoping this is a fixable issue..
[Nexus 7 (2013) General] gogol:
It's a known issue.

I had the same, and fixed by applying this :

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

Hopefully it will be fixed in the next release.

But until then, you can use the above solution.
[Nexus 7 (2013) General] kiyo21:
I had this same issue on two nexus 7 devices (one purchased, the other a replacement unit) but eventually returned both over single touch issues. The stutter was apparent especially in chrome when you pinch to zoom. Feedly was another app that would stutter as you scroll down an article. I assumed this was more of an app specific issue but I guess it may be just another touch related issue with the device.
[Nexus 7 (2013) General] juried:
AFAIK, this issue is due to the capacitive touch screen not having a very fine resolution input. It is especially noticeable on cheap tablets. The touch screen has input lines running say on a 1x1cm grid. As you draw your finger across, the line whichever is closest to your finger will register. So it will jump from one line sensing the finger to the next one, and this is then input to the software scrolling and produces a stuttering in the scrolling. You can easily try is by slowly drawing the finger up and down and watching the reaction of the page that is scrolling underneath.

To alleviate this, the screen driver can hand over from one line to the next in a smooth gradual manner but of course there will always be a scrolling rate where the effect is worse. The slower you scroll the clearer you can see it.

If lines are close to each other or you have fat fingers, this effect becomes less noticeable.

[edit] having said that, there are always apps which scroll poorly regardless of the quality of the screen.
[Nexus 7 (2013) General] CPmillenia94:
^I thought that was the issue at first, but now im thinking its a software issue. The slower I move my finger, the less stuttery the animation. It is only when i move my finger at a medium or fast speed that it begins to stutter like this.
[Nexus 7 (2013) General] troy2062:
This would be a perfectly plausible explanation, however the amount of stutter doesn't really seem to vary at all, regardless of the speed at which I drag.
[Nexus 7 (2013) General] tni.andro:
Huh? Try an app like 'Yet Another MultiTouch Test' that displays touch coordinates. The touchscreen certainly has single-pixel accuracy/resolution (a pixel is 0.08mm wide).
[Nexus 7 (2013) General] juried:
It has high resolution (different to accuracy btw) due to the driver software working out where the touch is by using all the pick-up dots that show a capacitive response. But in the Nexus you can actually see the capacitive pick-up dots if you hold it in the sun and get the reflection just right, and they are 5mm apart.