Database Develop

[1 Click Root and/or Recovery]Root and ClockWorkMod 5.0.2.0 [UPDATED 02/10/11]

Hello guys,
I change Maveric's 1Click root and recovery to work with new ClockWorkMod 5.0.2.0
README:
Thanks to all those who made possible this Tattoo's root
(xda-developers.com, htcmania.com and especially mainfram3 and Amon.Ra.)
HTCMANIA.COM
LIST OF COMMANDS:
RecoveryTattoo : Change new recovery. You can do a full backup. And back to original state.
rootTattoo: Change Root and new Recovery.
reboot2Recovery: Starts recovery mode.
Prerequisite:
- (PC) Close all programs / windows as possible, including Antivirus, firewall ..)
- (PC) rtattoo.zip Unzip in C:\ (must be C:\rtattoo)
- (TATTOO) All programs - USB to PC - HTC Sync
- (TATTOO) All programs - Settings - Applications - Development - USB debugging.
CONSIDERATIONS:
- You should have your functional goldcard before doing anything.
- The script takes your nCID.txt Cid and encrypted device number to nDEV.txt
(with the cid can make our goldcard)
ONLY RECOVERY:
- When you're ready from windows opened MyComputer -> (C -> rtattoo
- Double click on RecoveryTattoo. And do not touch anything, only when prompted to press a key.
ROOT+RECOVERY:
- When you're ready from windows opened MyComputer -> (C -> rtattoo
- Double click on rootTattoo. And do not touch anything, only when prompted to press a key.
If all goes well will have to restart our TATTOO.
Enjoy!!
ntenisOT
(THANKS TO Maveric!)
USE IT ON YOUR OWN RISK!!!
DOWNLOAD
New Version
1 Click Root and/or Recovery ClockWorkMod 5.0.2.0
DOWNLOAD
1 Click Root and/or Recovery ClockWorkMod 3.0.2.7
MD5 Checksum: a9098a0713ae627578412cca352359d3
1 Click Root and/or Recovery ClockWorkMod 3.0.0.5
MD5 Checksum: 67fd338e11cd378d5767ca5bd49085ca

Can I use the RecoveryTattoo script for changing my recovery from AmonRa to ClockworkMod?

Yep I did that to my Tattoo.

Wow! It worked, thanks a lot! I've been haiving some errors when installing ClockworkMod, but this worked. Thanks a bunch!

No problem mate I did that for my mobile so I thought it would be useful to share it with you.
I also reinstall the Stock Rom and tested everything so I am sure that is working.
After installing that you can flash your Tattoo with the latest Kalim's version 2.3.2 with working camera
Thanks a lot!

CM7 was the main reason I wanted ClockworkMod

I think that's the only reason for all of us!!!

ntenisOT1948 said:
Prerequisite:
- (PC) Close all programs / windows as possible, including Antivirus, firewall ..)
- (PC) rtattoo.zip Unzip in C:\ (must be C:\rtattoo)
- (TATTOO) All programs - USB to PC - HTC Sync
- (TATTOO) All programs - Settings - Applications - Development - USB debugging.
Click to expand...
Click to collapse
Do i have to install HTC-Sync Drivers (on the PC)? What is the right way to proof if the connection is stable and all drivers are installed in the right way?

tito_puente said:
Do i have to install HTC-Sync Drivers (on the PC)? What is the right way to proof if the connection is stable and all drivers are installed in the right way?
Click to expand...
Click to collapse
1. Open command prompt
2. Navigate to rtattoo directory - C:/rtattoo
3. Write: adb shell
If that can connect to your phone then you are 100% ready to start

Do i have to open the command prompt of the android sdk? Or the "normal" command prompt?
And after that i only have to do following?
ntenisOT1948 said:
ROOT+RECOVERY:
- When you're ready from windows opened MyComputer -> (C -> rtattoo
- Double click on rootTattoo. And do not touch anything, only when prompted to press a key.
If all goes well will have to restart our TATTOO.
Click to expand...
Click to collapse
The currently installed original Android 1.6 with sense will be uneffected by this process? Or will all data be deleted?

