Ok guys,
i think i'm in a sort of big trouble. I got SPL1.2, i was installing this Miky ROM and then at 91% Windows Mobile Device Center crashed on my pc. Now what i have is a 7500 booting with strange lines on the screen and then fading to white. I tried to pull out the battery and then to recover but nothing is working. I broke my 7500??? Why God is never here when i need him???
See if you can get into bootloader (tri color screen) if you can flash a factory rom. Have a look here, you should find what you need or a link to the needed resources http://forum.xda-developers.com/showthread.php?t=429013
Cheers
BR
***Why You Try This !!!___carefully step by step !!!!!!!!
cmonex
Senior Member Join Date: Jul 2006
Location: Budapest
Posts: 2,314
--------------------------------------------------------------------------------
here's an experimental program I made to make the process more automatic so users can fix their own wifi without our help.
this is good for both corrupt modelid and corrupt wifi, and fixes both at the same time.
STEP BY STEP:
1. download attachment at the end of the post for mac1.exe (requires .net 2.0 installed on the PC)
2. you will also need to download the other attachment in this post for the mtty program.
3. enter bootloader (tricolour screen) manually by pressing and holding camera button all the way in (yes I mean that, press it in as hard as you can!!), while doing a reset, then keep the camera button held until you see the tricolour screen.
4. disable USB in activesync (wmdc if you have vista - in this case, do not kill wmdc, just disable usb in it!!!)
5. run mtty and select USB option from the dropdown box!
6. then press enter in main window that comes up, see if that gives you Cmd>
7. now you should have Cmd>, if not, re-check if you did the above steps right until you get Cmd>
8. now run the mac1.exe, type in your MAC address you want to use for the Athena, if you have SPL 3.xx reported on the tricolour screen, then use the button for SPL 3.xx, otherwise if you have SPL 1.xx reported, use button for 1.xx.
9. this should have generated a .bin file for you, copy that bin file in the folder of mtty.
10. now, in mtty, type (do not copypaste!) this command: task 32
11. this should return Level = 0
12. now, you must only do one of the two following commands:
- if you have SPL 3.xx, then type (do not copypaste!!) this command: lnb filename.bin 76508000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
- OR, if you have SPL 1.xx, then the command is different (do not copypaste!!): lnbs filename.bin 75108000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
NOTE, the command starts with a lowercase "L", not "I"!
WARNING: PLEASE DO NOT MIX UP THESE TWO DIFFERENT COMMANDS!!!
if this info helps: most people will have SPL 3.xx, and if you have AP4 (not vanilla) already running then you're definitely 3.xx
13. mtty will popup a window asking "OK", you press OK!
if you get "Fail to synchronize with the host (1)", then make sure you did follow step by step. if still same error, try placing mtty and the bin file under C:\.
14. now the file downloads, if mtty reports it flashed the file, and at the end "code entrypoint unknown", then that's it, now boot back to WM and see if wifi works.
edit: see raskell's mtty tutorial too, #36. post in this thread
if you *really* can't manage to get it working, you can still feel free to PM me.
let me know if this program and step by step description helped any.
Attached Files mac1.zip (6.3 KB, 1585 views)
mtty_0513_Test.zip (553.9 KB, 1883 views)
__________________
Here is direct link__on floor #33 ===>
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Good Luck!!!
Obligatory reading before you begin: So You Want to Root and Mod Your HTC Phone
Introduction
Credit goes to Bin4ry for developing the loop-restore trick that applies to many phones, and of course CaptainRewind and jose51197 for being the first to demonstrate its applicability to the HTC Droid Incredible 4G LTE. Since that time, I have put quite a bit of work into writing these automated scripts. I am splitting them out of the original thread so that I can give them a proper home and continue to maintain them. With the start of this thread, I'm also introducing a Linux variant of the script.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usage - typical procedures
All of the below procedures assume you're still using a phone with a locked bootloader and S-ON.
Prerequisites:
Windows users: uninstall any HTC software you currently have installed (e.g. HTC Sync) and install the HTC drivers from this post. Only unlimited.io's S-OFF requires a certain driver version. Other procedures can use the latest version.
All users: Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
HTCDev Unlock: unlock the bootloader, install a custom recovery, and install superuser (for root access):
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Use task 3 of the script to revert the CID to stock (this will not affect unlock)
Unlimited.io S-OFF (DirtyRacun):
Follow the instructions for DirtyRacun: Fireball at unlimited.io very carefully
When you get to Temproot your phone via any method available, use task 6 of the script to put your phone in temp-root mode.
Continue the instructions for DirtyRacun
Facepalm S-OFF:
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Follow the directions for Facepalm S-OFF
Use task 3 of the script to revert the CID to stock (this will not affect unlock or S-OFF)
Flash the DirtyRacun HBOOT from unlimited.io - follow the instructions on the right sidebar
Notice: Windows users can run these commands by removing sudo ./ from each line.
Cautionary Notes about OTAs
When (if) fireball gets an official jellybean release from HTC/Verizon:
It is crucial that users have their CID as VZW__001 (and not SuperCID). It seems OTAs (over-the-air updates) for other HTC devices have caused bricks for users who are S-ON and SuperCID. I strongly recommend users revert their CID after unlocking or doing facepalm S-OFF.
New touch firmware may cause compatibility issues when switching between ROMs. If possible, delay updating while devs work on testing ROMs with the new firmware.
With this said, I really have NO clue whether we will ever get an official jellybean release.
Linux script notes
The linux script will only execute properly in a bash terminal!
After extracting, make runme.sh executable:
Code:
chmod +x runme.sh
Then, run the script:
Code:
./runme.sh
Manual procedures for reference
Windows
Before you begin
Uninstall HTC Sync and any other applications/drivers that come up with a search for "htc" in the uninstall programs list in Windows. Download and install the latest HTC Drivers from this post.
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a command prompt in the directory where you extracted Inc4GUnlockV6-Windows.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
The command prompt will appear to be hung. At this point you can accept the restore prompt on your phone. When the command prompt returns, type:
Code:
adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
copy cid mmcblk0p4.original
hexalter cid 0x214=0x31,0x31,0x31,0x31,0x31,0x31,0x31,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
adb shell "rm /data/local.prop /sdcard/cid"
del cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
adb reboot-bootloader
fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Windows.zip, then type:
Code:
fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
fastboot flash recovery recovery_file_name.img
fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
adb shell "rm /sdcard/cid"
del cid
Linux
Before you begin
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a terminal in the directory where you extracted Inc4GUnlockV6-Linux.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
./adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
./adb restore fakebackup.ab
./adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
The terminal will appear to be hung. At this point you can accept the restore prompt on your phone. When the terminal prompt returns, type:
Code:
./adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
./adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
./adb pull /sdcard/cid
cp cid mmcblk0p4.original
printf '\x31\x31\x31\x31\x31\x31\x31\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
./adb shell "rm /data/local.prop /sdcard/cid"
rm cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
./adb reboot-bootloader
./fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
./fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Linux.zip, then type:
Code:
./fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
./fastboot flash recovery recovery_file_name.img
./fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
./adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
./adb pull /sdcard/cid
printf '\x56\x5A\x57\x5F\x5F\x30\x30\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
./adb shell "rm /sdcard/cid"
rm cid
Changelog
Version 6.2
Linux: Fix incorrect use of grep when busybox is not available; update adb and fastboot executables
Version 6.1
Windows: (Hopefully) fixed hanging procedures due to std redirects
Linux: Allow more diverse device codes returned by adb devices
Version 6.0 - Initial Release (in this thread)
Great tool, wish I had this when I was did mine I wasted valuable angry birds time
Sent from my ADR6300 using xda app-developers app
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
kramer56 said:
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
Click to expand...
Click to collapse
I literally just put my palm to my face. You need to re-consider whether leaving your stock ROM is a good idea.
This post is relevant.
deserved. the original inc was just so easy i guess. this seems so much more involved with the windows os
I always flash roms with the og
mdmower said:
I literally just put my palm to my face.
Click to expand...
Click to collapse
I see why the new method is called Facepalm S-OFF now.
Well when i get to here adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; it asks on the phone for a encryption password and the cmd.exe says link not found and just keeps running that for 3 minutes then I exited out
maybe I am not extracting to the proper place, that is unclear to me, sorry
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
sidgallup said:
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
Click to expand...
Click to collapse
I have not seen a fireball with an FAXXXXXXXXX device code. Are you positive you have the Incredible 4G LTE (and not the Desire 4G LTE or Incredible 2, or Incredible S, or something else)?
It looks like you have two devices plugged in. If so, unplug the other device.
If you have HTC Sync or any other HTC software installed, remove it all and re-install just the driver.
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
that driver is for windows 8 i think you need 3.0.007 something like that.
Aldo101t said:
that driver is for windows 8 i think you need 3.0.007 something like that.
Click to expand...
Click to collapse
The 4.x drivers also work with Win7.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Do i need to use this same tool to get it unlocked using the HTCDev method?
sidgallup said:
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Click to expand...
Click to collapse
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
mdmower said:
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
Click to expand...
Click to collapse
Yeah, that's what i'm gonna do for now, i thought rooting this phone will be just as relatively easy as with my old Droid 2 Global but it's a completely different animal.
At least last week HTC announced they are updating stock to 4.2.2, with some luck our 4g LTE is getting the update too
mdmower said:
The 4.x drivers also work with Win7.
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
Click to expand...
Click to collapse
I stand corrected, thanks
Ok one last question just to be completely shure i'm not missing something... can i run the script witile the phone is ON or should i be running it with the phone in bootloader mode?
EDIT: ok i got it to work, that other "emulator" device was related to Blue Stacks App Player, as soon as i uninstalled it the script worked perfectly even when my phone wasn't listed as HTXXXX, just installed CM10 and everything is fine.
c:\Android>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
I am stuck on this, how do i get pass this the fastboot is there I see it but it won't run
I use windows vista home premium 32 bit
ok yesterday I got as far as the fast boot token on windows and now today the adb is out of date or something to that effect. every time I click sdk manager it has all the revision updates for platform and tools. yesterday it did none of stuff. My device is not found and when i run task 1 it say daemon not working switch to port 5037 and it does not list any devices. Should I do a factory reset on hboot screen? I just installed htc drivers ending in ....23 and still nothing. UBUNTU was a fail because nothing would auto run at all and I had to keep extracting to folders in which nothing found later not to mention no wireless on ubuntu either.
adb is up to date now but no device found, everything powers up just fine
wrong thread
Device in question, although likely not relevant to the issue I am having: Pixel 2 XL (Taimen). Let me know if there's any info I may have missed sharing that could help solve this.
My overarching goals here are:
1. Build vanilla AOSP "user" variant without root or any other additions
2. Sign the build with my own release keys
3. Be able to git-checkout release tags at a later time, build again, and produce OTA updates for this vanilla AOSP build
So far, I have been able to successfully build the latest release and flash it to my device using:
Code:
fastboot flashall
The device boots and runs as you would expect.
However, that is all using the test-key. I have followed the official documentation for generating release keys:
hxxps://source.android[.]com/devices/tech/ota/sign_builds#release-keys
The same documentation page provides the following listing for generating the release image:
Code:
make dist
./build/make/tools/releasetools/sign_target_files_apks \
-o \ # explained in the next section
--default_key_mappings ~/.android-certs out/dist/*-target_files-*.zip \
signed-target_files.zip
Apparently SignApk.jar doesn't work with password-encrypted keys (it throws an exception then swallows it which causes the whole thing to fail at a later point), and signing the APKs in the target files ZIP fails. Fine, I'm willing to use an unencrypted key for testing this project.
So I successfully get a signed-target_files.zip.
Lastly, the documentation provides the following for producing the release image:
Code:
./build/make/tools/releasetools/img_from_target_files signed-target-files.zip signed-img.zip
This also works successfully (minus the typo with the filename, switching the '_' character for '-'), so I use this to install:
Code:
fastboot update -w signed-img.zip
Then I get symptoms of the problem:
1. Warning that the bootloader is unlocked (fine)
2. White screen with "Google" logo
3. Reboot to bootloader
I never see the "android" splash screen after 2. like when I
Code:
fastboot flashall
to install the test-key version which does work.
So something else that I decided to try was to create an "unsigned-img.zip." I basically used img_from_target_files on the original, unsigned target_files.zip. and did a
Code:
fastboot update -w unsigned-img.zip
. This also booted successfully.
=====================
To recap:
1. Building is successful
2. "fastboot flashall" is successful
3. "fastboot update unsigned-img.zip" is successful
4. "fastboot update signed-img.zip" is NOT successful and always reboots back to the bootloader
Is there something I'm missing with regards to the image signing? If I'm doing this and having this issue on an unmodified AOSP branch, shouldn't everyone else be having these signing issues, as well?
Any help is appreciated.
It worked for me without -w argument:
Code:
fastboot update signed-img.zip