Database Develop

[DEV] Flashing the Tattoo via HBOOT - COULD BRICK! YOU HAVE BEEN WARNED!

Warning: This method hasn't been throughly tested. It could brick your HTC Click (Tattoo). In either situation, I am not responsible if your phone explodes into a portable fireworks show. Should you decide to take the risk, please make sure you have backed up your data in case of a brick. Thanks.
I found an another way to flash the HTC Tattoo via HBOOT.
What I did is name 'CLICDIAG.nbh' to 'CLICIMG.nbh' and got the following:
HBOOT said:
CLICK PVT SHIP S-ON
HBOOT-0.52.0001 (CLIC10000)
MICROP-0203
RADIO-3.35.07.20
Sep 22, 2009, 14:40:39
HBOOT
Parsing [CLICIMG.nbh]
[1] MFG_DIAG
Do you want to start update?
<ACTION> Yes
<Power> No
Click to expand...
Click to collapse
Knowing that I could possibly screw up/brick my Tattoo (and make it continuously boot into the DIAG program), I aborted the update. It goes to show that the Click/Tattoo still supports the classic way of flashing ROMs (like the way we got root on the HTC Dream/G1 via DREAIMG.nbh).
I have also heard that if you get rom.zip from the RUU (go to your temp folder in Windows while the RUU is on the "Welcome" screen and search for rom.zip) and rename it to 'CLICIMG.zip' and place it in the root of your MicroSD card, the Tattoo will also detect it as a ROM and ask if you'd like to flash it.
Opinions/Suggestions/Comments, anyone?

UPDATE: Tried to flash the ROM with SU-binary, and it bombed out with the dreaded error: "Main version is old! Update fail!". I googled for a solution, it said something about 'fixing' a perfect SPL on the Magic/Sapphire. Alas, I'm not game enough to try using a different devices' firmware.
I'm tapped for ideas.

Hi.
Did you check or try the recovery partition options?
Maybe something could be done with it...
android-dls.com/wiki/index.php?title=Replace_Recovery_Partition

Just tried flashing... sadly failed with a 'signature error'.
P

Note: I was not using a goldcard, assume it wouldn't make any difference in this instance?
P

Coburn64 said:
UPDATE: Tried to flash the ROM with SU-binary, and it bombed out with the dreaded error: "Main version is old! Update fail!". I googled for a solution, it said something about 'fixing' a perfect SPL on the Magic/Sapphire. Alas, I'm not game enough to try using a different devices' firmware.
I'm tapped for ideas.
Click to expand...
Click to collapse
Bad. RUU checking rom version to prevent downgrade.
ROM with test signed keys is one of oldest.
Need to search something new...

modaco said:
Note: I was not using a goldcard, assume it wouldn't make any difference in this instance?
P
Click to expand...
Click to collapse
Since you were willing to flash it, I think trying with a goldcard is well worth the effort. It painless to create one..

It didn't help.
Coburn and I have been chatting on IRC (#modaco on freenode) and we're kinda running out of ideas at this point...
P

Does that mean you don't see a chance getting root ever or just not that way?

Any 1 root
hi guys
any 1 successfully Root/or Flashed Via Goldcard ?

-bm- said:
Does that mean you don't see a chance getting root ever or just not that way?
Click to expand...
Click to collapse
We're trying our best. The root looks grim, unless we can somehow get a S-OFF bootloader. :/

Getting a S-OFF SPL would only be possible through HTC (who hold the keys to sign it). Either we're very lucky and someone leaks such a SPL or we're dead in the water.
Next best hope is someone finding a local root exploit on the kernel or in one of the setuid binaries that come in the Tattoo.

I have updated a rooted Tattoo with rom renamed to CLICIMG.zip and and an unrooted Magic 32a with rom.zip renamed to SAPPIMG.zip and copied to and fat32 sd followed by fastboot as described earlier in this thread - and2209

Thank you man my old dead tattoo is alive now becouse of you! thanks again

[Think Tank] NAND Write Access

http://forum.xda-developers.com/showthread.php?t=701835
The EVO has just been fully rooted and we should start the discussion of using the same method here for NAND access. We need to figure out what was changed to learn more about the new methods. I do not have experience in all the new images and will be unpacking them for further review. There might be stuff here very specific to the EVO and may not be repeatable on the incredible.
Information:
** Done via an engineering SPL (custom?)
** Looks as if they flash over the misc partition with mtd-eng.img
PC36IMG.zip File List:
* android-info.txt
ModelID: PC3610000
CIDNUM: SPCS_001
MainVer: 1.17.651.1
HbootPreUpdate: 11
* boot.img
* hboot_0.76.2000.img
* microp_v04.img
* NV.img
* radio_1.36.00.04.02.img
* rcdata.img
* recovery.img
* splash1.nb0
* system.img
* tp_atmel224_16ab.img
* tp_atmelc03_16ac.img
* userdata.img
* wimax_24722.img

What files would we need for the Incredible?

1wayjonny said:
The EVO has just been fully rooted and we should start the discussion of using the same method here for NAND access.
http://forum.xda-developers.com/showthread.php?t=701835
In theory this should work just about the same for the incredible.
Click to expand...
Click to collapse
toastcfh said:
This process will allow you to unlock Nand protection on all partitions at all times via Engineering SPL.
Click to expand...
Click to collapse
Don't think it's going to help us any...

dew.man said:
Don't think it's going to help us any...
Click to expand...
Click to collapse
You might be right as I missed that specific line but this thread is needed anyways. =)
If anyone gets a chance, please unpack mtd-eng.img for further discussion working now and tied up...