tito_puente said:
Do i have to open the command prompt of the android sdk? Or the "normal" command prompt?
And after that i only have to do following?The currently installed original Android 1.6 with sense will be uneffected by this process? Or will all data be deleted?
Click to expand...
Click to collapse
Yeah I tried that in a 1.6 installation and nothing affected until I installed a custom Rom where I had to wipe all data and cache first.. Do a nandroid backup first to be sure that you will not lose anything If something goes wrong you will be able to go back using the nandroid.

ntenisOT1948 said:
Yeah I tried that in a 1.6 installation and nothing affected until I installed a custom Rom where I had to wipe all data and cache first.. Do a nandroid backup first to be sure that you will not lose anything If something goes wrong you will be able to go back using the nandroid.
Click to expand...
Click to collapse
Thx for your quick answer, nice!
Until now i never used nandroid-backup (on my desire). Making a nandroid-backup means that i can restore the original android 1.6 without wiping or flashing? 1.6 will be restored with all its apps and settings?
If i get a continuous bootloop, is it possible to enter the recovery to restore the nandroid-backup?
btw.: After rooting the superuser-app will be installed?

tito_puente said:
Thx for your quick answer, nice!
Until now i never used nandroid-backup (on my desire). Making a nandroid-backup means that i can restore the original android 1.6 without wiping or flashing? 1.6 will be restored with all its apps and settings?
If i get a continuous bootloop, is it possible to enter the recovery to restore the nandroid-backup?
btw.: After rooting the superuser-app will be installed?
Click to expand...
Click to collapse
yes for the nandroid
I think you have to install the superuser app on your own..

How to use the RecoveryTattoo script for changing my recovery from AmonRa to ClockworkMod?
Can someone please explain how to do this?

vura said:
How to use the RecoveryTattoo script for changing my recovery from AmonRa to ClockworkMod?
Can someone please explain how to do this?
Click to expand...
Click to collapse
1.Unzip the contents to c:/rtattoo
2.Click RecoveryTattoo.bat
3.Follow on screen instructions
3. DO NOT DO ANYTHING ELSE. Just wait.
4. Your Tattoo will reboot!

rootTattoo.bat worked like a charm. No errors, tattoo rebooting. Clockworkmod is available, i already did a nandroid backup.
But now i want to install Titanium Backup to backup some of the apps. But TB always say "no root rights" available. What am i doing wrong?

tito_puente said:
rootTattoo.bat worked like a charm. No errors, tattoo rebooting. Clockworkmod is available, i already did a nandroid backup.
But now i want to install Titanium Backup to backup some of the apps. But TB always say "no root rights" available. What am i doing wrong?
Click to expand...
Click to collapse
I also installed this Root-App. It says my device is still rooted. i rooted it again. Clockworkmod 3.0.0.5 is still available, but everytime i want to use titanium it says that there are no root rights!?

tito_puente said:
I also installed this Root-App. It says my device is still rooted. i rooted it again. Clockworkmod 3.0.0.5 is still available, but everytime i want to use titanium it says that there are no root rights!?
Click to expand...
Click to collapse
i had the same problem.
start the app(titanium backup) go under problems and click to install busybox.
if the problem not solved you have to change your su.

palimpala said:
i had the same problem.
start the app(titanium backup) go under problems and click to install busybox.
if the problem not solved you have to change your su.
Click to expand...
Click to collapse
BusyBox is installed. Problem still there... how can i change superuser?

tito_puente said:
BusyBox is installed. Problem still there... how can i change superuser?
Click to expand...
Click to collapse
i tried to change superuser but its a bit complicated
so my first question is.do you want to keep your rom or are u about to flash a custom rom?

[Q] root problem

