Database Info

[FROYO-ODIN] Leak USCC Mesmerize Froyo EA11 Stock + Root

So here's what Samsung has been sitting on for the last few months..
{
"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"
}
I present to you an 'official' build including the kernel, radio, and full-blown froyo tastiness, for the USCC Samsung Mesmerize. Pre-rooted for your convenience, just download and flash with the latest version of ODIN. These are stock images plus root so your phone will function as if you just turned it on for the first time, albeit with a finger that magically instills root powers into any device you touch..
README
Step 0.5: I recommend disabling the Voodoo Lagfix before doing any of this. You need your sdcard partitioned normally. Let me repeat: Disable the Voodoo Lagfix if you are using a Voodoo kernel prior to flashing the Odin files.
Step 1
Download ODIN here: Odin v1.3
Step 2
Install the Samsung USB drivers: 64bit | 32bit
Step 3
WARNING: These files are for the USCC Samsung Mesmerize. Do NOT flash these to another device.
Download the ODIN package: USCC Froyo [ODIN]
Step 4
Unzip the ODIN package and you will find two files. One ends in tar.md5 This is the ODIN package that you will flash to your device. The other file ends in .pit. This file is a configuration file of sorts for your device. It is not needed unless you have trouble.
Step 5
Backup the data on your device. You are going to lose it.
Step 5.5
Backup the data on your device. It is not coming back.
Step 6
Open up ODIN. Load the tar.md5 file into the PDA section.
Step 7
Put your phone into download mode. The easiest way to do this is to issue the "reboot download" command from adb. If you don't have adb installed, simply download the attached adb.zip. Extract the files to a new folder and open up a command prompt in that folder by holding down shift then right-clicking inside the folder window. There will be a menu entry "Open command window here". Select it. Then, type "adb reboot download" (no quotes) and press enter. If this fails you need to turn on USB debugging on your device and try again. Settings>Applications>Development:Enable USB Debugging
For more information on ADB I strongly recommend reading the "ADB Workshop" by Adrynalyne and Captainkrtek.
Alternatively, you can power your phone off. Hold down the "Volume Down" button and plug in the USB cable (make sure the other end is plugged into the computer first).
If all is successful, you should see a yellow triangle around a hard-working android and the words 'Downloading... Do not turn off target' (also in yellow).
*Step 8*
Once your phone is in download mode it should pop up in ODIN. Once ODIN has found the device, make sure you have the tar.md5 file loaded in PDA from step 6, and press START! ODIN will begin flashing your device. After a few minutes it should reboot into recovery, flash some text, and reboot again into Froyo! If all goes well, the white box in ODIN will turn green (=
Troubleshooting
Lag or low quadrant score: re-flash using the .pit file
Odin doesn't recognize your phone: install the Samsung USB drivers and reboot
Odin says checksum failed: re-download package and try again
Looking Forward
That's all! You will need to setup your phone again like you did when you first got it. While annoying, it's worth it! Once you have everything setup you're good to go. Check back periodically for Froyo ROMs and customizations. There are already some on the way and many more coming since Froyo has been out for awhile -_-
Links:
<--USCC Froyo EA11 ODIN Stock + Root
http://www.megaupload.com/?d=WG39PL2H <--USCC Froyo EA11 ODIN Stock + Root Mirror phidelt82
http://www.megaupload.com/?d=XRDDYL75 <--USCC Froyo EA11 ODIN Stock + Root + Recovery Mirror phidelt82
http://rom2.galaxysense.com/mesmerize/USCC_Froyo_Root_Recovery_EA11.zip <--USCC Froyo EA11 ODIN Stock + Root + Recovery
(I will add more versions as they become available..)
Credits:
<phidelt82 | donate> hosting, help, and testing (this guy will flash anything I throw at him)
<CaptainKrtek | donate> HUGE thanks to CaptainKretk for offering to host these on his server. However, he does not have magical bandwidth that doesn't cost anything.. so if you appreciate his bandwidth, please help him out. I have.
<jt11134 | donate> Thank jt for the <2e> recovery that's in the integrated package rom + recovery package. Plus, he's the master behind much of the Fascinate AOSP progress.
more to come
Finally, I put some time into fixing this up for you all. If you appreciate my time, buy me a beer or two (=
<dcow | donate>

Thank you!!!! I will test when I get home from work today.

Is it safe to use wireless tethering some one said it wasn't on the fascinate

johnboyjr said:
Is it safe to use wireless tethering some one said it wasn't on the fascinate
Click to expand...
Click to collapse
Not sure. It's probably just as unsafe as using wireless tethering without a contract anyway. I'll look into it though.

Thanks dude, you and Keith are awesome. I will try these ASAP.
Sent from my SCH-I500 using Tapatalk

So with this new froyo ROM (I'm so excited!) There's currently no voodoo kernel that will work with this on the mesmerize, right? I don't care, I'm flashing it as soon as I can, Im just curious.
Sent from my SCH-I500 using XDA App

davidbruington said:
So with this new froyo ROM (I'm so excited!) There's currently no voodoo kernel that will work with this on the mesmerize, right? I don't care, I'm flashing it as soon as I can, Im just curious.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
No voodoo kernel yet. That will come in time. Hopefully I'll get a ROM built today. Then we will have themes coming.

as soon as i see voodoo for this...im on it like white on rice!!!

BakedTator said:
as soon as i see voodoo for this...im on it like white on rice!!!
Click to expand...
Click to collapse
It works 100% fine without voodoo.. you're missing out. And it's not like you can't add voodoo later once we get it ready (=

rooting
are we able to root froyo yet? can we just load up z4mod?

dfgas said:
are we able to root froyo yet? can we just load up z4mod?
Click to expand...
Click to collapse
ReREAD the First POST

It comes pre-rooted Thank the sweet devs for saving you an extra headache

elijahblake said:
ReREAD the First POST
Click to expand...
Click to collapse
completely sorry about that......

dfgas said:
are we able to root froyo yet? can we just load up z4mod?
Click to expand...
Click to collapse
It's pre-rooted.
YAY!

im flashing now you can use one click lag fix for the time being it will help but i wouldnt use full time as it messes with memory

You just made my day!
Sent from my SCH-I500 using XDA App

voodoo kernel
there is a test voodoo kernel out that came with the alpha build of froyo does any one know if this will work ? im going to try it out ill report back

I have voodoo kernel will this work.just asking as this is new too me.thanks

there is a test voodoo kernel out that came with the alpha build of froyo does any one know if this will work ? im going to try it out ill report back
Click to expand...
Click to collapse
Please read the first post (= This comes with the 2.6.32.9 kernel (the 2.2 one we've been trying to get our hands on forever) No hacked up alpha kernel needed..

phidelt82 said:
No voodoo kernel yet. That will come in time. Hopefully I'll get a ROM built today. Then we will have themes coming.
Click to expand...
Click to collapse
You are awesome man, thank you so much for all your hard work and your time. I'm flashing this as soon as I get my lunch break!
Sent from my SCH-I500 using XDA App

[ROOT] [KERNEL] [RECOVERY] - Root / Voodoo Lagfix / CWM Recovery

Hi all
Whipped this up for a friend. Thought we'd be nice and share
These packages will work on any current sw version for the Charge.
Please find below kernel and recovery packages hacked for the following:
permanent adb root
installs Superuser and su binary automatically on boot
includes Voodoo ext4 lagfix - CREDIT TO SUPERCURIO! http://project-voodoo.org/lagfix
lowmemorykiller tweaks
sdcard readahead cache speed tweak
If you are using Odin to flash, simply flash the below package. If you are using Heimdall, remove the zImage file from the below package and flash it.
After flashing the first time, you will hear a voice from the phone telling you what is occurring. The conversion to ext4 will take a few minutes. BE PATIENT. Once it boots, Superuser should be installed, and your phone's filesystem will be converted from rfs to ext4. To disable Voodoo lagfix and convert back to rfs, simply create a file on your sdcard inside the Voodoo folder, named "disable-lagfix". Then reboot your phone and listen for the voices again. This will also take a few minutes.
Please familiarize yourself with using Odin or Heimdall and have backup images on-hand if you are going to use this kernel. If you screw up, you will need them
I DO NOT have a Charge, these files have been tested by other users. As always I assume absolutely NO liability for anything that happens if you use this kernel. Phone blows up? It's on you to fix it
If you find this software helpful please click the "Thanks" or the "Donate" button. Either is fine by me. If you would like to investigate the changes that were made, please feel free to find them here, and here.
Enjoy.
EDIT
Uploaded 2nd version
EDIT
Uploaded 3rd version
changed the install scripts around
should copy files more efficiently
fix file ownership and permissions
UNTESTED!
EDIT
Uploaded 4th version
Confirmed root from independent user!
rewrote install process to preserve file path and permissions
will look into the bootanimation graphics issue
http://dl.dropbox.com/u/14764513/VoodooChargeKernel4.tar.md5
EDIT
Uploaded additional recovery file
Flashes custom version of ClockworkMod recovery 3.x
Recovery includes Voodoo specific options for enabling/disabling Voodoo lagfix
Flash with Odin or Heimdall just like the kernel files
HAS BEEN LIGHTLY TESTED! USE CAUTION AND HAVE A BACKUP!
if you do not have root:
* check adb shell and see if you get a '#' prompt. If so, you *have* root on adb, and you may install whatever you want in /system
* check to see if Superuser app is installed
* check to see if /system/xbin/su exists on your phone.
If you have problems, please post the results of those checks. Thanks.

LLGW. Headed to bed now but first thing in the morning, I wondering what I'm doing

Thanks jt!!!! Can't wait to flash this once my charge comes in the mail.
Sent from my SCH-I500 using XDA App

Ok, somebody use this to system dump ED2.
And, uh, is there matching Voodoo clockwork?

s44 said:
Ok, somebody use this to system dump ED2.
Click to expand...
Click to collapse
please
And, uh, is there matching Voodoo clockwork?
Click to expand...
Click to collapse
probably not

What verison of odin should I use? I just flashed this and it failed.

using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1

The kernel flash was successful, and the filesystem conversion took about 8 minutes to run. However, I was not rooted when the phone booted back up. Here is what I did, let me know if I missed a step:
Start on rooted ED1
Accept ED2 OTA
Lose Root
Flash new kernel using ODIN
After ~10 minutes, phone boots successfully, but I do not have root.

asenduk said:
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
Click to expand...
Click to collapse
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.

Where's my wifi? Anyone else facing an error when attempting to start wifi?

Yeah it looks like it killed wifi. I also am not rooted.

So if I flash back to rooted ED1 will it wipe my data?

azhockey said:
So if I flash back to rooted ED1 will it wipe my data?
Click to expand...
Click to collapse
I just reversed the filesystem changes and then flashed back to ED1. My data appears to be intact.

moondrius said:
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Click to expand...
Click to collapse
had to rename the file to .tar.md5 now its working..

asenduk said:
had to rename the file to .tar.md5 now its working..
Click to expand...
Click to collapse
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?

Updated OP with a new version. Anyone who has flashed the original version, please check adb shell and see if you get a '#' prompt. If you do, then you're technically rooted

NotATreoFan said:
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Click to expand...
Click to collapse
Superuser was installed but root was lost... Trying the updated version... On a positive note Quadrant is great! 1400-1550 avg
EDIT: wifi fixed with v2 but still no root.. will try from scratch and report back
{
"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"
}

Everything has worked for me. Thank you.
Sent from my ADR6400L using XDA Premium App

yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin

devanmc said:
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
Click to expand...
Click to collapse
Click PDA and select the file then just hit start

[TUT]Extract kernel "zimage" From boot.img and Convert to .tar and Flash using Odin

[TUT]Extract kernel "zimage" From boot.img and Convert to .tar and Flash using Odin
[Extremely Noob GUIDE]Since there is no explained and easy Guide to Extract Kernel [zimage] and Ramdisk [Ramdisk] from Boot.img, Then Convert it to zimage.tar and Flash it using Odin
Well here it is step by step:
Note: This Method is used to Extract Kernels form Stock Rom's Boot.img
First you need to install Python, which is round about 17MBs software freely available on python website.
Step 1:Download the attached Python script named "split_boot_img" from attachments down Below, Extract it and copy to the folder created in Step 2.
Step 2:Create a folder with any name you like. I recommend "boot.img extraction".
Step 3: Copy the boot.img, you want to extract, to the folder you created in Step 2.
Step 4: Run the script named "split_boot_img"by double-clicking and see the magic.
Congratulations!!! Here you go. the "zimage" and "ramdisk" files are extracted.
Now the Conversion Part:
Step 1: Download this IZARC software and install it from Here:http://www.izarc.org/download.html
Step 2: Open the folder created in First-Step 2.
Step 3: Right Click the ziamge File Extracted from boot.img. as in Image 1 in attachments.
Step 4: Select add to archive file from IzArc right click options as in Image 1 in attachments.
Step 5: Now scroll the Archiving type to ".tar" as in Image 2 in attachments.
Step 6: Click the Add button as in Image 3 in attachments.
Last Step: Now flash the "zimage" file created in Step 6 Using Odin.
View attachment split_boot_img.zip
Image 1:
{
"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"
}
Image 2:
Image 3:

Not Working
extraction doesn't work for me :/

shivasharmaarya said:
extraction doesn't work for me :/
Click to expand...
Click to collapse
Did you follow till last step. What message did you get?

yes
exceptionalkhan said:
Did you follow till last step. What message did you get?
Click to expand...
Click to collapse
Python script of yours is not working.Its giving error which flashes for microsecond and i am unable to see it

shivasharmaarya said:
Python script of yours is not working.Its giving error which flashes for microsecond and i am unable to see it
Click to expand...
Click to collapse
Maybe he should have put in that you need to use Python 2.7.9 not 3.x ... Had the same problem.
All steps worked after, but didn't flash it yet, I'll do it today or tomorrow.
Also you should mention IZArc is full of crapware, it open one install and even if I chose to not install stuff, it installed iStart and Search Enginer extensions to my browsers. After, surprise, another install showed up to actually install IZArc ... not I need to de-crap my system

dotuletz said:
Maybe he should have put in that you need to use Python 2.7.9 not 3.x ... Had the same problem.
All steps worked after, but didn't flash it yet, I'll do it today or tomorrow.
Also you should mention IZArc is full of crapware, it open one install and even if I chose to not install stuff, it installed iStart and Search Enginer extensions to my browsers. After, surprise, another install showed up to actually install IZArc ... not I need to de-crap my system
Click to expand...
Click to collapse
Did the kernel.img actually work for you? I tried this same process as well. It took me 4 hours to clean all the maleware from my laptop. I mad the .Tar file and tried to flash it. it failed completely. I think this OP needs to be removed. More than likely the OP is getting paid for all the downloads he is tricking people into.

Chillyz12 said:
Did the kernel.img actually work for you? I tried this same process as well. It took me 4 hours to clean all the maleware from my laptop. I mad the .Tar file and tried to flash it. it failed completely. I think this OP needs to be removed. More than likely the OP is getting paid for all the downloads he is tricking people into.
Click to expand...
Click to collapse
No, it failed also. Yes, it should be removed.
Ended up using http://forum.xda-developers.com/showthread.php?t=2446269 but for a strage reason Odin would not like it when I moved the .tar archive from a folder to an other from that method (I keep my pc organized), had to create the tar, flash it from that folder, then... deleted it because after I couldn't use it anymore.

dotuletz said:
No, it failed also. Yes, it should be removed.
Ended up using http://forum.xda-developers.com/showthread.php?t=2446269 but for a strage reason Odin would not like it when I moved the .tar archive from a folder to an other from that method (I keep my pc organized), had to create the tar, flash it from that folder, then... deleted it because after I couldn't use it anymore.
Click to expand...
Click to collapse
It won't trip knox, right?

Joker87 said:
It won't trip knox, right?
Click to expand...
Click to collapse
Flashing any modified boot / kernel / recovery trips Knox, doesn't matter what method you use. Sometimes even stock trips Knox as some users said.
What i did was take a stock rom from SamMobile that was 'hackable' through TowelRoot, extracted the kernel with WinRar, made the kernel flashable in Odin using that tool, flashed it via Odin, rooted device with TR, then used same steps to download,extract,make kernel bootable to restore my original kernel. Knox stayed 0x0 on i9195.
You can try reading about Heimdall. Supose you can flash without Odin and without converting. It would make your life easier, but for me it didn't work (didn't start on Win 64bit, i think i needed another MS visual c++ , a dependency of Heimdall).
ps.: the tool to create flashable archives would't work for me just by double-clicking, so I had to open an command prompt - CMD with admin rights, go to the directory where i had the tool and type ImgToTar.MD5.bat . Just put everything in C:\tool including recovery.img / boot.img or kernel.img then go start-> type in search box CMD -> right-click on the result and Run as admin -> in the black box type the next text followed by Enter key:
cd /
cd tool
ImgToTar.MD5.bat

I hope it works, i need it for the same reason of you, flashing an older kernel to root with towelroot keeping knox 0x0 at the end of this process

[Q] Rooting Help + Help + Help

please download Root to Samsung Galaxy Note Pro 12 3g sm-p901
1 ..
{
"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"
}
2..
3..
Means no one will have the same hardware and the Root .. Please solution of the problem

alhgan2014 said:
I hope I Want Root attention to two Ergonomics I have tried before and failed periods transferred
Waza possible, please download Root to fit his two Samsung Galaxy Note Pro 12 3g sm-p901
Click to expand...
Click to collapse
um...

Thanks

Did you try towelroot?

Towelroot is only for Qualcomm devices, the P901 is an Exynos device.
Read this: http://androidxda.com/root-samsung-galaxy-note-pro-12-2-sm-p901
And the original autoroot file is in this list: http://autoroot.chainfire.eu/#odin

dodo99x said:
Towelroot is only for Qualcomm devices, the P901 is an Exynos device.
Read this: http://androidxda.com/root-samsung-galaxy-note-pro-12-2-sm-p901
And the original autoroot file is in this list: http://autoroot.chainfire.eu/#odin
Click to expand...
Click to collapse
Yeah I think the only option is cf autoroot and tripping knox
Sent from my Fired-up Kitty

Ok, now that he's fixed his comment so it makes a tiny bit of sense. I had this problem with the p900 as well. This was how I fixed the hang on cache issue very quickly.
Get 7zip.
1. Open the zip file you got for cf-autoroot with 7zip. Extract the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file.
2. Remove .md5 extension and rename the file CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar
3. Open this file with 7zip, extract recovery.img from it. Set this aside, you'll need it in a few more steps.
3. Download Caboomi's Recovery img2tar odin maker tool from here http://forum.xda-developers.com/showthread.php?t=2281287
4. Unzip the tool into a folder. Delete the recovery.tar.md5 it comes with. You will also see a Runme.bat file.
5. Edit the bat file with something like Notepad ++. The second line will be
Code:
bin\tar -H ustar -c recovery.img > recovery.tar
Change this to
Code:
bin\tar -cf recovery.tar recovery.img
Save the file.
6.Remember the recovery.img file you took from the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar in step #3? Throw that file into the same folder where the Runme.bat file is located.
7. Run the .bat file. It will produce a new recovery.tar.md5
8. Flash this new recovery file in Odin. HAVE AUTOREBOOT TURNED OFF.
9. Flash the original CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file after that.
10. Hopefully success?

Got everything but the result is still the same problem
Gatsrom said:
Ok, now that he's fixed his comment so it makes a tiny bit of sense. I had this problem with the p900 as well. This was how I fixed the hang on cache issue very quickly.
Get 7zip.
1. Open the zip file you got for cf-autoroot with 7zip. Extract the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file.
2. Remove .md5 extension and rename the file CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar
3. Open this file with 7zip, extract recovery.img from it. Set this aside, you'll need it in a few more steps.
3. Download Caboomi's Recovery img2tar odin maker tool from here http://forum.xda-developers.com/showthread.php?t=2281287
4. Unzip the tool into a folder. Delete the recovery.tar.md5 it comes with. You will also see a Runme.bat file.
5. Edit the bat file with something like Notepad ++. The second line will be
Code:
bin\tar -H ustar -c recovery.img > recovery.tar
Change this to
Code:
bin\tar -cf recovery.tar recovery.img
Save the file.
6.Remember the recovery.img file you took from the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar in step #3? Throw that file into the same folder where the Runme.bat file is located.
7. Run the .bat file. It will produce a new recovery.tar.md5
8. Flash this new recovery file in Odin. HAVE AUTOREBOOT TURNED OFF.
9. Flash the original CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file after that.
10. Hopefully success?
Click to expand...
Click to collapse
Got everything but the result is still the same problem

alhgan2014 said:
Got everything but the result is still the same problem
Click to expand...
Click to collapse
Here I made one for you, try this one in Odin click me I didn't zip it since it's just the tar.md5 file not all the extra odin stuff. Don't modify this file's extensions, put it straight into odin.
After downloading, you should check the md5 matches: 44d09a57009cfdbb322f0c9ca13bd4fe
Let me know if it works. Otherwise we have to look for another problem cause/solution.

Please solution of the problem
Means no one will have the same hardware and the Root ؟
Please solution of the problem

Pleaseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Salvation is no hope for me is not reasonable Root site developers not to be in the Real Root device
Samsung Galaxy Note Pro 12 3g sm-p901

Thank god! Solution of the problem
Thank god! Solution of the problem by means of friend gatsrom

alhgan2014 said:
Salvation is no hope for me is not reasonable Root site developers not to be in the Real Root device
Samsung Galaxy Note Pro 12 3g sm-p901
Click to expand...
Click to collapse
From the message I got from you this morning, we seem to have got it going. Device is still rooted and okay right?

Gatsrom said:
Here I made one for you, try this one in Odin click me I didn't zip it since it's just the tar.md5 file not all the extra odin stuff. Don't modify this file's extensions, put it straight into odin.
After downloading, you should check the md5 matches: 44d09a57009cfdbb322f0c9ca13bd4fe
Let me know if it works. Otherwise we have to look for another problem cause/solution.
Click to expand...
Click to collapse
can u please re-upload the file, i got the same exact problem. ill be just flashing the file using odin right?
thx in advance

Please re up the file
Gatsrom said:
From the message I got from you this morning, we seem to have got it going. Device is still rooted and okay right?
Click to expand...
Click to collapse
Hi Gatsrom,
I have the same problem with my P901, tried already the steps you mentioned but didn´t work.
Can you please re up the file so I can try this.
Thanks

posting error

21667 said:
can u please re-upload the file, i got the same exact problem. ill be just flashing the file using odin right?
thx in advance
Click to expand...
Click to collapse
HNevenEG said:
Hi Gatsrom,
I have the same problem with my P901, tried already the steps you mentioned but didn´t work.
Can you please re up the file so I can try this.
Thanks
Click to expand...
Click to collapse
Let me go through the emails and files, see if I still have it.

Please help me to solve th eProblem
alhgan2014 said:
Thank god! Solution of the problem by means of friend gatsrom
Click to expand...
Click to collapse
Dear alhgan,
do you still have the files you got from Gatsrom?
I have the same problem then you had.
Thanks!

Finally rooted my P901
After hundred times stucked at cache.img I found the reason and got my p901 finally rooted!
Two things which I made wrong, so remember the following two points:
1. You have to switch on USB debugging in “development options” under Settings on your P901!
2. You have to start Odin as Admin!
Go on with the normal flashing procedure:
Start P901 in flashing mode
Start Odin as Admin (use only the Odin version which comes in the package from CF!)
Load tar.md5 File in AP
Connect the P901 to PC
Start
That´s all!

please rebuild the file to root
Gatsrom said:
Let me go through the emails and files, see if I still have it.
Click to expand...
Click to collapse
Tired of all the meathods... nothing works .... even enabling debugging or running odin in admin.... its a request bro.... please please remake the file to root p901... its stuck at the cache.img....

[Guide] ["Port"] How to flash Android 6.0.1 on the Galaxy Note 5 from T-Mobile!

[Guide] ["Port"] How to flash Android 6.0.1 on the Galaxy Note 5 from T-Mobile!
The tarball has been uploaded!
To start off, I must say that you can revert from 6.0.1 using this method that I am using. I will break this down into steps and I will try to make it as simple as possible. It took my awhile to figure this out using trial and error so if you like this, click the thanks button.
The KNOX counter is tripped when doing this. I am not responsible for any modifications you do to your device.
What isn't working:
I regret to inform you that after doing another test in-call audio is not working. HOWEVER YOU MUST STILL DO STEPS 11 AND 11a so you can use Cellular Data. In other words; the call fix I provided does not fix call audio but it does fix messaging and data. I recommend possibly using google hangouts to call for now. (not for long, working on a fix right now)
The ability to root via supersu zip (not for long).
Step 1: Download my .zip (this contains my .tar file), from: here and download CF-Auto-root for the T-Mobile Note5.
Step 2: Download the cellular fix for the T-Mobile Note5 from here: Download the "callfix" folder (in a zip).
Step 3: Download Odin (should be anywhere on the internet, google it). Now make a folder on your desktop with the call fix folder zip called "Callfix.zip", my zip that contains my tar file (marshmallow) that you downloaded, and CF-Auto-root (the zip).
Step 4: Make sure everything in the folder looks right, it should look like this:
{
"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"
}
Step 5: Extract the "Note5601tar.zip" and the "Callfix.zip" to the same folder (right click and click extract here). Now, open the CF-Auto-root.zip and ONLY extract the file called "CF-Auto-Root-nobleltetmo-nobleltetmo-smn920t.tar.md5" to that same folder you have created on your desktop.
Step 6: Rename "CF-Auto-Root-nobleltetmo-nobleltetmo-smn920t.tar.md5" to "CF-Auto-Root-nobleltetmo-nobleltetmo-smn920t.tar" (just remove the .md5). Then, delete any file that you have extracted from (files that end in .zips in that folder). Now make sure your folder looks like this:
Step 7: Drag the Callfix folder that has been extracted to the root directory of your phone (on whatever rom you're on right now).
You are now ready to begin!
Step 8: Boot the phone into download mode (turn the phone off, then hold volume down + home + power at the same time). If you come to a warning screen, press volume up to continue.
Step 9: In Odin (3.10.7) make sure Odin can recognize your device, you should see black text with a blue backing and the word "COM" then a number. Once you verified that your device is recognized, click "AP" and select my .tar file from the folder we made earlier called "Note5TMO601.tar" (the .tar file that was extracted from the .zip). Now click open to select it.
Step 9a: Verify that Odin looks somewhat like this:
Step 10: Click "start" and wait, make sure re-partition is not checked under options!! Don't mess with anything else under options. DO NOT ASSUME YOU'RE ALL SET RIGHT AFTER THIS STEP, THERE IS MORE TO DO!
Step 11 (important): Your phone should reboot into TWRP now, swipe to allow modifications if asked. Go to "advanced > File Manager > sdcard > Callfix > bin" now click the button that is blue and has a folder with a check mark over it. Click "Copy Folder" then click that same blue button again. Now swipe to confirm.
Step 11a: Click "back", "up a level", now do the same process as "step 11" for the folders "etc", "lib", and "lib64".
Step 11b (optional, but recommended): Go home (in twrp) and go to wipe then slide to wipe data & factory reset.
Step 12: Once all the folders in "Callfix" have been moved to "/". Go home (in twrp) and tap reboot > Download.
Step 13 (IMPORTANT, PHONE WON'T BOOT IF THIS ISN'T DONE) : In download mode (close Odin if open), open up Odin, click "AP" then select the file called "CF-Auto-Root-nobleltetmo-nobleltetmo-smn920t.tar". Now click "open" to select the file and click "start". This will not root the phone, even though you will get the SuperSU app. This will simply make the phone bootable (I don't have time to explain how this works).
Step 13a: Your phone will boot and you will see a new Samsung boot animation. It will boot up about half-way the first time, then crash and reboot (this is normal if it happens only a few times).
Step 14: Smack that thanks button and report any issues!
Thanks to: @bigbiff (for TWRP), and @Chainfire (for CF-AUTO-ROOT). Also, thanks to anyone who has ever worked on the Team Win Recovery Project.

Steps 11 and 11b were supposed to revolve around a flashable zip which I wasn't able to get to work, I'll most likely figure out some way to fix the flashable zip.
Also lets all thank @Chainfire for CF-Auto-root even though it doesn't root it (it's not supposed to), but it does something way better! It makes it bootable with the kernel I'm using!

My .tar file in the .zip file is still uploading to MEGA, ETA is 1 hour.

Does this method also trigger Knox sensor?
Sent from my SM-N920T using Tapatalk

Thx.

n00b Samurai said:
Does this method also trigger Knox sensor?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Forgot to add that, yes the KNOX counter is tripped.

Whoops, never mind

What kernel are you using and do you have deep sleep
Sent from my SM-N920T using Tapatalk

mastergrillo said:
What kernel are you using and do you have deep sleep
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I am using the official kernel from the N920C firmware.

Credit to @bigbiff and any contributor to the Team Win Recovery Project since I do use TWRP in my tarball.

Are you able to make the audio fix flashable?

I'll wait for the OTA, but thanks for doing this for people.
Sent from my HTC One M9

jaxenroth said:
Are you able to make the audio fix flashable?
Click to expand...
Click to collapse
This is a quote from ethanscooter, post #2
"Steps 11 and 11b were supposed to revolve around a flashable zip which I wasn't able to get to work, I'll most likely figure out some way to fix the flashable zip."
He tried to make the call fix flashable but it didn't work. He said he is still working on it.

Almost uploaded!

ethanscooter said:
Almost uploaded!
Click to expand...
Click to collapse
SO EXCITED! My phone is sitting in Download mode waiting to be flashed.

ethanscooter said:
Almost uploaded!
Click to expand...
Click to collapse
Thank you for doing this. Looking forward to the download.

djxcee said:
Thank you for doing this. Looking forward to the download.
Click to expand...
Click to collapse
, Don't forget to have all the other files on your phone and make sure you read everything!

I regret to inform you that after doing another test in-call audio is not working. HOWEVER YOU MUST STILL DO STEPS 11 AND 11a so you can use Cellular Data. In other words; the call fix I provided does not fix call audio but it does fix messaging and data. I recommend possibly using google hangouts to call for now.
Click to expand...
Click to collapse
I did a second test and only messaging and data works after applying that call fix. In call audio never worked in the first place. Steps 11 and 11b are still requires if you want data and SMS.
I am not changing the name of the "callfix.zip" file because it still does fix cellular, just not in call audio.
On a happy note, 78% uploaded..

Updated the OP! 85% uploaded!

TIP: You can go into recovery (twrp) > mount > system. Then go to the file manager, and rename /system/lib/liboemcrypto.so to liboemcrypto.so.bak. Now you can play movies bought in google play using the youtube app without it failing to load the video.
EDIT: 93% uploaded!