Develop Bugs

cooking rom question. wireless tether doesnt work

I am trying to make a stock Rom with wireless tether. I have cooked successful time in the past, but this one isn't working. I am using the latest rooted stock ota Rom as a base and just adding wireless tether.
I have noticed the hboot is 0.93 which is different than what my other evo had. His maybe because of the new unrevoke for 2.2.
Any ideas?
Thanks, cody

Cant you just flash the stock rooted rom and install wireless tether?

bender1077 said:
Cant you just flash the stock rooted rom and install wireless tether?
Click to expand...
Click to collapse
i want to cook it into rom. i have a few people that are wanting it. would be nice to keep it there for when and if they hard reset.
if seems even when i do it as you discribed above, it installes wireless tether as ad hoc instead of as an access point. i think thats how its worded.
thanks, Cody

You could install to system by making a flashable zip of the app. If it gets written to system/app it will survive a full wipe.

bender1077 said:
You could install to system by making a flashable zip of the app. If it gets written to system/app it will survive a full wipe.
Click to expand...
Click to collapse
hmmm. how do i make the app a flashable zip? and how do i then make it install into the system/app?
i like this idea
thanks, Cody

I believe REGAW has made a zipmaker tool that would be able to accomplish this.
ALTERNATIVELY you can also push the apk to the /system/app/ folder via ADB, and should install automatically once pushed.
First place the APK in the TOOLS folder of the Android SDK.
CODE:
adb remount
adb push yourfilename.apk /system/app
Let me know if that works for you.

bender1077 said:
I believe REGAW has made a zipmaker tool that would be able to accomplish this.
ALTERNATIVELY you can also push the apk to the /system/app/ folder via ADB, and should install automatically once pushed.
First place the APK in the TOOLS folder of the Android SDK.
CODE:
adb remount
adb push yourfilename.apk /system/app
Let me know if that works for you.
Click to expand...
Click to collapse
lol. funny you post this. i am googleing how to push wireless tether apk with adb on a mac and found this thread. i have almost got it figured out. having fun learning.
Thanks for your help, Cody

ok, new to adb so please excuse me.
i am on a mac so it is....
./adb remount
./abd push wireless_tether_2_0_5-pre8.apk /system/app
it seemed as if the push went fine, but when i go to run the wireless tether on the device it gives me a force close.
so close
in the adb, do i need to remount a second time after i push?
do i need to exit when im done with adb before unpluging my device from the usb?
just thinking it was something silly i did wrong. i am a noob at adb

Ok! Now I'm out of my territory because I am VERY unfamiliar with Apple/Mac. Can anyone else be of any assistance?

adb is adb. don't let that bother you. the fact that i never used or seen adb it the bigger concern. i am going to push a few other apps and see it they work ok.
it seems as if either /system/apps wasn't the correct place to install wireless tether or something happened to it in the push process. this is the exact apk that i manually install on the phone after flash and it works.
hmmm, Cody

OpenVPN / tun.ko / Binary Galaxy Tab