hello
im currently using an android 4.0.3 XXLQ3 rom
my main objective is to install PARANOIDANDROID rom:
http://forum.xda-developers.com/showthread.php?t=2115167
in order to get root+safe kernel + cwm i used phiz recommended method described here:
http://forum.xda-developers.com/showthread.php?t=1901191
after i flashed it i rebooted the device i now have cwm but i do not have root or supersu app and i dont know if im on safe kernel or not
i read on the forum that lq3 room has some sort of a space problem as described here
http://forum.xda-developers.com/showthread.php?t=1329360
saying:
1B.If you want just Root but not kernel, follow this
- Download Root_SuperSu 0.95
-Copy downloaded file to Ext SD card.
-Reboot into recovery (vol up+Home+power)
-Select install zip from ext SD card
-select 'root_SuperSU-*.zip' which you have copied to Ext card above
-Reboot device
-You can see superSU on appl drawer. open it and update.
-Now This will give you only SuperSU not busybox, though application which doesn't depends on system busybox will still works.e.g.Titanium Backup.
-To get full Root+busybox, Download Root_busybox *.zip
-Copy Root_busybox* only to Ext SD card
-Reboot into recovery, Select Install zip from Ext SD card. select Root_busybox* .zip and Flash.
-Done !
PS : If you can't see superSU after flashing above file(sometimes happen if there is too low space like in LQ3 ROM, then use this Root_superSU, followed by same above Root_busybox file.
Click to expand...
Click to collapse
so my questions are:
1. how do i get root from my current state? can i use the root_supersu in cwm instead of stock recover?
2. how can i tell if my kernel is safe atm? phiz is suppose to be safe but maybe if root failed the mmc_cap remove failed too?
soory for the long post
thanks in advance to all the helpers!

what is the name of the kernel( with extension) you flashed and how did you flash it?

nokiamodeln91 said:
what is the name of the kernel( with extension) you flashed and how did you flash it?
Click to expand...
Click to collapse
i flased PhilZ-cwm6-XXLQ3-OXX-3.99-signed.zip
i flashed it using stock recovery as the post described

that is correct file.. if you have cwm then the kernel has been installed... try to flash the kernel again from cwm... then reboot and see for a supersu app..

nokiamodeln91 said:
that is correct file.. if you have cwm then the kernel has been installed... try to flash the kernel again from cwm... then reboot and see for a supersu app..
Click to expand...
Click to collapse
i flashed it again using cwm i didnt see any error
still no root or supersu app i even downloaded root checker app and it says im not rooted

Hmmm. Try with the supersu zip that you mentioned earlier.

Try installing supersu from market (play store) and look if it works
Sent from my GT-N7100 using xda premium

dr.ketan said:
Try installing supersu from market (play store) and look if it works
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
it didnt work installling from the market.
i used Root_SuperSu -freespace and now im rooted
the last question i have now is my kernel safe?
phiz kernel suppose to be safe does super_su somehow overwrite the mmc_cap erase?

If your recovery is philz cwm then you have safe kern l
Sent from my GT-N7100 using xda premium

Nope. It's safe. Kernel is what has the erase command disabled and supersu just installs supersu

Thanks for everyone's help managed to root and install
u can close thread.

Ok

[ROM] [STOCK] [SO-02E] Rooted 10.1.D.0.343 (w/XZDualRecovery)

