Develop Bugs

[REF] If odin gives error - unbricking

Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"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"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution

try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.

dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.

m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.

dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]

m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.

Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)

Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.

Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).

I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App

Maybe we should pin this or any other topic for people to post if they have bricked their device?

I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.

m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.

Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say

dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.

ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps

m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.

was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.

Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash

Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App

Camera problem for a total noob

I get a force close every time I try to put the camera in sport mode. I did search for threads dealing with this problem and found some. The problem is that I don't understand most of the terminology. Would someone be nice enough to give me step by step instructions on how to fix this. It is really aggravating.

Its basically a good example of poor coding by Samsung.
along the lines of adding a new line of code in the middle of the old causing everything to shift up or down..
The fix(s)
You need to be rooted.
flash one of the roms that have the fix included(read the details for your selected rom)
or..
use the original fix (don't need to be rooted for this one)
http://forum.xda-developers.com/showthread.php?t=970452
you would download the file, and flash it with odin. for the original.
pretty simple really.
All the roms have instructions on first page as does the "fix"
Since you are having problems with terminology ill walk the odin method
make sure you have the Samsung drivers installed
http://forum.xda-developers.com/showthread.php?t=728929
download the camera fix . its a .tar file
download odin
extract odin
put your phone into download mode.
you do this by (from an off state) holding 1 on your physical keyboard and the power button at the same time.
open odin (click the "odin 3+v1.6.exe icon in the folder you extracted to)
connect your usb (you should see one of the com squares light up" mine is always on com 4")
click on "pda button" browse and set the camera fix .tar there
unclick where it says F.reset time
click start
let it run
your done
I am not the best at explanations. But i would like to see you get this fixed
I attached a zip of odin and the camera fix .tar for simplicity

Did it understand what tmspyder was telling you? If you did give him a thanks
Sent From My Evo Killer!

tmspyder said:
Its basically a good example of poor coding by Samsung.
along the lines of adding a new line of code in the middle of the old causing everything to shift up or down..
The fix(s)
You need to be rooted.
flash one of the roms that have the fix included(read the details for your selected rom)
or..
use the original fix (don't need to be rooted for this one)
http://forum.xda-developers.com/showthread.php?t=970452
you would download the file, and flash it with odin. for the original.
pretty simple really.
All the roms have instructions on first page as does the "fix"
Since you are having problems with terminology ill walk the odin method
make sure you have the Samsung drivers installed
http://forum.xda-developers.com/showthread.php?t=728929
download the camera fix . its a .tar file
download odin
extract odin
put your phone into download mode.
you do this by (from an off state) holding 1 on your physical keyboard and the power button at the same time.
open odin (click the "odin 3+v1.6.exe icon in the folder you extracted to)
connect your usb (you should see one of the com squares light up" mine is always on com 4")
click on "pda button" browse and set the camera fix .tar there
unclick where it says F.reset time
click start
let it run
your done
I am not the best at explanations. But i would like to see you get this fixed
I attached a zip of odin and the camera fix .tar for simplicity
Click to expand...
Click to collapse
musclehead84 said:
Did it understand what tmspyder was telling you? If you did give him a thanks
Sent From My Evo Killer!
Click to expand...
Click to collapse
Thanks for the info Tmspyder. I just got off a 12 hour shift and am exhausted. I think I got the gist of it but am going to get some sleep first, read it again, and then reread what you posted. I just want to be sure of what I'm doing so I don't turn my phone into a "brick".

you wont brick. one of the great things about the epic and odin.. it is a 1/1,000,000 shot at real damage

Ok, I followed the directions, but the phone did not reboot automatically. It still says downloading... What should I do?

NVM, pulled the battery, put it back into download mode, repeated the process and it worked fine. No clue why it didn't work the first time.

[SOLVED] Rooting HDC Galaxy Note 2 Mega (MTK6577)

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.

Can't Encrypt - Tmo Galaxy S3

I've tried going through all the steps to encrypt my phone, however, it seems I get stuck on the black screen with green "lock" android / robot. It never goes any further than that screen (it never reboots as the directions state it would).
I've tried a couple different roms (Frosty JB, Wicked, Synergy) and none seem to let me complete the encryption process. I haven't tried going back to stock yet, since someone with an i9300 (international SG3) posted they had the same issue even when they went back to stock.
Has anyone had this issue? If so, how did you fix it? I've been looking all over the place for days and haven't found anything.
EDIT/ANSWER:
After doing a bit more digging, evidently, there's something called a PIT file that has to do with partitioning in our phones. You need to use Odin to install it. These are the directions I followed:
Pull out the battery and reinsert.
Press and Hold Volume Down + Home + Power Button until you see a warning!!
Press Volume Up button.
Your device will now enter the download mode.
Connect your phone to the PC.
Let it install some drivers.
Open Odin and click on PIT
Select that .PIT file you downloaded.
Check the box – Re-partition and Click Start.
After the successful attempt to re-partition the device, Flash with new firmware(which you downloaded from SamMobile)
Browse the downloaded firmware to the PDA section in Odin.
Don’t check the re-partition box this time.
Click Start and wait.
As soon as the process completes, your phone will boot. and it won’t stuck at welcome screen.
PIT files for US ONLY phones can be found here:
http://forum.xda-developers.com/showthread.php?t=1848267 - SEE THE FIRST POST
This finally worked for me, but use at your own risk.

Root mess up

Brand new note 4, went to odin CF.... everything started well, then the dog ran into the usb cable and ripped it out the pc.
Right now all the phone says is-
"firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I can get to download mode..nothing else.
tried to odin twrp... tried the full tar from stock roms...nothing takes... i could not find kies anywhere..found references they did away with it?
Any ideas? thanks

Open kies and Look in Kies menus.There must be an emergency recovery mode.Give it a try.
Sorry just realize that you don't have kies. .. but must find it on Samsung official software support.
Sent from my GT-N7105 using XDA Free mobile app

gyankamp1 said:
Open kies and Look in Kies menus.There must be an emergency recovery mode.Give it a try.
Sorry just realize that you don't have kies. .. but must find it on Samsung official software support.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
I found kies , now it wants model and serial number for the recovery... I looked under the battery, all inside the case and on the phone box... tried every number twice, none are the dang serial number! Even used a magnifying glass and typed in numbers all over the inside the darn thing..
best i found online is its in the menu on the phone(can't get in at all)
- sprints web site is down, guess I wait and see if I can find the ## in my account somewhere

[email protected]
Senior Dev.
I have the remedy. Work for me. Down load Philz Touch.
Pull the battery. Re insert. Set phone to download. May have
to pull battery a few times and reinsert. Phone went into shock.
PDA. Hit start on old Odin 3.09. Untick flash. Enjoy cup coffee.

ibcenu said:
Brand new note 4, went to odin CF.... everything started well, then the dog ran into the usb cable and ripped it out the pc.
Right now all the phone says is-
"firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I can get to download mode..nothing else.
tried to odin twrp... tried the full tar from stock roms...nothing takes... i could not find kies anywhere..found references they did away with it?
Any ideas? thanks
Click to expand...
Click to collapse
Uninstall all Kies and old Samsung Drivers. Reboot PC.
Go to www.samsung.com, under Owners & Support, select manuals & downloads, then in the search box after "Start by Entering Your Product's Model Number or Name"
Type in SM-N910P and select the color of the device you have, click manuals & downloads, the latest Samsung Driver as of this post should be 1.5.45.0. Or download the one you see.
Install the Samsung Driver.
Next download Odin v3.09, Grab it from >>> HERE <<<
Unzip onto an easily located spot. ( Desktop or on a Solid State Drive )
Kudos to rwilco12 for mirror.
NOTE: If you have this .tar SKIP THIS SENTENCE!
Download the Stock N910PVPU1ANK2 .tar files from >>> HERE <<<
and move it into the Odin folder
Kudos to viperboy for post and mirror.
Open Odin as an administrator ( accept UAC verification ) and don't touch anything within Odin as of yet.
Onward to your device, put it in download mode ( VOL DN+HOME+POWER, Press VOL UP on the dialogue to continue ) and plug in the device ( Recommended using rear USB Port @ 2.0 and default device cable ).
Let your PC finish the device installation ( A COM:## within a baby blue box will pop up at the top of Odin, wait for PC to finish installing device and after Odin Dialogue to say ADDED ).
Select AP and load in the .TAR file.
Double check what you've done thus far to make sure you didn't do anything wrong.
- Samsung 1.5.45.0 drivers installed
- Odin v3.09
- Stock NK2 .TAR file
- AP slot loaded with NK2 .TAR
Once you have everything setup, select START. If it starts with errors, try other Samsung device cables, other USB 2.0 ports ( 3.0 can be do-able, but with it being "2.0 compatible" can cause issues )
If it starts fine then it'll take 20 or more so minutes tops so do something in the time being. But if it can't be done via Odin, and it can't be done via Kies. Then send it in for repairs ( if download mode doesn't show KNOX WARRANTY VOID, then your in the clear to have it repaired )

Spark91 said:
Uninstall all Kies and old Samsung Drivers. Reboot PC.
Go to www.samsung.com, under Owners & Support, select manuals & downloads, then in the search box after "Start by Entering Your Product's Model Number or Name"
Type in SM-N910P and select the color of the device you have, click manuals & downloads, the latest Samsung Driver as of this post should be 1.5.45.0. Or download the one you see.
Install the Samsung Driver.
Next download Odin v3.09, Grab it from >>> HERE <<<
Unzip onto an easily located spot. ( Desktop or on a Solid State Drive )
Kudos to rwilco12 for mirror.
NOTE: If you have this .tar SKIP THIS SENTENCE!
Download the Stock N910PVPU1ANK2 .tar files from >>> HERE <<<
and move it into the Odin folder
Kudos to viperboy for post and mirror.
Open Odin as an administrator ( accept UAC verification ) and don't touch anything within Odin as of yet.
Onward to your device, put it in download mode ( VOL DN+HOME+POWER, Press VOL UP on the dialogue to continue ) and plug in the device ( Recommended using rear USB Port @ 2.0 and default device cable ).
Let your PC finish the device installation ( A COM:## within a baby blue box will pop up at the top of Odin, wait for PC to finish installing device and after Odin Dialogue to say ADDED ).
Select AP and load in the .TAR file.
Double check what you've done thus far to make sure you didn't do anything wrong.
- Samsung 1.5.45.0 drivers installed
- Odin v3.09
- Stock NK2 .TAR file
- AP slot loaded with NK2 .TAR
Once you have everything setup, select START. If it starts with errors, try other Samsung device cables, other USB 2.0 ports ( 3.0 can be do-able, but with it being "2.0 compatible" can cause issues )
If it starts fine then it'll take 20 or more so minutes tops so do something in the time being. But if it can't be done via Odin, and it can't be done via Kies. Then send it in for repairs ( if download mode doesn't show KNOX WARRANTY VOID, then your in the clear to have it repaired )
Click to expand...
Click to collapse
This should do it.

Thanks for the replys! I have to catch a flight today so I swung by the sprint store and they could not flash it, so they gave me a new one
i never realized how dependant I've become on the darn smart phone... even though it was overnight into the morning, I felt lost without it..lol

ibcenu said:
Thanks for the replys! I have to catch a flight today so I swung by the sprint store and they could not flash it, so they gave me a new one
i never realized how dependant I've become on the darn smart phone... even though it was overnight into the morning, I felt lost without it..lol
Click to expand...
Click to collapse
Hah, at least you got a new one. Next time let the dog have a go on a chew toy to keep em busy so you won't break things!