Hi,
openvpn is up and running.
Install busybox via busybox-Installer (Market). Then install Openvpn via Openvpn-Installer (Market). I dont know if Openvpn-Installer is needed, as we are replacing the binary with another file - but as it takes care of dependencies just install it
Use tun.ko from there:
xxx.android-hilfe.de/samsung-galaxy-tab-forum/51007-openvpn-tun-ko-unionfs-ko.html
(replace the xxx with www)
Binary from here: (OpenVPN Installer won't work - its not able to recognize push options)
github.com/downloads/fries/android-external-openvpn/openvpn-static-2.1.1.bz2
Finally you have to provide the busybox-ifconfig in /system/xbin/bb/ifconfig and busybox-route in /system/xbin/bb/route (ln -s /system/bin/busybox /system/xbin/bb/ifconfig ...)
cheers
patrick

Can you give any hint how to install the additional binaries? Even with a rooted Tab and a terminal, I dot not get this working.
Sent from my GT-P1000 using Tapatalk

hi
just run openvpn installer from the market

I tried and got the connection established. But in opposite to my Desire, traffic is not routed that way.
Also, there is no /dev/tun
Addendum: Got it running, beside that I am using tap, doing a reinstall after having created the a.m. symlinks for busyboy, adding some push options on the server to force the routing did the trick (they were not required on my Desire).

I used the tun.ko module for the VPN Connections app and got it working great... except when I disable the VPN connection, it doesn't reset the dns servers to the values that where there before.
I don't believe it's the application since the same version on my Nexus One works correctly. If I turn off the data then turn it back on, I get my data back. I believe it to be the tun.ko not being written to reset the dns entries.

I think I could kiss someone, I now have working cisco vpn
How do we make the tun.ko module stay after a reboot? Mine disappeared from /modules/ when I restarted my tab? I copied it with root explorer.
Also if we can get it to stick will I have to run these commands each time?
insmod /modules/tun.ko
ln -s /system/bin/busybox/system/xbins/bb/ route
ln -s /system/bin/busybox/system/xbins/bb/ ifconfig

Hi, i am not getting this to work, is there any thing i am missing? What i did:
1. Rooted device and installed busybox
2. copying the tun.ko from the german site to /modules after remounting to r/w.
3. Running those three commands from previous post in terminal
4. Installing vpnc 0.99 and configuring connection
5. Connect
still get failed to connect.
any tips please?
Sent from my GT-P1000 using XDA App

trondjl said:
Hi, i am not getting this to work, is there any thing i am missing? What i did:
1. Rooted device and installed busybox
2. copying the tun.ko from the german site to /modules after remounting to r/w.
3. Running those three commands from previous post in terminal
4. Installing vpnc 0.99 and configuring connection
5. Connect
still get failed to connect.
any tips please?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I believe that's exactly what I did. Were all the commands successful?

works now.
I rebooted and reinstalled vpnc and busybox and recopied and reissued commands. Something must have been hanging from all my testing.
Tanks!
This is so great! Now I'm online with Sip, xmpp and RDP with work!
I know, get a life
Sent from my GT-P1000 using XDA App

I had to copy tun.ko to /system/lib/modules. I did have to create that directory but when I did, it was loaded every time.
You can make sure by using the lsmod command in the terminal emulator.

Yes, it works. Excellent!
Sent from my GT-P1000 using XDA App

sorry for noob question as i dont know that much about open vpn
i know its a virtual private network, and some ppl in my country offering a cheaper internet connection through them
what did this one do exactly?

Cisco vpn ftw
This is great! After reading everything and getting everything done I can connect through our Cisco VPN.

Question
What does this do that the Tabs built in VPN doesnt?

How can I use terminal emulator to run the two ln -s commands? I guess I need some prior commands to enable r/w to system?

I bought Better Terminal Emulator Pro in the Market to do this.
This is how I did it:
1. Install busybox from the Market into /system/bin,
2. Install root-explorer (to get r/w access to /system/xbin),
3. Create /system/xbin/bb,
4. Create symbolic links in /system/xbin/bb to busybox with the names ifconfig and route:
ln -s /system/bin/busybox /system/xbin/bb/route
ln -s /system/bin/busybox /system/xbin/bb/ifconfig
5. Copy tun.ko into /system/xbin with root-explorer,
6. Install OpenVPN from the Market into /system/xbin and set the paths to route/ifconfig to /system/xbin/bb,
7. Install OpenVPN Settings from the Market,
8. Configured to activate the TUN module via Menu / Advanced with insmod in path /system/xbin/tun.ko and to activate "Load tun kernel module"
9. Copied my existing and working OpenVPN-settings to the memory card and finally
10. Set the path to the OpenVPN configuration and to the OpenVPN binary.
After this, the OpenVPN connection could be established the data was rerouted via that connection.
@alias_neo
The internal Android functions do not support OpenVPN which can be quite easily installed on a Linux root server to establish a secure connection to that server. Setting the firewall rules on that server properly, the whole traffic can virtually enter the internet via the server and systems inbetween the Tab and the server cannot see what's going on anymore. So even an open WLAN hotspot can be safely used as well as all monitoring/logging/recording on forwarding systems sees only an encrypted connection.
Also OpenVPN is in my eyes more secure than a simple username/password encrypted connection (as PPTP offers). So, the secret to encrypt the connection is better protected as with PPTP.
If a VPN provider is used to tunnel the traffic into the internet (to hide it from the systems inbetween when there is no own server available), the encryption method of the VPN provider is relevant. For example, SwissVPN only offers PPTP or OpenVPN.

ipaqkiller said:
I had to copy tun.ko to /system/lib/modules. I did have to create that directory but when I did, it was loaded every time.
You can make sure by using the lsmod command in the terminal emulator.
Click to expand...
Click to collapse
I don't know if' I'm missing something, but I can't get the module to automatically load on a reboot. lsmod doesn't show tun.ko in the list. I have to issue insmod /system/lib/modules/tun.ko on each startup.
EDIT: Think I've sussed it, will post my details later for anyone who wishes to get this setup for cisco only without installing the openvpn installer.

ritdaw said:
I don't know if' I'm missing something, but I can't get the module to automatically load on a reboot. lsmod doesn't show tun.ko in the list. I have to issue insmod /system/lib/modules/tun.ko on each startup.
Click to expand...
Click to collapse
That's why I use the OpenVPN Settings app from the Market. It allows to activate the module with insmod when OpenVPN is started as this obviously cannot be done by the system automatically.

ipaqkiller said:
I had to copy tun.ko to /system/lib/modules. I did have to create that directory but when I did, it was loaded every time.
You can make sure by using the lsmod command in the terminal emulator.
Click to expand...
Click to collapse
akxak said:
That's why I use the OpenVPN Settings app from the Market. It allows to activate the module with insmod when OpenVPN is started as this obviously cannot be done by the system automatically.
Click to expand...
Click to collapse
Worked that out in the end, I thought it was only specific to OpenVPN connections.

Nevermind...?

Xoom WiFi (MZ604) Root!!

This is it guys... HUGE props to bigrushdog (his kernel made this possible!), MADindustries and modplan!
Download the Motorola WiFi Xoom Root Zip file and unzip it. (MediaFire) - Contains Tiamat 1.3.1
You need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
You'll need fastboot - get it here http://developer.htc.com/adp.html
Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Place the files in the SDK Tools folder.
If rebooting works... - This will wipe your phone by the way!!
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
If stuck at "Dual Core Technology"
Hold VolUp and power to restart Xoom
Hold VolDown will booting unit for fastboot mode
fastboot flash boot boot.img
fastboot reboot
adb shell
mkdir /data/media/sdcard2
exit
(physically put in microSD card if you are planning to use)
adb reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push su /system/bin
adb shell ln -s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb push vold.fstab /system/etc/vold.fstab
adb reboot
adb shell
WE HAZ ROOT!!
Check out this video for basic Windows walkthrough from Buddhahb - http://www.youtube.com/watch?v=ZsVpY0PDwtQ
Check out this video for basic Mac walkthrough from sleeplessninjas - http://www.youtube.com/watch?v=zC6J-hV6SM4
Update: 3/27/2011 12:04pm CST Added cifs.ko, tun.ko, and scsi_wait_scan.ko
Update: 3/27/2011 12:22pm CST Added vold.fstab file for USB mounting & MegaUpload
Update: 4/13/2011 10:07am CST Updated to Tiamat's 1.3.1 kernel for SD card support & Gallery support.

awesome work guys!

Woooooooooooooooooooooooooot

fantastic work!!
\o/

can you try the cifs.ko module as well? i have a 3g version and am curious

Thanks Xaositek and HUGE props to MADindustries and modplan for coming up with a quick solution.
Is there a rip of the stock "boot.img" in case it doesn't work so that people who soft brick their xoom can return it back to stock? If so can that be posted in the OP's post? I know I am not the only paranoid one that would like to have the stock boot.img before attempting any rooting.
Also just for curiousity, can someone explain the differences between the wifi and wifi+3g boot.img versions and what they had to do to workaround this. Thanks.

We end up replacing the stock boot - We'll probably need to wait for Motorola to toss us a bone there

I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
I was expecting the files to be something different that was close to the original root method by Koush where there is a "rootboot.img".
Maybe a better question for my understanding is this. Sorry if I am a noob.
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?

ericdabbs said:
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
Click to expand...
Click to collapse
It also has the su and Superuser.apk but essentially yes...
ericdabbs said:
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
Click to expand...
Click to collapse
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.

Xaositek said:
It also has the su and Superuser.apk but essentially yes...
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
Click to expand...
Click to collapse
Gotcha. Thanks for all your help.

ericdabbs said:
Gotcha. Thanks for all your help.
Click to expand...
Click to collapse
Grab the latest file from MegaUpload and add the additional modules

glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.

Guess I'll run out and grab one now at Best Buy then. Thanks!

modplan said:
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
Click to expand...
Click to collapse
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.

ericdabbs said:
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
Click to expand...
Click to collapse
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)