I was just trying to break root on my DI with *228 when I noticed it 'unlocks' SPL to add PRL data. Can we use adb to sneak in there and replace parts of the Nand?
-------------------------------------
Sent via the XDA Tapatalk App

rynosaur said:
I was just trying to break root on my DI with *228 when I noticed it 'unlocks' SPL to add PRL data. Can we use adb to sneak in there and replace parts of the Nand?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well that question gets brought up a lot and this happens on non-android phones. Could it do something that we do not know about?
Sure but most likely not

1wayjonny said:
Well that question gets brought up a lot and this happens on non-android phones. Could it do something that we do not know about?
Sure but most likely not
Click to expand...
Click to collapse
SPL - Service Programming Lock (activation)
SPL - Second Program Loader (boot-loader)

The thread is not needed, we will open one when we release nand flash. The desire method (what evo uses) won't help as we have no eng hboot. but rest assured, a solution is close if not already known.
To clarify all they were doing is using root to change the main version in misc partition thus tricking the phone into accepting a downgrade it woudn't have otherwise. you could do this to flash the 0.75/0.76 ruu's if you want.

Shadowmite said:
The thread is not needed, we will open one when we release nand flash. The desire method (what evo uses) won't help as we have no eng hboot. but rest assured, a solution is close if not already known.
To clarify all they were doing is using root to change the main version in misc partition thus tricking the phone into accepting a downgrade it woudn't have otherwise. you could do this to flash the 0.75/0.76 ruu's if you want.
Click to expand...
Click to collapse
So basically what you're saying is we basically have it pretty much done?! Just have to finish up a few things and should be done within the next week?!

Shadowmite said:
The thread is not needed, we will open one when we release nand flash. The desire method (what evo uses) won't help as we have no eng hboot. but rest assured, a solution is close if not already known.
Click to expand...
Click to collapse
Wow, nice to see things coming along so quickly. The G1/Dream didn't get a rooted .nbh for 3 months after release, and only got the engineering SPL because someone at HTC f-ed up and sent Tmo a refurbished G1 with the engineering SPL still installed (lolz on that one), so this is good news and obvious sign that people are really dedicating their time and attention to making sure the masses can run all kinds of crazy ROMs or brick their DIs at will

Red Trackball "of death" - need some instructions

I followed this thread : http://forum.xda-developers.com/showthread.php?t=726258 and run into serious problems that i can't seem to fix.
To be exact I am refearing to a user in that thread that mentioned he has a black screen, since version 0.33 of bootloader doesn't work for "lcd" (?)
However, since I had the same problem i followed his suggestion to use PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_si gned.zip from shipped-roms to get stuff working again. And it did - except the side effect that since then i have a red trackball as soon as the phone finished booting up.
I've tried all, followed the exact instruction for back to stock, formated sdcard, didn't succeed either, so now I'm stucked with this battery draining red light and researches on google gave a lot of hints in terms of moisture or overheat, no solution though.
Any help is highly appreciated.

