Guys,
I had tried the DirtyV f2fs yest and after some failed attempts i was able to finish the job,
My TWRP shows F2FS though the converted F2FS rom fails to have superuser, tried carbon slim (default internal su also fails) both of them fail in recovery method/normal in SuperSU and Busybox on rails fails after a help from a fellow member saying that push busybox through ADB. Tried that but it also says error cant mount system, Dunno why i cant get su access....i'm posting a snap of it
Currently i'm having Skipsoft toolkit with all drivers installed and ADB setup also...can any one help me out in this issue ?? Is there anything that i've missed
current rom- carbon latest nightly with smittyv 6.15
Thankyou.
EDIT : got su working by adb root, but now how can i push busybox ?
***SOLVED***
Related
THIS IS BETA SOFTWARE
If you don't know what you are doing, don't use this.
Restoring to factory after using this process (you need using stock images):
heimdall flash --kernel stockzImage --recovery stockzImage --factoryfs factoryfs.rfs
TMobile Tab Users:
How it works: The recovery is packaged as an update.zip that you run from a modified STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork. However, ROM Manager handles this all pretty seamlessly for you.
Installation instructions for TMOBILE TAB:
Download the kernel:
TMobile - http://koush.tandtgaming.com//samsung/tab/tmobile_zImage
Installation instructions:
Flash the kernel using flash_image: http://koush.tandtgaming.com//test/flash_image (This will flash both boot and recovery)
adb push flash_image /data/local/bin/flash_image
adb push tmobile_zImage /sdcard/
adb shell
su
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/tmobile_zImage
sync
exit # This should take you back to your computer's console
Download ROM Manager from the Market.
Flash Recovery.
Choose the appropriate Galaxy Tab version.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
Verizon Tab Users:
Want to save your self some command line headaches and risk and donate to a developer? Then go download the Verizon Tab Recovery Bootstrap off the Market and use that instead of this guide.
Download the kernel:
Verizon - http://koush.tandtgaming.com//samsung/tab/verizon_zImage
Installation instructions for VERIZON TAB:
You do NOT need to do this if you used the Bootstrap application
Flash the kernel using flash_image: http://koush.tandtgaming.com//test/flash_image (This will flash both boot and recovery)
adb push flash_image /data/local/bin/flash_image
adb push verizon_zImage /sdcard/
adb shell
su
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/verizon_zImage
sync
exit # This should take you back to your computer's console
adb reboot recovery # Boot into recovery
It will now convert your rfs partitions to ext4.
Download ROM Manager from the Market.
Flash Recovery.
Choose the appropriate Galaxy Tab version.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
Euro Tab Users:
Want to save your self some command line headaches and risk and donate to a developer? Then go download the Euro Tab Recovery Bootstrap off the Market and use that instead of this guide.
Download the kernel:
Euro - http://koush.tandtgaming.com//samsung/tab/international_zImage
Installation instructions for EURO TAB:
You do NOT need to do this if you used the Bootstrap application
Flash the kernel using flash_image: http://koush.tandtgaming.com//test/flash_image (This will flash both boot and recovery)
adb push flash_image /data/local/bin/flash_image
adb push international_zImage /sdcard/
adb shell
su
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/international_zImage
sync
exit # This should take you back to your computer's console
adb reboot recovery # Boot into recovery
It will now convert your rfs partitions to ext4.
Download ROM Manager from the Market.
Flash Recovery.
Choose the appropriate Galaxy Tab version.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
If you appreciate my work, please buy the Premium version of ROM Manager!
I bought my Tab in the UK, its not locked to a carrier but I use it on the 3 network. Which of these kernels is the right one for me?
Keep up the good work!
Rom Manager has the ATT recovery but when you try to flash it it says invalid certificates. I'm running JMA firmware.
Greenarcher707 said:
Rom Manager has the ATT recovery but when you try to flash it it says invalid certificates. I'm running JMA firmware.
Click to expand...
Click to collapse
ATT is not available yet. If you read the instructions, you would see you need to manually replace the kernel first before using ROM Manager.
Sprint Tab
Will there be a version for the sprint tab? or can I use the verizon version for the Sprint tab since both are CDMA?
Thanks
This is very exciting work!
Now I can't wait to get a Tab!
Sent from my PC36100 using Tapatalk
Nice... but I'm assuming that this won't work for Euro (P1000) Tabs atm because there's no kernel image listed above?
Koush congrats on the rom recovery first of all. I must ask since sooner or later it will be asked, what happens for the ones who have the ATT sgt and proceeded to convert to the newer euro rom flash. Are we up a creek without a paddle or will you be developing the rom recovery futher for this kind of situation. Again thanks for your help and my donation will be coming very shortly Koush!!!
Backing up right now.
Thanks for the hard work.
Nice work @koush but still no go for euro tab i hope you can make one for us too
keep up the good work...
Well done, and thank you Koush.
Think we'll eventually see a way that doesn't require Odin or other coding to do stuff with the kernel?
Wow, thanks!
D'oh! my apologies.
Koush said:
ATT is not available yet. If you read the instructions, you would see you need to manually replace the kernel first before using ROM Manager.
Click to expand...
Click to collapse
I tried this, but came up with errors in recovery:
update media, please wait
update media, finished
--Install from package ...
Finding update package ...
Opening update package ...
Verifying update package ...
E:failed to verify whole-file signature
E:signature verification failed
--Appling Muti-CSC ...
Installing Muti-CSC
Installation aborted.
What did I miss?
bhagiratha said:
I tried this, but came up with errors in recovery:
update media, please wait
update media, finished
--Install from package ...
Finding update package ...
Opening update package ...
Verifying update package ...
E:failed to verify whole-file signature
E:signature verification failed
--Appling Muti-CSC ...
Installing Muti-CSC
Installation aborted.
What did I miss?
Click to expand...
Click to collapse
On VZW? I pulled that version due to bugs. I'll figure it out.
Hello and congratulations to the new advanced Kush for this product.
Is this compatible P1000 France?
Thank you in advance
Does it work with G Tab EU and if it work , which model (Verizon , TMobile , AT&T) shoud i choose pls ?
Thanks for the great progress. Cant wait for the VZW kernel
Sent from my SGH-T959 using XDA App
great work
great work koush. the link seems to be down all i get when i click it is the text. thanks in advance edit tmobile tab
Hello,
I am trying to get UbuntuDesktop using Install or Mount from this forum runnning on my Samsung S4mini
http://forum.xda-developers.com/showthread.php?t=2627255
Anyhow always when I try to mount the linux.img it says: mount: permission denied (are you root?)
(please see the attached screenshot)
You probably first recommend me to check if I have my phone properly rooted and if I have the root privileges. Yes I have both.
For rooting I used this: http://forum.xda-developers.com/showthread.php?t=2364980
It worked successfully. The App RootChecker says, Phone successfully rooted, the App SuperSU also.
I installed Terminal Emulator for the Install or Mount and also BusyBox X+ for some missing commands. Both are in the list of SuperSU and when I am starting Terminal Emulator and typing "su" a message tells me that I have SuperUser rights.
Also the installation of Install or Mount was without any error - except at the end when it was trying to mount the linux.img.
I searched the forum and google for this problem - but all solutions are concerning problems when the users didn't type su or haven't properly rooted or something similar. Unfortunately I'm a new member and so not allowed to post my question in the Q&A of the Install or Mount. I hope it's ok to do it here now.
Hi,
I've successfully rooted my FireTV Gen2 and have Kodi installed.
I want to install Xposed but the official version does not support SDK 22 or Arm64.
There is an unofficial version of xposed which works on SDK22 and Arm64 but it is a zip file flashed via recovery.
I am currently on version 5.0.4 and have tried installing CWM but could only find one guide.
I run into an issue immediately when i try chmod the cache folder:
"Unable to open /cache: Is a directory"
No **** it's a directory lol.
I've power cycled several times which hasn't helped. I can't downgrade either because SU isn't working properly.
The device is actually functioning fine and the first time I ran SU in shell the FireTV prompted me to grant.
So can anyone please tell me what the **** is going on?
joncy92 said:
Hi,
I've successfully rooted my FireTV Gen2 and have Kodi installed.
I want to install Xposed but the official version does not support SDK 22 or Arm64.
There is an unofficial version of xposed which works on SDK22 and Arm64 but it is a zip file flashed via recovery.
I am currently on version 5.0.4 and have tried installing CWM but could only find one guide.
I run into an issue immediately when i try chmod the cache folder:
"Unable to open /cache: Is a directory"
No **** it's a directory lol.
I've power cycled several times which hasn't helped. I can't downgrade either because SU isn't working properly.
The device is actually functioning fine and the first time I ran SU in shell the FireTV prompted me to grant.
So can anyone please tell me what the **** is going on?
Click to expand...
Click to collapse
Well there is no CWM for the firetv2... so there's that problem. And there is also nothing to downgrade to...
I am currently working on recovery for the firetv2 and will release it soon.
OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!
kyleyarbrough said:
OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!
Click to expand...
Click to collapse
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
HI! thanks for that advice. I wish I could. I've tried several methods, and although I can get into ADB shell, I can't access su:
besides kindle fire first aide and other batch files, I found some manual instructions:
http://forum.xda-developers.com/showthread.php?t=2277105
Here's what it tells me to do (among many other things): I realize this is just backing up stuff that doesn't exist etc, but it's indicative of the problems without having su.
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
but if I go into adb shell and type any commands, like just simple su:
I get /sbin/sh: su: not found
when I do whoami: I get root
but I get a funky prompt:
~#^[[61;5R
instead of a normal # root prompt.
So I'm kind of stuck because I can't really do anything without the su, and it says I'm root. So can I adb push over the files and mount the right drives or whatever to get it to recognize su. At that point I can install twrp, but i'm sure at that point my existing twrp will work too!
I can't seem to get it into fastboot mode either. When I adb devices it says I'm in recovery, not device and in TWRP it says no OS installed. So my only functioning loader is TWRP. (or however you put that more accurately).
I feel like with adb push working, I should be able to do something to get this back, but all the tools expect you to just push a button, not do it the hard way.
So long story short, if you can point me to a thread that tells me how to update TWRP or how to push SU over with ADB or anything that would be awesome. I"m not a complete turd at this, but I think I broke it using something like kingoroot instead of just using the bin4ry while I still had the cyanogenmod working somewhat. So I'm thinking that's why i got the funky prompt, and that's why my su is gone from where it should be.
I've got some strange problems when trying to use an app which requires superuser.
I've unlocked my bootloader, flashed TWRP and (tried to) flashed SU. But now, when I try to get SU in any app it tells me, that this is not possible.
Unlocking was done with [ToolKit] OnePlus 3 ToolKit, Unlock Bootloader, Flash TWRP, Root, and More! [v2.0]
SecureSettings tells me: Root access was not detected. The System+ module...
ES Explorer tells me: Sorry, test failed. This feature cannot run on your device
There is no overlay from SuperSU, asking if SU should be granted, and the only entries inside the SuperSU app is the ADB shell and Thermux. In this two cases the window popped up and asked if I grant SU, when calling su.
Where should the SU binaries be located? I've got a folder located directly in
Code:
/
but nothing in
Code:
/system/bin
or
Code:
/system/xbin
It uses systemless root, you won't find any supersu files in /system.
If you have twrp installed I would just grab the latest supersu beta and flash it, those toolkits always seem to cause issues that can be bypassed by learning how to do the basics yourself
Already flashed it by myself. The toolkit just pushed the zip with fastboot into storage. Then I flashed it using twrp. Also download latest version, copied it onto phone and flashed that zip. Same result...