As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only

modplan said:
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
Click to expand...
Click to collapse
Got it. When I get my wifi xoom, I'll give this a shot.

d3coy3d said:
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
Click to expand...
Click to collapse
Tiamat's kernel allows for the 1.5ghz OC

When i command to push the first file, I get all the info on android debug.

chaz03 said:
When i command to push the first file, I get all the info on android debug.
Click to expand...
Click to collapse
Revisit the instructions now - you can just copy and paste them all now

[Q] How to change Bluetooth MAC Address

Is it possible to change it using root or adb please?

Why would you want to?

Nope. Impossible

NeoTechni said:
Why would you want to?
Click to expand...
Click to collapse
just wanted to clone my wife's one for the hands free in the car to avoid having to switch through the menu in the car.

I was unable to locate /pds as per http://pocketnow.com/tweaks-hacks/motorola-atrix-4g-how-to-change-wi-fi-and-bt-mac from http://forum.xda-developers.com/showthread.php?t=992326. I suspect every phone maker puts Bluetooth address where they wish...
However I was able to locate a zero byte bt_mac_addr file with no extension in /proc folder. It is empty both when bluetooth is on and off.
I hope someone more technically skilled than me can figure out if it can be populated to change the bluetooth address succesfully.
Thanks in advance

I looked at the '/proc/bt_mac_addr' file again using root explorer this time and can see my bluetooth mad address in it and could edit the address and change permissions to it but the modifications don't stay saved even after reboot though the root explorer says changes saved successfully. Can someone help me modifying the file please.
I'm on rooted 2.3.3