I think the issue is in the misc partition, something might not be right there...
You currently have the misc img of a desire on your N1...
Maybe you could try to flash a default N1 misc image and PASSIMG of a non korean N1 that matches your current hboot?

Amon_RA said:
I think the issue is in the misc partition, something might not be right there...
You currently have the misc img of a desire on your N1...
Maybe you could try to flash a default N1 misc image and PASSIMG of a non korean N1 that matches your current hboot?
Click to expand...
Click to collapse
I did use the original stock image provided by modaco, unzipped it and fastbooted all the images like system, recover and so on.
Now my current boot is:
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
RADIO-4.06.00.12_7
jUN 14 2010, 12:02:27
So could it be that there's a conflict in a "protected area" that can't be solved, except by the approach you suggested?

You did follow the thread in your first post and flashed the Desire misc image (mtd0.img), right? I would try to :
1. unlock your bootloader so S=OFF (fastboot oem unlock)
2. get hold of an N1 mtd0.img dump with S=OFF and flash it

Amon_RA said:
You did follow the thread in your first post and flashed the Desire misc image (mtd0.img), right? I would try to :
1. unlock your bootloader so S=OFF (fastboot oem unlock)
2. get hold of an N1 mtd0.img dump with S=OFF and flash it
Click to expand...
Click to collapse
You are the man! thank you so much!!! Time to read about mtd0.img and fire up the hex editor
Unless I find a website that generates or a file that is good enough.
But really great, I was about to wave goodbye to my Nexus

RunTimeWorld said:
You are the man! thank you so much!!! Time to read about mtd0.img and fire up the hex editor
Unless I find a website that generates or a file that is good enough.
But really great, I was about to wave goodbye to my Nexus
Click to expand...
Click to collapse
Maybe you can just ask someone to dump his N1 mtd0 partition for you...

Amon_RA said:
Maybe you can just ask someone to dump his N1 mtd0 partition for you...
Click to expand...
Click to collapse
That would be awesome, mind giving it a shot?
Don't wanna stretch your patience though..
Btw.. why don't you make a GUI to RA and sell it on the market? ;-)

RunTimeWorld said:
That would be awesome, mind giving it a shot?
Don't wanna stretch your patience though..
Btw.. why don't you make a GUI to RA and sell it on the market? ;-)
Click to expand...
Click to collapse
Try this : http://dl.dropbox.com/u/4481275/misc.img
Maybe there will be a GUI one day...

Thanks you Amon!!!
off-topic I know... But rarely do u see "popular dev's" responding to people questions/needs and for that I just wanted to pop in and say AMON_RA you are awesome!!! Thanks for everything u do that makes this community GREAT!!
/nohomo guys, just appreciation!!!

I absolutely agree and appreciate to get such a response from a pro!However, I am new to Android and trying to figure out a few things.
[Edit]I figured out about the misc partition and guess what? IT WORKS!!!![/Edit]
Amon, you helped me a big deal, thank you so much, you've triggered a dude to contribute. Big time!

I have the same problem and I tried to do the same method as Amon_Ra posted. But I get the following error message when flashing misc.img:
Code:
remote: signature verify fail
so I was wondering if I am suposed to rename the file as mtd0 and flash it trough adb shell as:
Code:
adb push mtd0.img /data/mtd0.img
adb shell
misc /data/mtd0.img
thanks!

I know that this post is too old, but i have the same problem and the link doesn't works

Amon_RA said:
Maybe you can just ask someone to dump his N1 mtd0 partition for you...
Click to expand...
Click to collapse
your link is doesnt work anymore,can you frop it again!

Seriously anyone have that image?

towfurious said:
Seriously anyone have that image?
Click to expand...
Click to collapse
What do i need do get you? I havev nexus one unlocked with br and cm7. It is slcd version. Just tell me the command

I think that it's poosible to dump the misc partition with
Code:
dump_image misc /sdcard/misc.img
(as root)
I'm not sure i dumped it correct, file is an attachment.
It's a vodafone nexus one with AMOLED.

Header2k thank you but i need dump from nexus slcd

Race55 can you dump it for me?

towfurious said:
Race55 can you dump it for me?
Click to expand...
Click to collapse
Just to confirm, there is no personal info in the misc partition right?

I looked into my dump with an hex editor. The only readable part is something like "Google" and the stock firmware version number. Don't think that there's anything personal
Edit:
In order to flash this try the "flash_image" command.