UPDATE: If you're already on an unrooted 10.1.D.0.343 - a new exploit has been found so check out this thread to root it.
After much digging through the threads and the net looking for a working Rooted 10.1.D.0.343 ROM for the SO-02E with no luck I decided to make my own and share it to everyone who own the SO-02E variant from Docomo.
This ROM is fully stock with the exception of having Superuser and XZDualRecovery installed. No default files have been tweaked in anyway.
I made this ROM using the guide from [NUT]
All the scripts were made by [NUT] - I just replaced some files to make XZDualRecovery work for the SO-02E.
I am not a developer or anything - I'm just some guy who loves his SO-02E
I tested this on my SO-02E, upgraded from 10.1.D.0.333 to 10.1.D.0.343 and everything works.
No reboot issue when mounting the system as R/W and no issues booting into recovery.
No data is lost and all apps are retained when upgrading so you should be good - but backup your data just in case.
Prerequisite:
Rooted 10.1.D.0.333
Recovery Installed (e.g. XZDualRecovery)
Installation:
1. Copy SO-02E_10.1.D.0.343_system.zip to your SDCard
2. Flash SO-02E_10.1.D.0.343_stripped.ftf with Flashtool (make sure nothing is ticked)
3. Boot straight into recovery
4. Flash SO-02E_10.1.D.0.343_system.zip
5. Clear cache (optional but it doesn't hurt to)
6. Reboot
7. Profit!!!
Special thanks to [NUT] for getting XZDualRecovery working on the SO-02E
Stock Odexed Files:
(I split SO-02E_10.1.D.0.343_system.zip into two files for download so you need to join them with 7zip and copy the .zip file to the SDCard )
SO-02E_10.1.D.0.343_stripped.ftf
Download
Mirror
SO-02E_10.1.D.0.343_system.zip.7z.001
Download
Mirror
SO-02E_10.1.D.0.343_system.zip.7z.002
Download
Mirror

[MOD]
[MOD] Stock ROM 10.1.D.0.343 Deodexed and zipaligned
Installing this mod will update your 10.1.D.0.343 so it's deodexed and zipaligned.
Prerequisite:
Rooted stock 10.1.D.0.343
Installation:
1. Copy 343.deodex_zipaligned.zip to your SDCard
2. Boot into recovery
3. Flash 343.deodex_zipaligned.zip
4. Clear cache
5. Reboot
6. Profit!!!
343.deodex_zipaligned.zip.7z.001
Download
Mirror
343.deodex_zipaligned.zip.7z.002
Download
Mirror
--------------------------------
[SMALL APP] Serajr Power Toggles - 23 Toggles Set - v1.1 - 10/06/13
Check out this thread for more info
Tweaked for 10.1.D.0.343
Install in Recovery
Download
-----------------------------

Nice to see my guide put to good use, this is exactly why I made it in the first place! :highfive:
Have fun with this release people :good:

Must I join 2 files: "SO-02E_10.1.D.0.343_system.zip.7z.001 and SO-02E_10.1.D.0.343_system.zip.7z.002" before I copy it to SD card?

nak89 said:
Must I join 2 files: "SO-02E_10.1.D.0.343_system.zip.7z.001 and SO-02E_10.1.D.0.343_system.zip.7z.002" before I copy it to SD card?
Click to expand...
Click to collapse
It's my fault for not be more clear - yes you need to join them with 7zip (or whatever program that recognizes 7z formats). From there you'll end up with SO-02E_10.1.D.0.343_system.zip, copy the .zip to the SD and use TWRP or CWM to flash.
I'll update my OP to make it more clear.

nak89 said:
Must I join 2 files: "SO-02E_10.1.D.0.343_system.zip.7z.001 and SO-02E_10.1.D.0.343_system.zip.7z.002" before I copy it to SD card?
Click to expand...
Click to collapse
Yes. Extract both of them together and put it in one folder.

I did it, but I only can upgrade to .343 but it has not root?

nak89 said:
I did it, but I only can upgrade to .343 but it has not root?
Click to expand...
Click to collapse
It does have root. What version were you coming from before? If you're already on an unrooted 10.1.D.0.343 then you'll need to downgrade to 10.1.D.0.333 via Flashtool, root it, install XZDualRecovery, then upgrade to 10.1.D.0.343 as written in the OP.

lancebukkake said:
It does have root. What version were you coming from before? If you're already on an unrooted 10.1.D.0.343 then you'll need to downgrade to 10.1.D.0.333 via Flashtool, root it, install XZDualRecovery, then upgrade to 10.1.D.0.343 as written in the OP.
Click to expand...
Click to collapse
In .333, What tool do you use to root? I'll try it Thanks!

nak89 said:
In .333, What tool do you use to root? I'll try it Thanks!
Click to expand...
Click to collapse
Check out this thread on rooting .333
After you have root you need to install XZDualRecovery.

lancebukkake said:
Check out this thread on rooting .333
After you have root you need to install XZDualRecovery.
Click to expand...
Click to collapse
Thank so much, I had 343 with root + deodex

nak89 said:
Thank so much, I had 343 with root + deodex
Click to expand...
Click to collapse
glad to help :good:

lancebukkake said:
glad to help :good:
Click to expand...
Click to collapse
Why does my Root Explore always force close?

nak89 said:
Why does my Root Explore always force close?
Click to expand...
Click to collapse
hmmm...that's strange. I tested it, with nothing installed except for Root Explorer and it doesn't FC on me. I've tested R/W to system and all is good.

nak89 said:
Why does my Root Explore always force close?
Click to expand...
Click to collapse
Take a look at this thread - this should help.

Nice thread sir..now I can root the Z docomo of my cousin thanks again

i'm on 10.31b.0256 .. what can i do?

tufoz said:
i'm on 10.31b.0256 .. what can i do?
Click to expand...
Click to collapse
if you the easiest root way, go [URL="http://cubeundcube.blogspot.jp/2013/11/xperiarootz-so-02e-so-04e.htm]this linkl[/url], clik the rootkitZ_20131112.zip. I've tried this and works.

[MOD][4.4.2]Native Tether for Build 183.46.15

YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. WE ARE NOT RESPONSIBLE FOR YOUR DEVICE. FLASH AT YOUR OWN RISK.​
This will enable Native Tether for Build 183.46.15. Shout out goes to iKrYpToNite for his work with this.
Prerequisites:
Droid RAZR M Rooted or unlocked on 183.46.15
METHOD 1: TWRP INSTALL
1) Download the package below labeled "183.46.15_tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
METHOD 2: MANUAL INSTALL
1) Download the package below labeled "183.46.15_tether_manual".
2) Download root browser by Jrummy from the play store
3) Navigate to System/Priv-App and rename VZWEntitlementservice.apk to VzwEntitlementservice.apk.bak.
4) Navigate to System and rename the build.prop to build.prop.bak
5) Place the package on the root of your sd card and extract the build.prop file within the folder.
6) Navigate to system and Copy and paste the new file.
7) Set permissions for the file to
Owner: Read/Write
Group: Read
Others: Read
This should show (rw-r--r--)
8) Reboot. Verify tether works
9) Profit.
REVERTING
METHOD 1:
If installed in twrp, download the package below labeled 183.46.15_tether_revert. Flash in Twrp, reboot, verify subscription check re-enabled.
METHOD 2:
If manually installed, simply delete the build.prop you installed, remove the .bak extension from the original build.prop, verify permissions, reboot.
If you enjoyed this, consider donating! I do appreciate it.