/proc is a virtual Filesystem provided by the Linux Kernel. The changes you made there won't persist a reboot cause it only gets saved in Ram.

Thank you. Does it mean I need a script of some type? Is it possible to achieve a change some other way? The pocketnow article seems to do it for the motorola phone but by modifying text file in another folder which I cannot find.
I followed the same process as follows using below commands
C:\Program Files\Android\android-sdk\platform-tools>adb push C:\APK\bt_mac_addr /sdcard/download/bt_mac_addr
1 KB/s (18 bytes in 0.015s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell
$ su
su
# cp /sdcard/download/bt_mac_addr /proc/bt_mac_addr
cp /sdcard/download/bt_mac_addr /proc/bt_mac_addr
cp: can't create '/proc/bt_mac_addr': File exists
Is there another file I can change for it maybe?
Thanks again for all the help.

If you really want to do it then you can (On stock rom) use the same trick that is used for adb remount (Put an echo whatever into into /etc/install-recovery.sh)
You need to make sure it runs as root as well
Have a play around.
Installing the insecure adb apk (From Paul Modaco).
and
adding to the end.
/system/xbin/echo 8D:64:22:01:E2:A9 > /proc/bt_mac_addr
looks like it should work.
(If you have an unlocked bootloader then you can just do it from init.semc.rc in the initramfs)
Or you can look at the method (I posted the manual method in the rooting/insecure adb thread).
This presumes that this is actually working (Its possible you might have to restart a service to actually change it).

just make a simple init.d script

Thank you both. I Will look at it when i'm at the pc. A bit scared having never done anything similar. I Appreciate your guidance very much
Sent from my R800i

Thanks again for your previous replies. I tried "/system/xbin/echo 00:01:02:03:04:05 > /proc/bt_mac_addr" using script manager with superuser permissions granted and running in root mode but it gives the following error: "echo: write error: Input/output error". Same problem in gscript unfortunately.
Would you please tell me what this means and kindly suggest what I should do. I have not figured out yet how to do adb insecure or init.d but hope you could suggest the best way after seeing the above error.
Thanks in advance

ps3taker said:
Thanks again for your previous replies. I tried "/system/xbin/echo 00:01:02:03:04:05 > /proc/bt_mac_addr" using script manager with superuser permissions granted and running in root mode but it gives the following error: "echo: write error: Input/output error". Same problem in gscript unfortunately.
Would you please tell me what this means and kindly suggest what I should do.
Thanks in advance
Click to expand...
Click to collapse
You probably have to remount /system writable

Atarii said:
You probably have to remount /system writable
Click to expand...
Click to collapse
Thank you - I tried this but still same error

ps3taker said:
Thank you - I tried this but still same error
Click to expand...
Click to collapse
try this:
Code:
echo "00:01:02:03:04:05" > /proc/bt_mac_addr

DooMLoRD said:
try this:
Code:
echo "00:01:02:03:04:05" > /proc/bt_mac_addr
Click to expand...
Click to collapse
Thanks - I tried this but it still gives the same input/output error unfortunatelly
Besides mounting system as rw via script manager option I also enabled run at boot, run on network change, run as root but still no change before and after reboot.
I hope you could think of something please. Maybe /proc folder needs to be mounted rw but i'm not sure how or if it is not rw already - root explorer has no problem openning it rw straight away...
Thanks again for everybody's help in advance

ps3taker said:
Thanks - I tried this but it still gives the same input/output error unfortunatelly
Besides mounting system as rw via script manager option I also enabled run at boot, run on network change, run as root but still no change before and after reboot.
I hope you could think of something please. Maybe /proc folder needs to be mounted rw but i'm not sure how or if it is not rw already - root explorer has no problem openning it rw straight away...
Thanks again for everybody's help in advance
Click to expand...
Click to collapse
It won't work as that interface is read only
Sent from my R800i using XDA App

Thanks for trying to help.
I wonder if there is another file somewhere. Any idea what Play's equivalent of Motorola's Atrix 4G folder called "/pds" is - as it it seems to work for them: http://pocketnow.com/tweaks-hacks/motorola-atrix-4g-how-to-change-wi-fi-and-bt-mac
Thanks again for all the help - it was exiting to try scripts and other things you pointed me to.

Superuser just won' work!

I rooted my kindle fire using kindle fire utility 0.9.6 (after the rooting superuser wasn't installed on my kindle), downloaded twrp, flashed hashcode jelly bean ROM from this link
http://forum.xda-developers.com/showthread.php?t=1766829
and then flashed Superuser-3.1.3-x86-signed.zip which I downloaded from this link
http://androidsu.com/superuser/
but superuser won't work, when I check the root explorer in ES file explorer it tells me that this feature can't work on ur phone
Please I'm really dying out here
Someone Help Pleeeeeeeeeeeeeeeeeease !!!!!

You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?

soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
Click to expand...
Click to collapse
Thank you for replying so fast
how can I install su binary? and about the superuser.apk isn't that what i flashed into my device i have a superuser icon on my desktop but it just won't add any apps to its list.
Thanks again

At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.

soupmagnet said:
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
Click to expand...
Click to collapse
what do you mean by not that it matters at this point?
can't I just download the zip and flash it?

soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
Click to expand...
Click to collapse
Maybe you missed this

soupmagnet said:
Maybe you missed this
Click to expand...
Click to collapse
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?

Scarfacew said:
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Click to expand...
Click to collapse
I too used the KFU to supposedly root my KF, but when I tried to install Titanium Backup, it gave me the same error message saying that my phone did not have root privileges... I wonder if there is something not installing correctly when using KFU...

"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.

soupmagnet said:
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
Click to expand...
Click to collapse
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
{Edit} I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized after the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance

Scarfacew said:
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
Thanks in advance
Click to expand...
Click to collapse
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.

soupmagnet said:
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
Click to expand...
Click to collapse
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized since I flashed the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance

Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.

soupmagnet said:
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
Click to expand...
Click to collapse
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.

Scarfacew said:
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Click to expand...
Click to collapse
Ok, well try a different ROM. If the problem persists then we can try to think of something.

I flashed the Alien droid ROM it's working fine till now but I need to know how to install an arabic keyboard please
Thanks

Ok, I have a dumb question, but from where do you run the DOS commands from? (ie. what directory?)..
c:\KFU?

Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.

soupmagnet said:
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
Click to expand...
Click to collapse
Thanks. but not sure i understand.
Here is what I'm attempting to do.. using the root method described here: http://forum.xda-developers.com/showthread.php?t=1638452 under "Getting to fastboot mode" there are a series of command line examples that seem to start with adb.... (ex. adb shell chmod 755 /data/local/tmp/fbmode).
Under Rooting the stock software, the first step command line is "adb shell mount system"
my question is from where do I start (directory) so that when I enter these commands they work?
Or are you saying that I need to fun all these from the KFU directory? (or KFU/tools) or some other directory..
I appreciate the help and feedback..

:h my::
Wherever adb is...Right-click on that folder to find it's path so you can "cd" or change directories to it. Alternatively, you can Shift + Right-click on that folder and select something like "Open command window here".