OTA update file (4.0.19915 to 4.1.26)

Here is the update that the test phones(4.0.19915 to 4.1.26) received right before the launch of the retail unit. You might think this is useless, but it paints a very clear picture of how Moto updates work on the Atrix.
For each file that is being updated it hash checks and then applies the binary patch. This means changing the file permissions, mounting the system as rw will not cause this to fail as someone else had mentioned before. When it comes time to update, we can extract it and run the patch against the retail dump to create an updated dump.
This also tells us we can use recovery to flash update.zip files, we just need to figure it out. This would be very helpful when creating an updated dump.
This file is downloaded to /cache/tmp. A simple script was used to capture it before it was deleted.
Download the file here:
http://www.ponack.net/designgears/atrix/update.7z

This is very good news.
does this also mean that an OTA can be packaged as a zip and "flashed" to a phone?

verrry nice

Thanks DG!
and please stay
we will miss you

GSeeker said:
Thanks DG!
and please stay
we will miss you
Click to expand...
Click to collapse
I will still be around doing things here and there

Anyway to unbrick my atrix with this?

hassanjanjua2002 said:
Anyway to unbrick my atrix with this?
Click to expand...
Click to collapse
What kind of brick do you have on your hands?
Also, thanks dg

Very informative!

Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.

navalynt said:
Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.
Click to expand...
Click to collapse
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.

Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it

t0dbld said:
Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it
Click to expand...
Click to collapse
baseband_ota.img and mbm_combo.bin

I want Update.zip signed for this orginal files from /system/lib
libskia.so
libskiagl.so
libwebcore.so
Because I changed these files to make the device read Arabic, but the device stops working and Restart
Now I want to push this and return the original files

