Database Info

[Q] KDZ App crash in Windows 7

Hey guys.
I've searched through the forum to see if this problem exists but I cant find it anywhere so hence my post. Apologies if I have missed it and it has been posted before.
So I wanted to update to firmware 2.2.2 as my Optimus One is giving me the SD card and sim card problems and its getting unbearable now.
I went to this thread (http://forum.xda-developers.com/showthread.php?t=106012) and followed all the instructions. As soon as I run the KDZ_FW_UPD it crashes instantly and goes no further.
I've followed the steps EXACTLY as they are stated but it still happens. Here is what the crash report says.
Problem Event Name: APPCRASH
Application Name: KDZ_FW_UPD.exe
Application Version: 1.0.4.4
Application Timestamp: 4ac2a689
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 89000000
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I am running V10A in South Africa.
Running Windows 7 Ultimate 64bit.
Please please help me otherwise I need to pay to take my phone in to get fixed some how.

Arktic88 said:
Hey guys.
I've searched through the forum to see if this problem exists but I cant find it anywhere so hence my post. Apologies if I have missed it and it has been posted before.
So I wanted to update to firmware 2.2.2 as my Optimus One is giving me the SD card and sim card problems and its getting unbearable now.
I went to this thread (http://forum.xda-developers.com/showthread.php?t=106012) and followed all the instructions. As soon as I run the KDZ_FW_UPD it crashes instantly and goes no further.
I've followed the steps EXACTLY as they are stated but it still happens. Here is what the crash report says.
Problem Event Name: APPCRASH
Application Name: KDZ_FW_UPD.exe
Application Version: 1.0.4.4
Application Timestamp: 4ac2a689
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 89000000
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I am running V10A in South Africa.
Running Windows 7 Ultimate 64bit.
Please please help me otherwise I need to pay to take my phone in to get fixed some how.
Click to expand...
Click to collapse
try this it works in windows 7 definately just read carefully http://forum.xda-developers.com/showthread.php?t=1038338

So Sorted it out.
Ran the installation etc on my oooold P4 PC with windows XP. Worked perfectly and now phone has been successfully updated to 2.2.2
MODS can please lock this thread or delete it.

me just got not responding for kdz updater
then just wait for it and continue to do things ~

Run it in Windows XP Compatibility mode
Arktic88 said:
Hey guys.
I've searched through the forum to see if this problem exists but I cant find it anywhere so hence my post. Apologies if I have missed it and it has been posted before.
So I wanted to update to firmware 2.2.2 as my Optimus One is giving me the SD card and sim card problems and its getting unbearable now.
As soon as I run the KDZ_FW_UPD it crashes instantly and goes no further.
Click to expand...
Click to collapse
I have this problem too. The solution is in properties choose "Run in compatibility mode" and "Windows XP". Now it works.

I changed windows to classic theme.....the aero was giving problem.

Does it run in windows xp sp 3 or any os listed in the properties=compability mode
vlastikw said:
I have this problem too. The solution is in properties choose "Run in compatibility mode" and "Windows XP". Now it works.
Click to expand...
Click to collapse
Im using windows 7 x64, it crashes and says update finished and i cannot hardreset it.

[Confirmation] Samsung N7100 clone (Chinese version) rooted now

Actually i don't want to make this new thread but since i'm new here and can't do a reply to the original thread so i make this. I just want to make a confirmation for Bin4ry who owned this awesome thread "Root MANY ANDROID!" that his tool work on my n7100 clone phone. And i want to make some recap for i have done.
my phone spec is:
processor: Mtk6515
RAM: 512 MB
Android version: Android 4.1.2
my computer spec is:
Brand: Asus ee-pc 1215B
Processor: AMD C-60
OS: Windows 7 32 bit
what i have done is:
1- enabling usb debugging mode and unknown sources function (i'm not installing any adb drivers or something sound like that since the first time)
2- i plug in to my laptop, and my device recognized as "sanstar" but strangely it's reacognized with a name "My HTC" on device manager
3- Run cmd and go to the folder where i put the tools.
4- Type runme.bat and choose "1" but somehow it gaves me some error
5- So i watched Bin4ry video for one more time :highfive:
6- And then, i back to step 3 and type "stuff\adb devices" and wait...... not for long it tells me that my device already connected... YAY :fingers-crossed:
7- I did step 4 again...wait for the process and see if restore function already pop up on my android phone and yep, it's showing something ahehehe
8- Click "restore my data" button....my phone restart after that and tadaaa....there's "superuser" showing up :victory:
So thank you so much, Bin4ry

Hello,
I also have the same phone but I had no luck with this method. After searching for a long time, I found SRSRoot which allowed me to Root my phone. It was a tough fight but I now have a rooted Note II clone...
acoet said:
Actually i don't want to make this new thread but since i'm new here and can't do a reply to the original thread so i make this. I just want to make a confirmation for Bin4ry who owned this awesome thread "Root MANY ANDROID!" that his tool work on my n7100 clone phone. And i want to make some recap for i have done.
my phone spec is:
processor: Mtk6515
RAM: 512 MB
Android version: Android 4.1.2
my computer spec is:
Brand: Asus ee-pc 1215B
Processor: AMD C-60
OS: Windows 7 32 bit
what i have done is:
1- enabling usb debugging mode and unknown sources function (i'm not installing any adb drivers or something sound like that since the first time)
2- i plug in to my laptop, and my device recognized as "sanstar" but strangely it's reacognized with a name "My HTC" on device manager
3- Run cmd and go to the folder where i put the tools.
4- Type runme.bat and choose "1" but somehow it gaves me some error
5- So i watched Bin4ry video for one more time :highfive:
6- And then, i back to step 3 and type "stuff\adb devices" and wait...... not for long it tells me that my device already connected... YAY :fingers-crossed:
7- I did step 4 again...wait for the process and see if restore function already pop up on my android phone and yep, it's showing something ahehehe
8- Click "restore my data" button....my phone restart after that and tadaaa....there's "superuser" showing up :victory:
So thank you so much, Bin4ry
Click to expand...
Click to collapse

need room plz
hi
i am need rom not2 i7100
plz help
model:i7100
fcc id:a3lgti7100
bb chip:mt6515
ms board:gt n7100
kernel ver:3.0.13([email protected])(gcc version 4.4.3(gcc))
android ver .4.1.2
sw ver . s005-ssd-hh-l002
custam build verno.0088130115
phone model:GT-N7100
Brand:samsung
cpu hardware:smdk4412
cpu model:armv7proces rev 2 (v71
cpu frequency:200.0~1400.0 MHz
screen resolation:1280.720
Gpu vendor: imaginatio technologies
gpu renderer: power vr sgx 531
gpu versionopen gl: open gl es-cm 1.1

custom rom
acoet said:
Actually i don't want to make this new thread but since i'm new here and can't do a reply to the original thread so i make this. I just want to make a confirmation for Bin4ry who owned this awesome thread "Root MANY ANDROID!" that his tool work on my n7100 clone phone. And i want to make some recap for i have done.
my phone spec is:
processor: Mtk6515
RAM: 512 MB
Android version: Android 4.1.2
my computer spec is:
Brand: Asus ee-pc 1215B
Processor: AMD C-60
OS: Windows 7 32 bit
what i have done is:
1- enabling usb debugging mode and unknown sources function (i'm not installing any adb drivers or something sound like that since the first time)
2- i plug in to my laptop, and my device recognized as "sanstar" but strangely it's reacognized with a name "My HTC" on device manager
3- Run cmd and go to the folder where i put the tools.
4- Type runme.bat and choose "1" but somehow it gaves me some error
5- So i watched Bin4ry video for one more time :highfive:
6- And then, i back to step 3 and type "stuff\adb devices" and wait...... not for long it tells me that my device already connected... YAY :fingers-crossed:
7- I did step 4 again...wait for the process and see if restore function already pop up on my android phone and yep, it's showing something ahehehe
8- Click "restore my data" button....my phone restart after that and tadaaa....there's "superuser" showing up :victory:
So thank you so much, Bin4ry
Click to expand...
Click to collapse
do have any custom rom for this phone.?

Intel Android Devices Root / Temp Recovery Session

Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
Tethered Temporary CWM / TWRP Recovery Session :
Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .
WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
Current Version : IntelAndroid-FBRL-07-24-2015.7z
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (
APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE
XDA:DevDB Information
Intel Android FBRL, Tool/Utility for the Android General
Contributors
social-design-concepts
Version Information
Status: Stable
Created 2015-07-28
Last Updated 2015-07-28

Supported Devices List / Trigger
Supported Devices List / Trigger
Acer :
B1-730 T2
B1-730HD T2
A1-830
A1-840FHD T3
A1-840 (HD) T3
Asus :
ME170C T2 & T3
ME176C T2 & T3
Dell :
Venue 7 3730 / Venue 8 3830 All Triggers Should Work
Venue 7 3740 / Venue 8 3840 T3
Venue 7 3741 / T3
Venue 8 7840 T3
Iview :
i700 T2 & T3
Kurio :
Xtreme 7 Only had a chance to test trigger T3
Odys :
intellitab 7
Nabi:
Dreamtab model IN08A trigger T3 reported working
Prestigio :
MultiPad Thunder 7.0i
Tesla :
L7 Tablet T3
Tesco :
Op3n Dott 8 T2 & T3
Toshibia :
Excite 7 T3

Links to devices specific threads / forums
Links to devices specific threads / forums
If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .

The Concept / Source Code
The Concept / Source Code

Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates

Generic / Tips for Unbricking
Generic / Tips for Unbricking

Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!

GeeKerGurL said:
Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.
Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
Click to expand...
Click to collapse
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?

GeeKerGurL said:
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
Click to expand...
Click to collapse
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Okie dokie. Ill be here.

social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Woot!!!YA! no need, I got it back all by myself just had to boot with vol down and go back through the process and everything copied fine and worked this time! :good: thanks a ton for offering to help me though buddy!
BTW trigger 3 works for the 3830 V8 no modem
WOOOHOOOOHOOOOWOOOO! root check cleared, I am SOO happy to finally have root on this thing. Besides my minor hiccup for whatever reason this method was pie too! YAHOO. I went from about to cry to jumping around happy like a crazy person haha.

recovery fstab
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.

whgarner said:
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
Click to expand...
Click to collapse
recovery.fstab may or may not need to be edited for some devices especially if the device doesn't use by label partitioning. What device do you have?
Sent from my XT907 using XDA Free mobile app

asus aa3-600
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.

Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?

tomtom1265 said:
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
Click to expand...
Click to collapse
I'm going to post the source after I finish getting the thread put together I just wanted to get it up yesterday.
As for doing it through shell scripts the reason its binary is because if /system is mounted or any prebuilt binary has a dependency on a shared library it makes it extremely difficult some times impossible to stop services and unmount /system and such.
But I hope to have everything finish by the end of the day.
Sent from my XT907 using XDA Free mobile app

whgarner said:
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Click to expand...
Click to collapse
You use Linux or windows? If Linux, you may need to use my fastboot binary, anyway if using Linux while in fastboot mode use terminal type lsusb.
Do you see your device listed?
Sent from my T1 using XDA Free mobile app

Root!
Thank you for this!
I successfully rooted my V8 3830 KK4.4 V1.33 no modem with T3 - in about 4 mins. tops.
FYI:
I connected and launched the launcher from the IntellAndroid-FBRL folder. Typed ACCEPT and got the green screen. Chose T3. The tablet rebooted into fastboot and files where loaded, But then fastboot turned red and said "device unauthorized" when CWM popped onto my tablet. (maybe it's suppose to do that, DK) and yes, US debugging was on, I flashed the SU zip, rebooted, all is well. SU updated and working fine. I was able to remove all the crapwear. :laugh:
thank you SDC!

Quick question - Do any of the intel devices have unlocked bootloader?? Thought I read somewhere somebody was able to install a factory 4.3 or 4.2 on a Dell venue and the bootloader unlocked?

[Q] Trying to root SM-G920F using Linux

Hi! I'm exasperated so I turn to the experts: you! I hope this is right (or should I have continued this megathread?)
TLDR: Want to root international S6 running branded 5.1.1; but using Linux and having trouble getting things to work. Have tried lots already; details below.
1. bootloader status = I think it's unlocked but not sure how to determine this.
2. Rom name with complete baseband/date/version = "Austrian 3/Hutchinson" branded, PDA Version G920FXXU3COI9, CSC Version G920FDRE3COJ1, PHONE Version G920FXXU3QOJ1.
3. Kernel name = uh, stock Samsung 5.1.1?
4. Mods = none
5. Custom Rom = none
6. Guides =
7. Root status = unrooted.
8. Your exact problem = Want to root, having trouble doing so.
9. Any method you tried that failed = see details below.
10.Any other detail you think would be necessary = my phone's ODIN screen lists this information:
PRODUCT NAME: SM-G920F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I've tried rooting my S6 using Linux, using a virtual WInXP hosted on Linux, and using an old real WinXP computer. None of the methods worked, but let me describe what I've tried on each -- I'd be happy if I can get either one of the methods across the finish line!
1) Virtual WinXP computer on Linux host
created a brand-new virtual WinXP installation to make sure nothing would interfere.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
In the settings for the virtual machine, set up rules to ensure all Samsung USB devices (USB vendor ID 04e8, any product ID) would be routed directly to the virtual machine.
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Neither Windows nor Odin sees the phone - neither in its normal operating mode nor in its "Odin" download mode.
Give up.
2) Physical Ubuntu computer, using JOdin
Installed Heimdall (latest version = 1.4.0-0).
Downloaded JOdin (latest version = v1035).
Installed Oracle Java 8 (8u67).
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
JOdin says: "We could not obtain the pit file. We tried, but it didn't work." It seems that this is not really JOdin's fault but rather Heimdall (which JOdin relies on) because running just Heimdall from the CLI gives the same problem, as seen from this log (verbose version).
I dare not download a "random" PIT file from the Internet; this would satisfy JOdin but the risk of choosing the wrong one is too high. Other sites also mention ways to use the adb shell but ironically these require root - so I can't use them.
3) Physical WinXP computer
I did all of the above Linux trickery because I don't own a computer with Windows. By sheer chance, a friend came by with an old WinXP machine that I could commandeer for this purpose.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Odin sees my phone in download mode (first success!) and I can do the steps to start the root.
Odin works it way through the file and goes to "NAND write start" and then "Complete(Write) operation failed". I've tried this using the CF-Auto-Root and also separately using the unibase kernel for 5.1.1, with identical results.
I feel that I'm so close and yet success is not yet in reach. What more can I do? Thank you for your help and kind assistance!

torbengb said:
Hi! I'm exasperated so I turn to the experts: you! I hope this is right (or should I have continued this megathread?)
TLDR: Want to root international S6 running branded 5.1.1; but using Linux and having trouble getting things to work. Have tried lots already; details below.
1. bootloader status = I think it's unlocked but not sure how to determine this.
2. Rom name with complete baseband/date/version = "Austrian 3/Hutchinson" branded, PDA Version G920FXXU3COI9, CSC Version G920FDRE3COJ1, PHONE Version G920FXXU3QOJ1.
3. Kernel name = uh, stock Samsung 5.1.1?
4. Mods = none
5. Custom Rom = none
6. Guides =
7. Root status = unrooted.
8. Your exact problem = Want to root, having trouble doing so.
9. Any method you tried that failed = see details below.
10.Any other detail you think would be necessary = my phone's ODIN screen lists this information:
PRODUCT NAME: SM-G920F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I've tried rooting my S6 using Linux, using a virtual WInXP hosted on Linux, and using an old real WinXP computer. None of the methods worked, but let me describe what I've tried on each -- I'd be happy if I can get either one of the methods across the finish line!
1) Virtual WinXP computer on Linux host
created a brand-new virtual WinXP installation to make sure nothing would interfere.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
In the settings for the virtual machine, set up rules to ensure all Samsung USB devices (USB vendor ID 04e8, any product ID) would be routed directly to the virtual machine.
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Neither Windows nor Odin sees the phone - neither in its normal operating mode nor in its "Odin" download mode.
Give up.
2) Physical Ubuntu computer, using JOdin
Installed Heimdall (latest version = 1.4.0-0).
Downloaded JOdin (latest version = v1035).
Installed Oracle Java 8 (8u67).
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
JOdin says: "We could not obtain the pit file. We tried, but it didn't work." It seems that this is not really JOdin's fault but rather Heimdall (which JOdin relies on) because running just Heimdall from the CLI gives the same problem, as seen from this log (verbose version).
I dare not download a "random" PIT file from the Internet; this would satisfy JOdin but the risk of choosing the wrong one is too high. Other sites also mention ways to use the adb shell but ironically these require root - so I can't use them.
3) Physical WinXP computer
I did all of the above Linux trickery because I don't own a computer with Windows. By sheer chance, a friend came by with an old WinXP machine that I could commandeer for this purpose.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Odin sees my phone in download mode (first success!) and I can do the steps to start the root.
Odin works it way through the file and goes to "NAND write start" and then "Complete(Write) operation failed". I've tried this using the CF-Auto-Root and also separately using the unibase kernel for 5.1.1, with identical results.
I feel that I'm so close and yet success is not yet in reach. What more can I do? Thank you for your help and kind assistance!
Click to expand...
Click to collapse
I think may need to find a way to run the newest odin thats the only thing i can see thats rong in your attempts idk im not a big linux guy. U might need to get ahold of a win8 pc

WinXP SP2 = solved!
I solved the problem on Windows and finally got that big friendly PASS! :laugh:
As it turns out, there were two things blocking my success:
Odin version not compatible
Windows XP needed Service Pack 2
Initially I tried using the newest version of Odin, of course. But version 3.10.7 does not work, says "is not a valid Win32 application" so I went back to earlier versions until I found one that could run. The second-newest Odin version 3.10.6 does not work, says "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll." Finally, version 3.06 could run, but as I now know, that version is so old that it does not support the Samsung S6! Of course it doesn't say so, and that's why I was stumbling in the dark for a good while.
So I need a newer version, but what can I do to make the newest one work? I finally discover that v3.10.7 (despite being only a minor release) has this in its unofficial release notes: "Removed support for Windows XP or earlier"! Okay that was hard to find!
So I need the previous version, v3.10.6. However, that one complains about kernel32.dll. Where can I find a newer version of that DLL? It dawns on me that my brand-new WinXP installation doesn't have any of the service packs yet, so I install WinXP SP2 and, lo and behold, version 3.10.6 can finally run!
But all of this was on my virtual machine, and it still couldn't detect when I plugged in the phone on the host computer. So I took a look at the WinXP machine that luckily was passing through my home just now. It's in German, and only runs WinXP SP1. I managed to find and install SP2 in German, and finally I had Odin v3.10.6 running on that machine - and it actually detected my phone!!
From here on, it was trivial to complete the rooting process. Once the software gets to run as intended, it's a beautifully simple thing. My phone is now rooted, and I can finally have Llama put it into airplane mode when I go to sleep. SUCCESS!
(But I still don't know why it doesn't work on Linux.)

Can't root my phone after flashing via SP Flash Tool Then many problem

Hello Guys!
Seems a huge discussion about android platform but i cannot see my related issue. i am presenting a clear note about all of my issue.
My phone details is
MTK 6737
Name: Symphony
Model: R100
RAM: 3GB
First i have flash my phone using SP Flash tools (format all+download). after that IMEI number not showing and not found anywhere. i have checked huge tutorial, youtube video, forum thread etc a lot but not correct solution. everybody says i must have ROOT ACCESS in order to adjust my IMEI number again.
I got two problem
1. Nvram error (wifi issue)
2. Invalid imei issue
I spend over 14 hours like a whole days with computer & internet to find correct solution. i have downloaded huge driver like ADB driver, CDC driver, MTK USB driver, SN Writer tools AND many more.
Maximum people says "MTK Engineer Mode" then i had opened that, unfortunately, CDC information not available in menu list. more than 10 root app used to get ROOT access but all are failed. i have followed more than 50 tutorial to modify scatter.txt file with navram.bin etc but failed.
Now, i am looking for help from expertise who know about this matter.
Thank you very much.