Related
Since there are many newbies here who are new to the world of flashing I've decided to do them all a huge favor by posting this thread. If there are other tutorials around, I'd suggest the mods sticky them please. I'm going to make this one as user friendly and easy as possible.
Okay. So you're bored of the stock HTC ROM eh? Never fear, the XDA cooks are here
If you are using an XP machine, you are good to go. If you are using Windows Vista or Windows 7, then go to this page and follow the instructions here to roll back the drivers. THIS IS IMPORTANT IF YOU'RE ON VISTA OR 7 BECAUSE OTHERWISE YOUR PHONE WON'T CONNECT IN BOOTLOADER!
Also, take note that while doing ANY kind of flashing, always remove both your SD card and your SIM card. ALWAYS.
Firstly, you will have to CID unlock your phone. Download the USPL and follow the instructions to flash it onto your phone. What, still need instructions? Okay.
Unzip it.
Connect your phone (WHILE IT IS RUNNING, NOT IN BOOTLOADER)
Click start_uspl.exe
Wait till the process finishes.
The phone will automatically reboot. During boot up, you will see a few numbers on your white HTC screen. Look out for the SPL number. If it is 1.11.0000, then you have been successful in unlocking your phone. If not, well, you have to try again. Mostly it should happen in the first go.
Now. Once your phone is CID unlocked, you can download any ROM you want and flash it to your device. Lets say you are kind to me and download one of my ROMs (see my sig )
*Before you flash any ROM though I strongly suggest you update your USPL to the new cmon USPL. This improvement lets you flash ROMs of ANY size to your device. To flash this, just download the file, and replace the ruu_signed.nbh file located in any of my (or anyone else's) ROM package with the one included in cmon USPL.
Then, put your phone into bootloader mode. To do this, switch your phone off. Then press the voice recording, power and reset buttons together. After 5 seconds release the reset button, but keep the other two pressed till you see a three colored screen. Once you see the screen you are in bootloader mode.
Once in bootloader, connect the phone to the PC. Once it is connected run the RUU.exe located in the folder where you just put the cmon USPL .nbh file. Keep pressing next and finally press update. It will be done in 2 seconds. On next boot your SPL version will now say 1.11.cmon. Yay, success.
Now you are ready to flash any ROM of your choice. Download whichever ROM you want, and unzip the package into a folder. The package will have around 6 files. Of them, only RUU.exe and ruu_signed.nbh are important. Once you check for these files, put your phone in bootloader mode again, connect to PC and start RUU.exe. Like cmon USPL, keep pressing next and then update. Soon, you will have a progress bar on your phone as well as your computer screen. The flashing process will be complete in 10 minutes.
The phone will reboot once the flashing is done. Now you can kiss old stock ROM goodbye! On system reboot, the phone will take some time to start, and it will ask you to "tap screen to begin setup". Do as the phone tells you to, align the screen, enter the date and time and your new flashed ROM is ready to use!
I hope this post helps all the newbies out there in flashing their devices. Be warned, you have to be careful while doing this or your device might end up as a very attractive brick. It is very easy and I'm sure all you people can manage it.
Special thanks to:
pof and cmonex for their USPLs
All the brilliant cooks of Artemis XDA
*If I made any mistake in this the experienced people can bring it to my notice and I will make changes. Everything is correct best to my knowledge
Did you mention remove memory card? Also Vista users need to change USB drivers !
Yes, thanks bazzywazz I missed out on thos epoints. First post edited
And on phone usb settings uncheck "enable advanced network function"
Hi all!!
Ever since I got my Sprint Vogue, I have spent God only knows how many hours looking for and gathering information regarding this phone (flashing instructions, unlocking, SuperCID, etc). There are a few sites that have fairly comprehensive guides as to how to do this, but there are very few posts in the Vogue Section here at XDA-Developers.
Having said that, I figured I would create my own "How to Flash Your Vogue"-Thread. This is a multi-step process and I cannot emphasize the importance of following every step down to the "T", that is unless you are looking for a silicone-skinned brick...
Who is this guide for?
*Anyone with a CDMA version of the Touch. [highlight]That means no GSM[/highlight]
*Noobs and Seniors alike.
*People who have trouble flashing their devices.
*Anyone looking for links to more information.
*Curious people in general.
*Anyone willing to get rid of the nasty stock rom and looking for a newer and cleaner OS (notice that I never said more stable, so do not blame me afterwards ).
[highlight]Please keep in mind that there is always a chance of bricking your device with these procedures. I will not be in any way, shape, or form responsible if you damage your device while doing this.[/highlight]
Got your coffee? Alright, let's do this.
Step 1. Preparing the device
As with every phone, you have to make sure that you have the following things done before flashing:
* Battery charged at least 50%.
* All the necessary programs (see next post).
* Instructions handy.
Make sure that you back up all your information (contacts, e-mails, files).... essentially, anything that you would like to keep post-flashing. You can do this via Active Sync/Mobile Device Center or via third party software (PIM Backup is really good)...
You will have to reinstall every last piece of software in your device as it will be hard reset. Some programs may work if installed in a SD card directly, but a lot of them write things to the registry and copy files to the device, which they require to run. Long story short, keep all your cabs and exe files in a safe place so you can restore later if needed.
Step 2. Unlocking the Device (HardSPL)
Unlocking the device is done so that you can flash custom roms in your devices. The unlocker that you are about to download and use was provided by "ImCoKeMaN" at PPCGeeks. If you are interested in the full thread, please click here.
If you have read the above link, you will see two versions of the HardSPL (0.40 and 2.31). Simply use 2.31 as it works fine with most devices.
[highlight]To use this under Windows XP,[/highlight]
1. Connect your device to your computer and make sure it is synced with ActiveSync.
2. Download and extract the contents of the zip file, which is an exe. Let it run to completion. You will be prompted to disconnect and reconnect your device at one point in the process. Do it... don't worry
3. It will look like it is flashing a rom via a RUU. Do not disconnect the device after it is done!!!!!
4. Once it is done flashing, you will see a prompt that says that it will run exitbl. DO NOT DISCONNECT YOUR DEVICE. At this point, open ActiveSync, go to File>Connection Settings> Uncheck "Allow USB Connections". Continue following the on screen instructions and let it finish.
5. Go to bootloader once more to verify that it worked. You should see 2.31 CoKe MFG.
[highlight]To use this under Windows Vista/7 x64 (thanks jitajt),[/highlight]
jitajt said:
connect your device to WMDC (it's not necessary to set up device, just connect without setting up device)
then right click on the 2.31 unlocker and run as administrator
follow the directions, you will get an error about sleep.exe not being compatible with x64 but just hit ok and continue, (you will get about 10 of them)
then just keep following the directions in the command prompt and it will put your phone into bootloader then you have to disconnect and reconnect when it tells you to. and it will flash your phone and reset it. then your done you can close the command prompt and disconnect your phone.
I did it just like above and I have not had any problems.
Do this at your own risk as I am not responsible for your phone
Click to expand...
Click to collapse
Step 3. Flashing your Roms
The time has finally arrived. You sat down patiently through the unlocker and you are now ready to take the leap of faith into what you believe will bring your device to a new level of usefulness (also known as getting rid of that nasty, bloated, stock rom )
The process is relatively simple:
1. Download the RUU package from this post. I am only posting this because some cooks only post the rom nbh files rather than the whole package.
2. Go into the threads and look for whichever rom you prefer. Look at my signature to learn which one I am using. NFSFan (my current one) is by far the best one I have tried so far. You can download it from here
3. Put your device in bootloader mode and connect the device to the computer. [highlight]Once in bootloader, activesync will NOT see the device. If the RUU gives a connection error, try to run it with the devices in regular mode (with ActiveSync connected)[/highlight]
4. Open the Romupdateutility.exe and follow the steps.
5. Once it is done flashing the rom, disconnect it from the computer and hard reset it. To do this, simply hold "Send" + "End Call" +Stylus in the reset hole for about 3 seconds. It will prompt you to erase all the data and restore to factory defaults. Press "Enter", which is the center button in the directional pad. Once it is done, press "Send" to reboot.
Congratulations, you just flashed your first rom for Vogue
Step 4. SuperCID
This step can be skipped if you are not thinking of doing anything as far as your radio (such as flashing radios other than the ones intended for Vogue). This is also used to do other things such as modifying certain important things on your device such as the NV files, which is information that will not be discussed here. However, if you are interested in finding out more, simply google it, there is a ton of information out there.
Anyways, back to SuperCID... here is the procedure (thanks to hpnasik at mobile-files.com for the post)
1. Download the following special rom . This is an Alltel rom with radio 3.37. This was specially prepared to be able to reduce the Security Level of the device to level zero.
2. Download mtty since you will need it. Do not worry if you do not how to use it. You will have a step by step in this guide.
3. Flash the Alltel rom from above.
Now comes the fun part...
4. Disable USB in Connection Settings of Active Sync
5. Boot The Phone holding power button and camera button to enter bootloader.
6. Phone Will Display Serial in Bottom
7. Connect Phone to PC
8. Phone should Display USB instead of Serial in Bottom
9. start mtty.exe
10. Select All Default and Connect to USB in drop down box and Shoot the Following Commands (All Commands are case Sensitive)
11. run command rtask a : After this Command Phone will not Display any thing
12. run command echo_on : even though nothing is shown to screen
13. run command readCID : in Sprint it will display SPCS_001
14. run command writeCID 00000000 : Set CID Value to 00000000 replaces SPCS_001 in Sprint (This make PPC Radio Security Level to Zero)
15. run command readCID : This will Display the Update CID as 00000000
16. run Command retuoR : This will return to Original Boot Loader State
Congratulations, you just SuperCIDed your device. Original thread with the instructions can be found here if you are interested.
Step 5. Flashing your radio.
Now that your device has been SuperCIDed, you will have the opportunity to flash radios that have been ported to this device (ie. there is a version of the 3.42.40 radio for the Titan, which has been ported to the Vogue). There are two ways of doing this:
Way 1: Do it by flashing via RUU (same as with flashing a rom)
Way 2: Flash via microSD card. Simply put whichever radio that you wish to flash in the root of a 2GB or less microSD card formatted to fat32. Rename the radio to VOGUIMG.NBH and put your device in bootloader. The flashing will start by itself.
Way 3 (I know I said two ways...): There are a few stock roms that come with new radios. One of them can be downloaded directly from HTC and it is for the Sprint Touch. This one comes with Radio 3.42.30
The other one is for Bell Mobility and this one comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options seem much easier?? I have run into the problem where my device would not let me flash other radios than the one that I had. SD card method did not work and the RUU started out fine but quits at 8% rebooting my phone and displaying Error 328 in the RUU on the PC. Anyway, here are the links...
Sprint rom with radio 3.42.30
Bell rom with radio 3.42.50
Verizon Stock Rom
All Shipped Roms (All Carriers) - Thanks conflipper!
All Above Radios zipped
The newer radios perform a little better and give out better GPS signal (faster locks)....
Hang on a sec... did you just say GPS?!?!? But my Vogue does not have a GPS.... It does, just read a little further and be happy
Step 6. Enabling GPS, Returning to Stock, and Carrier Cabs
As I said before, there is a GPS hidden on your device. Now, if you are like me and went straight to the specs of the phone to confirm, you will probably try to call BS on this. Long story short, there are a few custom roms which have this "tweak" already implemented (like the one I am using from NFSFan). If you require some more info, I will post it later...
[highlight]Location must be on or else your GPS will not work. To activate it, go to Settings>Personal>Phone and change the Location setting to ON instead of 911 (thanks for pointing it out, th3lolz)[/highlight]
[highlight]For Verizon Users[/highlight]
br125 said:
For those of you with the official mr1 update from verizon that cannot get their gps working:
My xv6900 came with the official update and I got it working, it involves downgrading to a NON-GPS radio, then back to a gps radio...
go here: http://forum.xda-developers.com/showthread.php?t=533639
now the instructions are going to imply that you must load the unlocker before each flash... bs don't worry about that
1. flash the .40 unlocker
2. flash the non-gps rom (reset before customization)
3. flash the 2.31 unlocker
4. flash the vzw rom (reset before customization)
5. flash any custom rom or android rom
that's it, time consuming, but it works
*ignore the multiple flashing instructions, its completely unnecessary, I've never flashed more than once with no problem ever....
I also suggest keeping the vzw radio, but do as you will, I like the 3.37.38 radio.. ain't broke don't fix it
lastly, just make sure you RESET BEFORE THE CUSTOMIZATIONS RUN...... that is what locks your gps.
good luck!
ps. the verizon radio rom that is in that post is for the "leaked" 3.37.37 radio, I reccomend using the official update from verizon here for the 3.37.38 radio rom instead:
http://www.pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon Wireless
RESET BEFORE CUSTOMIZATIONS
Click to expand...
Click to collapse
[highlight]How to Relock you phone[/highlight]
If, for whatever reason you need to return your phone for repair/replacement, you will need to relock it. To relock your phone, simply run the unlocker 0.40 and flash the stock rom of your carrier.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
[highlight]Carrier Cabs[/highlight]
Thanks to Codybear for gathering all of the cabs with settings for various carriers. But since the link went down, here is another one courtesy of LMiller1708
https://sites.google.com/site/vogueroms/vogue-files
This information was only gathered by me and I take no credit whatsoever other than trying to put it in a one stop thread. Thanks to the following people
Shadowmite
ImCoKeMaN
mindfrost
NFSFAN
Codybear
joshkoss
and a bunch of people that were involved in developing all this...
Thread sticky'd as requested
Peace,
Josh
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
dwigginstm said:
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
Click to expand...
Click to collapse
How exciting!! My first victi...erh patient
Did you put the device in bootloader mode? If you did and it is connected to the PC, you should see USB on the screen of your device. Also, do you have ActiveSync on your XP machine? You will need it for the drivers on this step. Changing USB ports sometimes help as well. And one last thing, do not use a USB hub, go directly through the USB ports in your computer. Good luck!
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
yes i have activesync set up with the phone and pc, but when i put the phone in bootloader mode and connect it the pc recognizes it but not activesync. is there another program i can unlock the phone with?
dwigginstm said:
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
Click to expand...
Click to collapse
Do not worry about ActiveSync. While you are in bootloader, the device is not running WM, which is why your computer only sees it as a USB device. This is perfectly fine. ActiveSync will not recognize it.
Please, follow the instructions in my post for unlocking. Read it thoroughly and try to understand it, else you will end up bricking your device.
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
dwigginstm said:
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
Click to expand...
Click to collapse
that is a message in the RUU. do not pay attention to it. good luck...
so i finally got the unlocker to start and it begins the ten minute process and stops then show a 262 error code ive done this over and over again
Let's go from the top. I just saw the message that you were talking about. The unlocker does ask for ActiveSync as you pointed out and it is asking you to connect the device to the computer. Then it asks for you to press any key when that is done. So, try that and you should see the word "initializing" with a dotted line getting longer for about 20 seconds. Do that.
The RUU will start up afterwards. The prompt will tell you that it is going to flash a new SPL, and if I am not mistaken that is where you are getting stuck.
Just out of curiosity, which version of the Vogue do you have? (Alltel, Bell, Verizon, Sprint, US Cellular)?
no internet
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
terrancextc said:
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
Click to expand...
Click to collapse
You downloaded a cab. Simply put it in your SD card and run it by tapping on it. Don't unzip it...
Unlocker is not 64 bit compatible... grrr....
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
obones said:
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
Click to expand...
Click to collapse
Not sure if you do or not but do you need to have Htc Sync installed for the drivers?
I do have HTC Sync installed
Are you rooted? You need root to do this. If you are then why not use fake flash or unrevoked to enter recovery.
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
obones said:
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
Click to expand...
Click to collapse
Recovery-windows.bat won't work unless you are rooted. The screen with the red triangle isn't actually recovery mode. The .bat file you would run pushes the recovery to the phone.
If you are not going to root, then you can get an app from the market that puts your phone on silent as you switch it off, and then back to normal when it's booted. This disables the boot sound. It's called silent boot I think.
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
obones said:
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
Click to expand...
Click to collapse
try fake flash? ive never used it so i duno if u need to be rooted
Fake flash needs root. No custom recovery will work without root. Quite simply, if you are not rooted you will not have write access to /system
please help.
i try to install froyo rom.
after flash FroYo_inkreDroid (14.07.2010) rom (throught standart flashrom procedures by update.zip) the device will not boot into os. i try update modem and after this the device win not booting to recovery mode.
i try press both combination (back key + power and volume down + power). the result of both combination is: 7 short vibro signals and black screen.
please help me, how me recovery my device.
thnx and sorry for my english.
your going to have to root it.
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Edit:
Rooting this device has been made possible by GT35pro. See posts below.
same problem
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
CWM installed and rooted the HDC galaxy note 2 MAGE / MEGA
rebmoe said:
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
Click to expand...
Click to collapse
I just created the cwm recovery and root. The link is on my blog. The zip file is password protected so be sure to get it from my blog page.
http://gt35pro-mobile-gadgets.blogspot.sg/2013/02/cmw-recovery-english-and-root-for-hdc.html
After you have clockwork mod recovery, use it to flash the root access into the phone.
Have fun!
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
londonflu said:
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
Click to expand...
Click to collapse
The one I got did not have that screen calibration problem. Everything works good. Anyway, root is available now.
Superb!
Thank you for sorting this out!
-KristN91
Extra Guide
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
S_ft_need_download_all_fail (4050)
I'm trying for several days, but always get this error in the flash tool: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Tried on Windows 7 x64, Windows 7 x32 and Windows XP SP3 (x32). Only on the Windows XP computer I was able to make a backup with Flash Tool using the Read Back option.
When I try to flash the red bar goes to 100% then the error message shows...
Does anyone get this error aswell, and did someone manage to solve this?
Please help, I'm in desperate need for root because I need touch screen calibration.
Thnx!!
YES! SUCCES!! I managed to root my HDC Mage :laugh: Did use another method though, check http://forum.xda-developers.com/showthread.php?t=2160490 if you are interested.
Anyway, now back to calibrating the touchscreen. What tools are good do fix touchscreen issues? I already tried http://forum.xda-developers.com/showthread.php?t=934500, but I still am not satisfied.
Thnx :good:
Just curious, if anyone that owns an HDC, is actually located in the USA?
londonflu said:
Just curious, if anyone that owns an HDC, is actually located in the USA?
Click to expand...
Click to collapse
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Because I tried to order 5 different phones from China including Fastcardtech; they couldn't ship for some reason; even got an empty box from ZOPO mobile. I ended up buying the BLU here in the US, I'm kind of glad it happened, since now I have an N'vidia Tegra 4 CPU, that runs circles around the dual-core phones.
I did order one more phone on ebay from China, been waiting for 2 weeks now. MAKES ME WONDER IF THEY EVEN ACTUALLY SHIP TO THE US AT ALL?
Thank to Paypal I was able to get refunded everytime.
KristN91 said:
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
Click to expand...
Click to collapse
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
thank you
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
farazafs said:
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
Click to expand...
Click to collapse
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
jg77 said:
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
Click to expand...
Click to collapse
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
farazafs said:
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
Click to expand...
Click to collapse
There is something wrong in the layout of the scatterfile. Can you post the logiles of sp flash tool? Just zip them all together.
I have had the exactly the same error with my HDC Mage. I just had to rename a small section of the scatterfile and then it was all good.
[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!
THIS GUIDE CAN APPLY TO ANY MODEL, PROVIDED YOU ENSURE TO GET THE PROPER FILES FOR YOUR VERSION!
I've had success myself flashing stock firmware from the M919V for Wind Mobile onto my I337M with no issue. This shouldn't be an issue. However, for the purpose of this guide, it is important that you get the firmware that was intended FOR YOUR DEVICE!
This was originally posted in the I337M forum as that's what I have, but here you go!
---
First head over here >> http://forum.xda-developers.com/showthread.php?t=2559693 >> and check out the original thread that helped me get to this resolution. Thank you to all the lovely people there!!
Before my softbrick occurred, I had flashed the NE1 modem through ODIN. I found that the same modem remained regarldess of the firmware I flashed. So I thought to match them up and give it another go. This worked great. This will work even if it was a regular S/W upgrade or install that caused the no sound and/or WiFi and/or Bluetooth issue.
Quick note before we begin: this guide assumes that you already went through a softbrick and have successfully come back from it, or went through a software update/firmware install which resulted in the same issue. Some of the steps in this guide may be able to be applied to some parts unbricking a phone, but this is NOT the intention. The intention is to help recover sound, WiFi and Bluetooth AFTER a successful unbrick or failed update/install otherwise.
DISCLAIMER: I am not responsible for your phone melting, imploding, turning into maple syrup or dying. Follow at your own will!
PRE-GAME CHECKLIST:
- Determine the ORIGINAL FIRMWARE that came on your device (this one was important for me, not sure how crucial it may be for others) - to be honest, I'm not 100% sure how to figure this out other than looking at the phone's box. It should notate which software version (SW-VER) it is. Before doing this, I was soft bricked, and had to use the very original 4.2.2 software for my carrier to recover from THAT. So maybe this part wasn't as important as I think, but I wanted to mention it anyway.
- The ORIGINAL USB cable for the phone - I suspect any high quality ones would work, but the one that came with the phone is a no-brainer
- ODIN 3.xx (I used 3.09)
- Samsung USB Drivers installed properly
- NO SD CARD (to be safe - this is optional as it should not be touched throughout the process)
- DO NOT, under any circumstance, use a USB hub for this procedure. Make sure it's direct into your computer with no extensions. I also recommend a cable that is 6ft or shorter if possible, but the quality of the cable is the most important
DO IT:
1) Download the ORIGINAL firmware that came with your phone (if you weren't able to determine this, I'd say the most recent one should be safe to flash, unless you softbricked while on 4.2.2 or 4.3 - in that case I would stick with the corresponding version, though I'm not sure how it would be affected since I didn't run into this)
2) Extract the file (I use 7Zip) and ensure there is one .tar.md5 file as a result - do not extract again
3) Boot up the phone into Download Mode (PWR off completely, then hold VOLDOWN + HOME + PWR together until the warning appears on the screen - click VOLUP to accept and proceed)
---PHONE WIPE---
This part is optional but I highly, highly recommend it.
4a) Flash Philz CWM (you can find the file and instructions on how to flash it through ODIN very easily)
4b) After flashing, it usually reboots into recovery. If it does not, do so manually: turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on.
4c) Make sure you close ODIN once confirmed the flash is done
4d) Tap factory reset and confirm it
4e) Once done, choose the clean ROM install option and confirm that as well
4f) Reboot the phone and continue on with the steps
NOTE: if there is anything to backup, now would be a good time to do this.
---
5) Open ODIN (IMPORTANT: In Windows, right-click and choose "Run as administrator" - this helped avoid an error for me)
6) Connect your phone directly to a USB on your PC and confirm that ODIN recognized it (it should highlight the first box and have "COM#" listed)
7) Click the second section (AP / PDA) and choose the .tar.md5 file you got in Step 1
***NOTE: ODIN may look like it's freezing or hanging here - IT IS NOT, BE PATIENT - it is a large file and it will take a bit of time to verify the MD5 for it
8) Click Start and sit back - it should take 8-10 mins or so (8:55 for me) with KitKat, and 5-7 mins or so with JB.
9) Your phone should have rebooted into a fresh Firmware. If you hear the Samsung boot sound, GREAT! You should be good (test WiFi and Bluetooth if possible) and you're done. Assuming that's not the case, which is why you're here, proceed to the next step
***If it's stuck in a bootloop, you need to force Recovery mode and do a factory reset. To do this, turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on. Use the VOL buttons to scroll to the factory reset option, and choose PWR to select. Then confirm on the next screen. Once that's done, wipe cache in the same way. Then, reboot, again in the same way. Now your phone should boot up
10) Go through setup and then go into Settings > More > About device. Observe the "Baseband version" section, and see if it matches the "Build number" section (starting from I337 and onwards). IF THEY MATCH, then repeat steps 5-10. IF THEY DO NOT MATCH, continue.
11) Download the matching modem file - ENSURE that the version of the modem you download MATCHES EXACTLY with the "Build number" in your phone's settings. Flash the file in ODIN in the AP / PDA section (if you need detailed instructions on this, it's a snap to find in XDA or Google)
12) Once done, reboot into the regular OS and verify that the "Baseband version" and "Build number" sections MATCH. If not, try to flash the modem again. After this has been verified, go ahead and follow steps 5-10 as many times as necessary until you hear that beautiful boot noise! It took me twice.
All the best and happy flashing guys! I'm not too much of an expert, just very good at explaining things, but I'll try to help as I can with any questions!
THANKS:
- All the great help thanks to input from around XDA in this thread (also listed in the beginning of this one): http://forum.xda-developers.com/showthread.php?t=2559693
- All the devs that work hard for us Canadian and AT&T guys over here