designgears said:
baseband_ota.img and mbm_combo.bin
Click to expand...
Click to collapse
Lol damnit lying in bed so tired , but so tempted by what ever mbm_combo.bin is but linux machine and keyfind back at my store only cr-48 and mac air here not enough processing power :-( anyhow thanks so much for post i cant wait to check it out. On side note you sure you going to leave dg ? I mean ever sense we got dock hack figured out im more leaning twoards keeping it . . Also because this is first cheep device i have bought $150 small invesment payed $500 or more for most my devices and cause i think we will get bootloader now and something seems weird abiut that dev dump of gb being vanilla. Maybe an option they will offer to quiet the devs anyhow at least keep posting us the leaks if you wont stay

designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse

Im not a dev far from one but from what i am reading this sounds like some pretty good information has been gathered just from this old update.....Also you dont have to stay just keep the leaks and any others a coming....Thanks

it seems as they signed all of the partitions... have you guys looked at the odexed version.... under recoveryand overall... what are they trying to patch... BZIP2 is attached and renamed "updater"??? Also traces of BSDIFF just like in other moto images... .
Also this is from the radio_baseband image...
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_target.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_nand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_onenand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_shared.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_clk.c
OLYMPUSBP_N_01.61.01P.dbl

hassanjanjua2002 said:
designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse

zambezy said:
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse
Not saying that I will do it, but; How would we flash those *.bin files to the phone?

mp2ning said:
Not saying that I will do it, but; How would we flash those *.bin files to the phone?
Click to expand...
Click to collapse
I'm guessing with NVFlasher

Fix For Dinc BootLoop with no recovery from NVRam Update

I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
update:
Since megaupload is down and Had some people asking for a re-up here's a mediafire link to the file
http://www.mediafire.com/?cu7hu6pu75zvskh
Also as mentioned below by eljean this should work on the SLCD as well it's just your screen will be blank during the process. For those who has this Dinc I found that if the screen is blank wait a few minutes for it to fully boot then test to see if you can execute any ADB command. If you can the just type "adb reboot oem-78" this will reboot it and put it in fastboot mode which will allow you to execute the commands in the document.
update 2:
Nevermind what I said about the ADB... this worked for me on another phone but I realize you'll probably won't get to a point where you can execute the command because your phone in a loop LOL. So I guess getting to fastboot blind folded is your only option

dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
That's a great find and good little zip/guide to get it set up.
The engineering HBOOT can be quite useful for many things besides flashing/erasing certain partitions. The inc community just hasn't used it that much.

tdiman said:
That's a great find and good little zip/guide to get it set up.
The engineering HBOOT can be quite useful for many things besides flashing/erasing certain partitions. The inc community just hasn't used it that much.
Click to expand...
Click to collapse
.77 Will not work on a Slcd Inc, if on Slcd we have no eng

HELP, I am having this problem with my incredible with an SLCD i put the .77 hboot on and then put the other zip in. I couldnt see the screen so i put it in fastboot by memory. I got remote failed errors the entire time.
Should I try putting the evo Hboot on this. I have no idea what else to do.

mattjt21 said:
HELP, I am having this problem with my incredible with an SLCD i put the .77 hboot on and then put the other zip in. I couldnt see the screen so i put it in fastboot by memory. I got remote failed errors the entire time.
Should I try putting the evo Hboot on this. I have no idea what else to do.
Click to expand...
Click to collapse
DO NOT USE EVO HBOOT
I don't know how to help you but I'm almost 100 percent sure that will brick it
Sent from my DROIDX using XDA App

mattjt21 said:
HELP, I am having this problem with my incredible with an SLCD i put the .77 hboot on and then put the other zip in. I couldnt see the screen so i put it in fastboot by memory. I got remote failed errors the entire time.
Should I try putting the evo Hboot on this. I have no idea what else to do.
Click to expand...
Click to collapse
The guy above you kinda said .77 won't work with SLCD... I honestly don't know how to fix that, but do NOT flash an Evo HBOOT.
I don't wanna come back and see you saying you flashed it anyways lol.
Sent from my Droid Incredible running CM7.0.3.

im sorry to revive an old thread but I cant seem to do this everytime I try to execute a command it responds with
FAILED (Remote: Not allowed)
any help?

Boot poop?
Sent from my Synergy Rom

masully1984 said:
Boot poop?
Sent from my Synergy Rom
Click to expand...
Click to collapse
ummm what?

OMFG MAN I LOVE U SO MUCH !!! I FIXED IT !!
The error I was making is that the Hboot you provided is within a .zip file but I didnt know and then I saw. It turned the screen all black because I have a SLCD Incredible but then I just did everything basically blind folded. You just saved me $200 !!! I EFFIN LOVE U MAN, WHENEVER U COME TO NYC WE PARTYIN BRO !!!!

GRATZ
+1
I forwarded this to Eljean but apparently they found this thread first.
Way to go. I never even imagined my write-up helping the Incredible people.

New Method
I got bored and created a more streamlined version of this fix.
I hope it works, I don't have an Incredible to test with.
http://www.multiupload.com/XS5SQL8Q9K
it includes everything needed (even ruu) and it does it for you
Also if anyone has this issue for an HTC Evo I posted this same method at
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54

cutthroatamft said:
I got bored and created a more streamlined version of this fix.
I hope it works, I don't have an Incredible to test with.
it includes everything needed (even ruu) and it does it for you
Also if anyone has this issue for an HTC Evo I posted this same method at
Click to expand...
Click to collapse
Hey there, I think this is a solution to my problem... I have an Incredible S. Would it work with it, if not what would I have to change? Can you re-upload the file somewhere, all of the links are down.
Thanks, Ned

cutthroatamft said:
I got bored and created a more streamlined version of this fix.
I hope it works, I don't have an Incredible to test with.
http://www.multiupload.com/XS5SQL8Q9K
it includes everything needed (even ruu) and it does it for you
Also if anyone has this issue for an HTC Evo I posted this same method at
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
Click to expand...
Click to collapse
Same here. This might fix a problemed dinc I have but the links are broken.
Sent from my ADR6300 using XDA App

same here it might fix my problem plz someone update the links

link
Can anyone provide a new link to this? my incredible just keeps booting up to the white screen and then rebooting. its an slcd.

I do have this file! It didn't work for me because I'm s-on bit I held on to it. Don't know how or where I could upload...mayb I can email it??..

Can you please attach it to a post in this thread? I have the same thing going on with my amoled incredible.
Thanks.
Sent from my ADR6400L using XDA Premium App

smtom said:
Can you please attach it to a post in this thread? I have the same thing going on with my amoled incredible.
Thanks.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
it wont upload? i think the file may b too big....

strive53 said:
it wont upload? i think the file may b too big....
Click to expand...
Click to collapse
How big is it? I have an Inc that could REALLY use it. Do ya need a place to upload it to other than here?