Topsnake said:
METHOD 1: TWRP INSTALL
1) Download the package below labeled "183.46.15_tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
Click to expand...
Click to collapse
I can confirm that tethering does work on the latest 183.46.15 build using this method. I flashed the .zip in TWRP, rebooted, and the Mobile Hotspot is now working. Thank you for working on this for all of us!

ScallywagginIT said:
I can confirm that tethering does work on the latest 183.46.15 build using this method. I flashed the .zip in TWRP, rebooted, and the Mobile Hotspot is now working. Thank you for working on this for all of us!
Click to expand...
Click to collapse
No problem!

Thanks for your time again Topsnake... I'll be flashing .15 when I get home was kinda hoping you would put one out for the update...
We cannot teach people anything; we can only help them discover it within themselves.

Hello
Whats the lines should be added to original build prop? or what needs to be changed?

i m confused
u said u can flash native tether using twrp recovery in 183.46.15 build...
but i read in most forums that 183.46.15 build cant be unlocked nor can install custom recovery.. so how u can flash native tether using twrp..
plz tell me if there is a way to install twrp in 183.46.15 build.. i tried lot to install twrp but nothing working..

rahulbeast said:
u said u can flash native tether using twrp recovery in 183.46.15 build...
but i read in most forums that 183.46.15 build cant be unlocked nor can install custom recovery.. so how u can flash native tether using twrp..
plz tell me if there is a way to install twrp in 183.46.15 build.. i tried lot to install twrp but nothing working..
Click to expand...
Click to collapse
bootloader was unlockable before 183.46.15
if bootloader is unlocked, updating doesnt lock the bootloader
if bootloader is locked you just need root access to
to change the build.prop
XT907 with kernel date July 2014 or after
can now be unlocked with sunshine app
http://theroot.ninja/download.html
xda thread: http://forum.xda-developers.com/showthread.php?t=2792487
free to test compatibility, $25 to unlock
I would root with hydrogen peroxide, even though kingroot or temporary root should work too
Sent from my XT1060 using XDA Labs
---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------
see method #2
Sent from my XT1060 using XDA Labs

what exactly is edited in the build prop? so I can just make the changes myself without losing my current build prop edits. Thanks!

motolio said:
what exactly is edited in the build prop? so I can just make the changes myself without losing my current build prop edits. Thanks!
Click to expand...
Click to collapse
post #1 method 2

hello a question like I can put transparent bars of notification and navbars, can you teach me?

CWM RECOVERY for Galaxy J700t1 (Metro PCS variant)

Ok guys here is a custom recovery for the metro 2016 variant of the Galaxy J700t1 (Metro PCS) Flash with FlashFire or with Odin. Custom recovery but it won't mount the internal sd yet. Can't flash or backup.. so its still a work in progress, but its a working recovery other than that lol. Must be rooted first. Make sure that you download root file explorer and ensure you have a copy of su and busybox in your /system/bin and /system/xbin folders. Make sure you have USB debugging on, OEM on, and unknown sources on in System-Developer options. Thanks to Paco for the root exploit! But we needed a recovery for this fine device. Enjoy!
EDIT: SOME CLARITY FOR EVERYONE... ok, so here's the deal. In marshmallow the system is write protected after you trip KNOX 0x1. The system will persist and will lose integrity if the stock kernel's "CASHE" gets changed. hmmm.... so. this is what you need your system to be at if you want to flash a custom kernel or recovery with flashfire or flashify: After you root with Paco's method, you should be on stock rooted rom with stock recovery. when you flash with flashfire DO NOT WIPE CASHE OR DALVIK CASHE OR FORMAT CASHE in ANY WAY ... IT WILL SEND YOU INTO THE "RESET MODE"... NO worries tho. If this happens to you , ODIN this stock kernel CASHE that i'm posting below and you should boot back up. Keep in mind what you're doing as well... if for some reason you hit the "RESET" SCREEN, don't flip... just ODIN the partition you changed back to stock whether it be the kernel or in this case the RECOVERY. ... also, try not to use ever root in flashify/ flashfire because it lowers the permissions for the SU binaries and removes SU from some of the system folders.
INSTRUCTIONS:
1. start from stock if you can.
2.root via paco's method HERE
3.I would make sure you have a stock copy of the stock firmware (ROM KERNEL RECOVERY) on your computer just in case
HERE
4.download my cwm port for the j700t1 below and put it on the root of your drive or anywhere on your phones internal memory (not your external sd card)
5. Download root browser from the playstore as well as flashfire or flashify or both.
6.rename the cwm.img to recovery.img with root browser and ensure that you have SU and Busybox in /system/bin , /system/xbin , and it wouldn't hurt to have it in ~#/sbin as well..... AND check the permissions with root browser to make sure the permissions are set to 0777 (rwrwrwrw)
7. In "Flashfire" click the "+" symbol - click "Flash firmware package" -- Go to the cwm "recovery" file you put on your internal sd card and select the file. Fireflash will bring a screen up saying "Partitions" at the top showing the package. Click the check mark at the top right. FlashFire will go back to the "Actions" screen. Click"reboot" toward the bottom. Under the "reboot" screen, click recovery to boot directly into your new recovery after the flash. Uncheck Preserve recovery- click the check mark at the top right again. Click "Flash" at the bottom. --- wait. Device will reboot... flashfire will take over and your loading screen willl flash by... phone will boot back up into CWM....
To Flash ODIN tars --- Rename the perspective tar to the partition it goes to before trying to odin. Example: rename "cwm.recovery.img." to just "recovery.img" ... Same with the stock kernel tar below. . rename to "boot.img" then ODIN.
Sideload apps or ROMS or ZIPS just don't wipe any cashe partitions until we can get a good custom kernel. I could use the help with the kernel I will be honest. I can get it done but with a lot of trial and error. Anyone who can remove the SELinux write protection from the kernel please contact me.. I'm working on it. I was able to get a custom kernel to boot. but still no r/w mount for the USB yet. Just keep the CASHE lol. One more thing.. if your'e testing kernels, everytime you have to odin a stock kernel you will LOSE ROOT, so go ahead and re-root again.
https://drive.google.com/file/d/0B_WsJ57QBykaQ3ROeFZnajNzbmc/view?usp=sharing --- CWM img
CWM.TAR-- (new
--Stock Kernel CASHE.tar
Stock KERNEL
Team Rejectz

removed as it was reported not working by @timmetal6669

messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
thank you!! the one I sent you? will flash right away

timmetal6669 said:
thank you!! the one I sent you? will flash right away
Click to expand...
Click to collapse
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t

messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
not working...
do not flash this
Here is an odin flashable copy of the j700t1 stock kernel to get you booting again. just go into download mode, open odin and flash this if you happened to flash one of the kernels above
https://drive.google.com/open?id=0B_WsJ57QBykaSDRlQXlXSnpSd28

messi2050 said:
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
Click to expand...
Click to collapse
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:

timmetal6669 said:
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
Click to expand...
Click to collapse
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that

messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
Sent me into a loop... but I'm the metro pcs variant
Oh update... If anyone uses that odin flashable stock boot.img .. remember it IS a stock boot img. you will lose root. but you won't lose your system and your apps.. so just re root using paco's CF autroot exploit.

messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
might just be what i'll have to do.. the boot image is its own source

So no progress on the recovery to backup or flash yet?

Krumplife4400 said:
So no progress on the recovery to backup or flash yet?
Click to expand...
Click to collapse
Im working on it. the recovery is flashable and it works... just won't mount the SD right now... I have to right a script or look for a work around.. give me a bit...might take a few days. I'm a single dad and im' in school. I do this cuz i love it and I just bought this phone... Don't worry.,.. I'll be making ROMs before you know it... lol... mods everything... look up my threads lol

Thanks keep up the good work

Are you able to mount USB-OTG?? I am about to leave work so I haven't had a chance to play yet!

I can confirm it boots on j700t as well. I haven't flashed anything but it's there. I got twrp to boot and stay for roughly 5 minutes but still cannot mount anything either.
Sent from my SM-J700T using XDA-Developers mobile app

Verification Failed
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..

!Led*Eyes! said:
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
Click to expand...
Click to collapse
Start over.
Set up phone like day one
Re-root with cf auto root
Update su binaries
Install BusyBox
Install flashify
Download IMG from op
After download, tap on IMG file should bring up flashify as an option
Flash IMG and reboot
Profit.
- I see you're good but no cwm? Skip start over root part and use flashify.
-sent from this device using this app.

So flashify over flashfire ? Ill give it a shot. Thanks

!Led*Eyes! said:
So flashify over flashfire ? Ill give it a shot. Thanks
Click to expand...
Click to collapse
No problem
sent from the interwebs using dis here application an m'digits....

I decided to just try it with flashify without reverting everything back to stock and voila! I chose the google drive option when searching for the file so it did download it again.... i re member reading something a while back about about a similar issue with not being able to mount the sdcard because the fs was encrypted and the recovery couldnt read it. I think they overcame by formatting the sdcard but i do not know .. i realize that simply formatting the sd in recovery and trying to mount would be fruitless but could the trouble be in the "expected recovery key" ? Just a thought. Thanks again timmetal6669 & OriginalShinken1 for the beta and the help. You guys are so close!

Has anyone tried to sideload a ROM yet since we can't flash?