Database Users

[R&D Ubuntu on a rooted Galaxy S4]

After rooting my S4 I was checking around online for any way to boot into ubuntu on it as I think it would look awesome on the S4 and it would run smoother than it did on my dead Note. While snooping around google I was suprised that no one even mentioned trying to run ubuntu on the new Galaxy S4 so I took it upon myself to try to run it through the terminal into vnc.
Sadly after a lot of attempts I keep getting the script to boot I started looking online for a similar ubuntu.sh script and found one for the S3 herehttp://www.redmondpie.com/how-to-run-ubuntu-linux-on-galaxy-s-iii/. So I got it and changed the /sdacrd that most phones have and changed it to /storage/extSdCard as this is where the external sdcard on the S4 is and now get this error in the terminal.
.../storage/extSdCard/ubuntu # sh ubuntu.sh
ubuntu.sh[17]: syntax error: "if" unmatched
I know this is an error in line 17 which is:
if [ -b /dev/block/loop255 ]; then
echo "Loop device exists"
else
busybox mknod /dev/block/loop255 b 7 255
fi
I'm not really familiar with loops and would be happy for some help with this as others might find it useful too.
I have attached the original ubuntu.sh by zacthespack with only the directories changed.
NOTE: I have an ubuntu.sh that I got to boot last night at home, but all I got is a white screen in vnc. zacthespack says it might be a vnc issue but I doubt it as I have tried multiple different vnc's. I will upload the ubuntu.sh when I get home (if zac allows me )

Sorry...first time posting. Anyway to move it?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Couple of things...
1. You need to boot or chroot into an Ubuntu image (Complete Linux Installer does this)
2. Running Ubuntu natively is pointless and very difficult since you need a working Freedreno setup and the means to hijack the screen
3. What are you trying to do again?

To boot into ubuntu. I have complete ubuntu installer and it still doesn't work.
To be more specific it says "cannot attach image to loop device"
{
"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"
}
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Ubuntu is nice but would like to see backtrack5 . Nothing like a full (well mostly full if chroot) pentest suite in your pocket.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Bender B. Rodgriguez said:
Ubuntu is nice but would like to see backtrack5 . Nothing like a full (well mostly full if chroot) pentest suite in your pocket.
Click to expand...
Click to collapse
Yeah that would be pretty cool too. Im going to look into it on my free time.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Bender B. Rodgriguez said:
Ubuntu is nice but would like to see backtrack5 . Nothing like a full (well mostly full if chroot) pentest suite in your pocket.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
fwiw dsploit does ~80% of what BT5 does
http://www.dsploit.net/

jbe4 said:
fwiw dsploit does ~80% of what BT5 does
http://www.dsploit.net/
Click to expand...
Click to collapse
Yeah I agree, Ive used it before. Still like to have the full bt5 suite tho.
Only so much can be done with MITM , session hijacking stuff. I also like to have dirbuster, and the webapp tools as well.
I also prefer not to use tools that any monkey can pick up on. Not that BT is uber-hard and only for the dedicated pentester, but the linux learning curve is enough to keep it out of the hands of the truly unworthy.

greenzone560 said:
To boot into ubuntu. I have complete ubuntu installer and it still doesn't work.
To be more specific it says "cannot attach image to loop device"
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Are you 100% positive that is the correct mount point?
I ask because with Android 4.2.2 they have emulated mount points for the internal SD card but not 100% sure about the external.
Can you browse to the image using an app like ES file Explorer. If so what is the path you used?
Do an 'ls' command from the prompt you showed and see whats there?

jbe4 said:
fwiw dsploit does ~80% of what BT5 does
http://www.dsploit.net/
Click to expand...
Click to collapse
if you truly know your way around BT5, or the newer Kali Linux, no, dsploit does not do ~80% of what they do, but a mere 5% at most.

scrosler said:
Are you 100% positive that is the correct mount point?
I ask because with Android 4.2.2 they have emulated mount points for the internal SD card but not 100% sure about the external.
Can you browse to the image using an app like ES file Explorer. If so what is the path you used?
Do an 'ls' command from the prompt you showed and see whats there?
Click to expand...
Click to collapse
Im not 100% sure that the external SD has emulated points but, it sure seems like it. Yes I can browse it with Root Browser (personal preference). The mount point for ext. sd card is /storage/extSdCard...Im 100% sure of that.

I used motochoppers exploit to root, so I don't know if that makes a difference. As far as I know it should not affect the emulation process since we are at the root level anyways. Vnc and rdp apps work, so emulation on the internal sd is fine. Its just that it doesn't want to bind internal and external into one process...so to speak.

greenzone560 said:
Im not 100% sure that the external SD has emulated points but, it sure seems like it. Yes I can browse it with Root Browser (personal preference). The mount point for ext. sd card is /storage/extSdCard...Im 100% sure of that.
Click to expand...
Click to collapse
yep, that's the correct mount for the external. I had seen this article previously too for bt5, idk if it'll actually help though

Just reread this post. I see you are making good progress here.
As for the vnc issue. When I did a backtrack chroot on my skyrocket there were similar issues. The fix was basically to edit the vnc ui file and set it to the correct screen dimensions of the phone.
Read this and try the sed command to change them accordingly. The path to the vnc files may be different in ubuntu as well.
Sorry if way off base here , just figured I would offer a suggestion
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 01:39 AM ---------- Previous post was at 01:38 AM ----------
greenzone560 said:
After rooting my S4 I was checking around online for any way to boot into ubuntu on it as I think it would look awesome on the S4 and it would run smoother than it did on my dead Note. While snooping around google I was suprised that no one even mentioned trying to run ubuntu on the new Galaxy S4 so I took it upon myself to try to run it through the terminal into vnc.
Sadly after a lot of attempts I keep getting the script to boot I started looking online for a similar ubuntu.sh script and found one for the S3 herehttp://www.redmondpie.com/how-to-run-ubuntu-linux-on-galaxy-s-iii/. So I got it and changed the /sdacrd that most phones have and changed it to /storage/extSdCard as this is where the external sdcard on the S4 is and now get this error in the terminal.
.../storage/extSdCard/ubuntu # sh ubuntu.sh
ubuntu.sh[17]: syntax error: "if" unmatched
I know this is an error in line 17 which is:
if [ -b /dev/block/loop255 ]; then
echo "Loop device exists"
else
busybox mknod /dev/block/loop255 b 7 255
fi
I'm not really familiar with loops and would be happy for some help with this as others might find it useful too.
I have attached the original ubuntu.sh by zacthespack with only the directories changed.
NOTE: I have an ubuntu.sh that I got to boot last night at home, but all I got is a white screen in vnc. zacthespack says it might be a vnc issue but I doubt it as I have tried multiple different vnc's. I will upload the ubuntu.sh when I get home (if zac allows me )
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Bender B. Rodgriguez said:
Just reread this post. I see you are making good progress here.
As for the vnc issue. When I did a backtrack chroot on my skyrocket there were similar issues. The fix was basically to edit the vnc ui file and set it to the correct screen dimensions of the phone.
Read this and try the sed command to change them accordingly. The path to the vnc files may be different in ubuntu as well.
Sorry if way off base here , just figured I would offer a suggestion
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 01:39 AM ---------- Previous post was at 01:38 AM ----------
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nope, not off topic at all. I will look into the .img file and see if anything is different there. Which I'm assuming I will need to change from sdcard to extSdCard for it to let through to the vnc.

I have finally found a solution to the "if" unmatched problem. The ubuntu.sh needs to edited in a linux enviorment because it breaks if you edit it in windows. I will post the ubuntu.sh later today. Also I think I have backtrack 5 down too
EDIT: Okay, I'm stumped...I have no idea why it can't see "system/bin/sh"
Here is the error:
[email protected]:/storage/extSdCard/bt5 # sh bootbt
BACKTRACK 5 IS STARTING PLEASE WAIT...
loop device exists!
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': No such file or directory
....
unmount: can't unmount /data/local/mnt/dev/proc: invalid argument
unmount: can't unmount /data/local/mnt/sys: invalid argument
etc...
losetup: /dev/block/loop255: No such device or address
And here is the script I used:
echo "BACKTRACK 5 IS STARTING PLEASE WAIT..."
perm=$(id|cut -b 5)
if [ "$perm" != "0" ];
then echo "This Script Needs Root! Type : su";exit;fi
chmod 755 /data/local
mount -o remount,rw /dev/block/mmcblk0p5 /system
export bin=/system/bin/
####Sometimes people have busybox installed in /xbin##########
export bin=/system/xbin/
export kit=/storage/extSdCard/bt5
export mnt=/data/local/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/root
if [ -b /dev/block/loop255 ]; then
echo "loop device exists!"
else
busybox mknod /dev/block/loop255 b 7 255
fi
busybox mkdir /data/local/mnt > /dev/null 2>&1
busybox mkdir /data/local/mnt/proc > /dev/null 2>&1
busybox mkdir /data/local/mnt/sys > /dev/null 2>&1
busybox mkdir /data/local/mnt/dev > /dev/null 2>&1
busybox mkdir /data/local/mnt/dev/pts > /dev/null 2>&1
busybox mkdir /data/local/mnt/sdcard > /dev/null 2>&1
busybox mkdir /data/local/mnt/extSdCard > /dev/null 2>&1
busybox mkdir /data/local/bin/bash > /dev/null 2>&1
if
[ ! -d "/data/local/mnt/sdcard" ]; then
mkdir /data/local/mnt/sdcard
fi
busybox mount -o bind /sdcard /data/local/mnt/sdcard
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $mnt/etc/hosts
echo "Back Track is configured with SSH and VNC servers that can be accessed from the IP:"
if
config wlan0
echo " "
busybox chroot $mnt /bin/bash
echo "Shutting down BackTrack ARM"
umount /sdcard
umount /storage/extSdCard
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
losetup -d /dev/block/loop255
If anyone can help, then please do Thanks in advance...

Bump. Anyone?
Sent from my GALAXY [S4] SGH-I337 using xda app-developers app

greenzone560 said:
Bump. Anyone?
Sent from my GALAXY [S4] SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Hey greenzone,
I had a few minutes tonight so I took the scripts that worked for the sgs2 and made a few minor changes to them. I got BT5 to boot! VNC only shows the grey screen though. I will have to take a look at it a little closer. Here are the scripts that used.
Drop files in sdcard/bt
image needs to be named bt.img
Busybox needs to be installed in /system/xbin

Bender B. Rodgriguez said:
Hey greenzone,
I had a few minutes tonight so I took the scripts that worked for the sgs2 and made a few minor changes to them. I got BT5 to boot! VNC only shows the grey screen though. I will have to take a look at it a little closer. Here are the scripts that used.
Drop files in sdcard/bt
image needs to be named bt.img
Busybox needs to be installed in /system/xbin
Click to expand...
Click to collapse
Wont boot on mine..I get system/xbin/busybox not found error. I tried changing it to /bin still no go. What can cause that? I tried reinstalling in both of those directories so dont even go there lol
EDIT: here is a screen.
http://s24.postimg.org/nqoclmal1/Screenshot_2013_05_18_21_54_13.png
Sent from my GALAXY [S4] SGH-I337 using xda app-developers app

greenzone560 said:
Wont boot on mine..I get system/xbin/busybox not found error. I tried changing it to /bin still no go. What can cause that? I tried reinstalling in both of those directories so dont even go there lol
EDIT: here is a screen.
http://s24.postimg.org/nqoclmal1/Screenshot_2013_05_18_21_54_13.png
Sent from my GALAXY [S4] SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Hrmm..
It definitely looks like busybox is not in /system/xbin from your output. I know you said not go to there but just verify the busybox binary is there. ( ls /system/xbin/busybox).
You can also change the "busybox path" variable in all the scripts to point to where you have busybox installed.
Also all the files and the bt image need to be in /sdcard/bt or the script will not work anyways. Or you can edit the path in the "kit" variable in the scripts to point to the folder you are using on your external sd card.
also run in order
installbt.sh
startbt
bt

[HOW TO] [FIX] Recover from nested emulated 0 folders

A user of my rom had this 0 folder issue.
This issue was new to me so it took a couple hours to find a solution.
Didn't find any related "How To" guides here so i thought i would share it here.
The issue is that your pc file explorer for example (Win Explorer) only sees a 0 folder while still running the latest HTC USB drivers.
Well, there is a solution to recover from 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"
}
To recover from this you can try the following but you must be running the latest htc drivers.
Step 1
Connect your phone to your pc by USB (note: not usb3)
Backup all your sdcard content to your pc
Download this zip file and extract this to the root of your hardisk (adb.zip)
Step 2
Now open a command shell and go to your adb folder
You can open a shell by ticking "Windows start button" and type "cmd" in the search bar and hit enter.
then type the following commands in the just opened shell and hit enter after every command
cd..
cd..
cd adb
adb shell
You should now see something like "[email protected]/#"
Step 3
Now type the following commands one by one in this shell and after every command hit enter
adb shell
rm -r /data/media/0
busybox find /data/media -maxdepth 1 ! -path "/data/media" ! -path "/data/media/0" | while read filename; do mv "${filename}" /data/media/0/ ; done
Now reboot your device.
If all went fine then you just reset the 0 folder symlink and flashed a compatible recovery
If you now go to Windows Explorer then you should see your sdcard content
If the above how to didn't help the try the steps below:
Step 1
Connect your phone to your pc by USB (note: not usb3)
Backup all your sdcard content to your pc
Download this zip file and extract this to the root of your hardisk (adb.zip)
Download TWRP 2.5.0.0 recovery (recovery.img) (md5: C18DA6C73B2C7CCC9539E58C678C8DD6) and copy it to the adb folder in the root of your hardisk you just created
Step 2
Now open a command shell and go to your adb folder
You can open a shell by ticking "Windows start button" and type "cmd" in the search bar and hit enter.
then type the following commands in the just opened shell and hit enter after every command
cd..
cd..
cd adb
adb shell
You should now see something like "[email protected]/#"
Step 3
Now type the following commands one by one in this shell and after every command hit enter
adb shell
rm -r /data/media/0
busybox find /data/media -maxdepth 1 ! -path "/data/media" ! -path "/data/media/0" | while read filename; do mv "${filename}" /data/media/0/ ; done
Step 4
Now reboot into your bootloader while your phone still connected to usb.
When your bootloader recognizes your phone you should see in red "Fastboot USB"
If not then your USB drivers aren't up to date or your using USB 3
If so then type the following commands and after every command you must hit ENTER
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Goodluck :fingers-crossed:

V6-Maniac said:
A user of my rom had this 0 folder issue.
This issue was new to me so it took a couple hours to find a solution.
Didn't find any related "How To" guides here so i thought i would share it here.
The issue is that your pc file explorer for example (Win Explorer) only sees a 0 folder while still running the latest HTC USB drivers.
Well, there is a solution to recover from this.
Most likely your on Clockwork Mod Recovery when this is happening.
Not gonna tell ya the whole story but there is a issue with CWM and 0 folders.
To recover from this you can try the following but you must be running the latest htc drivers.
Step 1
Connect your phone to your pc by USB (note: not usb3)
Backup all your sdcard content to your pc
Download this zip file and extract this to the root of your hardisk (adb.zip)
Download TWRP 2.5.0.0 recovery (recovery.img) (md5: C18DA6C73B2C7CCC9539E58C678C8DD6) and copy it to the adb folder in the root of your hardisk you just created
Step 2
Now open a command shell and go to your adb folder
You can open a shell by ticking "Windows start button" and type "cmd" in the search bar and hit enter.
then type the following commands in the just opened shell and hit enter after every command
cd..
cd..
cd adb
adb shell
You should now see something like "[email protected]/#"
Step 3
Now type the following commands one by one in this shell and after every command hit enter
adb shell
rm -r /data/media/0
busybox find /data/media -maxdepth 1 ! -path "/data/media" ! -path "/data/media/0" | while read filename; do mv "${filename}" /data/media/0/ ; done
Step 4
Now reboot into your bootloader while your phone still connected to usb.
When your bootloader recognizes your phone you should see in red "Fastboot USB"
If not then your USB drivers aren't up to date or your using USB 3
If so then type the following commands and after every command you must hit ENTER
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
If all went fine then you just reset the 0 folder symlink and flashed a compatible recovery
If you now go to Windows Explorer then you should see your sdcard content
Goodluck :fingers-crossed:
Click to expand...
Click to collapse
It's an issue when upgrading from 4.1.2 to 4.2.2.
User can copy files to pc prior to upgrading, then copy back after and the files can be copied to the folder visible to Windows.
Also, creating a symlink to /data/media/clockworkmod in /data/media/0/ will allow a user to get CWM to see backups and allow the user to have access to it in the folder visible to Windows.
Your solution ignores the fact the someone might prefer CWM over TWRP.
Sent from my HTC One using xda app-developers app

ilal2ielli said:
It's an issue when upgrading from 4.1.2 to 4.2.2.
User can copy files to pc prior to upgrading, then copy back after and the files can be copied to the folder visible to Windows.
Also, creating a symlink to /data/media/clockworkmod in /data/media/0/ will allow a user to get CWM to see backups and allow the user to have access to it in the folder visible to Windows.
Your solution ignores the fact the someone might prefer CWM over TWRP.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thx for the info, didn't know that.
Strange thing is that the guy i help out didn't went from 4.1.2 to 4.2.2
He went straight from 4.2.2 custom rom to 4.2.2 custom rom.
Also i don't ignore a possible desired user recovery choice.
Issue with the 0 folder came when cwm was flashed.
Butt will amend the line .
More info is also welcome...

V6-Maniac said:
Thx for the info, didn't know that.
Strange thing is that the guy i help out didn't went from 4.1.2 to 4.2.2
He went straight from 4.2.2 custom rom to 4.2.2 custom rom.
Also i don't ignore a possible desired user recovery choice.
Issue with the 0 folder came when cwm was flashed.
Butt will amend the line .
More info is also welcome...
Click to expand...
Click to collapse
Possible that he didn't format SD card prior to flashing the first 4.2.2 ROM and didn't notice the problem until he got to yours?
Sent from my HTC One using xda app-developers app

ilal2ielli said:
Possible that he didn't format SD card prior to flashing the first 4.2.2 ROM and didn't notice the problem until he got to yours?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
If you have formated your SD card (firmware update that took care of that for you) DO NOT DO THIS. apon reboot your system is no longer fucntioning and if oyu boot into recovery it does not see your SD card anymore. I had to adb sideload to get a rom back ot the phone. Not the OP fault but mine. Luckly i know how to recover just wanted to give warning to others

Bump!! I think this thread should be in the stickies @Red5 what do you think?
Sent from my HTC One using xda premium

This has only became evident to me today.
I was on stock 4.1.2 and flashed Viper Rom 4.2.2 and noticed I was missing 16GB storage.
In the thread I was told to look in data/media and all my files which I saved on SD Card from 4.1.2 were there. Also this 0 folder which had pretty much the same folders but with no user files
I was told to delete duplicate files/folders in the modia (not 0) folder but I dont know if i should just leave empty folders in Media with everything in 0, or delete all folders in Media and leaving only the 0 folder there with everything inside that intact.. If that makes sense..
I am unsure what will happen to CWM if I delete that from the Data/media folder
Cheers

twerg said:
This has only became evident to me today.
I was on stock 4.1.2 and flashed Viper Rom 4.2.2 and noticed I was missing 16GB storage.
In the thread I was told to look in data/media and all my files which I saved on SD Card from 4.1.2 were there. Also this 0 folder which had pretty much the same folders but with no user files
I was told to delete duplicate files/folders in the modia (not 0) folder but I dont know if i should just leave empty folders in Media with everything in 0, or delete all folders in Media and leaving only the 0 folder there with everything inside that intact.. If that makes sense..
I am unsure what will happen to CWM if I delete that from the Data/media folder
Cheers
Click to expand...
Click to collapse
Anything that's already in /data/media/0 can be deleted from /data/media
/data/media/legacy/, /data/media/obb/, and /data/media/clockworkmod can be left alone.
If you want to be able to see your clockworkmod folder and backups when connected to a PC/MAC you'll need to create a symlink in /data/media/0 pointing to the data/media/clockworkmod folder.
Sent from my HTC One using xda app-developers app

Super frustrating problem. I had this happen a couple weeks ago and it pissed me off. Wound up just formatting and it fixed it never to return
Sent from my HTC One using Tapatalk 2

InflatedTitan said:
Super frustrating problem. I had this happen a couple weeks ago and it pissed me off. Wound up just formatting and it fixed it never to return
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes very annoying.
Well i formatted and reset rom and now have no SD Card, directory or files om the phone.
A guy here on xda tried for almost 2 hours last night to fix it, can sideload a rom bit still no SD and rom will not boot.
Should never have rooted this phone, i was npt going to but of course i did amyway.

Tried this method on my nexus 10 (with the proper recovery but didn't work) sucks because i don't have links to my sd card and cant download anything as a result. flashing the google stock image didnt help either wondering if there was anything else i can do?

[HowTo] Fully restore to stock rom to fix some problem!

This thread will help anyone who want to restore the stock rom, it may fix many problem like application lost. In fact I happened to delete a file and my kindle fire hdx's wifi connection became very unstable, so I decide to restore it. Here is how, it's easy.
1. Edit your build.prop.
Edit every "310079820" to "310079819" (or lower). For me, I edited "ro.build.version.incremental", "ro.build.version.number", "ro.build.description" and "ro.build.fingerprint" section. Please be very careful!!!! If you are using Kindle Fire HDX 7'' (Both LTE or Wifi)(NOT FOR 8.9''!!!), you can use the View attachment build.prop.zip attached. (USE FOR YOUR OWN RISK!!!!)
{
"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. Reboot your Kindle
3. Open Settings-Device-System Updates, click "Check Now"
4. Download the rom.
5. Install update.
6.You're done! Enjoy!

scx110a said:
This thread will help anyone who want to restore the stock rom, it may fix many problem like application lost. In fact I happened to delete a file and my kindle fire hdx's wifi connection became very unstable, so I decide to restore it. Here is how, it's easy.
1. Edit your build.prop.
Edit every "310079820" to "310079819" (or lower). For me, I edited "ro.build.version.incremental", "ro.build.version.number", "ro.build.description" and "ro.build.fingerprint" section. Please be very careful!!!! If you are using Kindle Fire HDX 7'' (Both LTE or Wifi), you can use the View attachment 2472000 attached. (USE FOR YOUR OWN RISK!!!!)
View attachment 2471999
2. Reboot your Kindle
3. Open Settings-Device-System Updates, click "Check Now"
4. Download the rom.
View attachment 2472010
5. Install update.
View attachment 2472011
6.You're done! Enjoy!
View attachment 2472012
Click to expand...
Click to collapse
I can't root my kindle since i have canceled root on my kindle after i root it. My kindle have some problem, and i want to restore it, but i can't edit the build.prop. I have tried to edit the build.prop in the rom file, but it didn't work, what can I do? Thanks.

sdcardsd said:
I can't root my kindle since i have canceled root on my kindle after i root it. My kindle have some problem, and i want to restore it, but i can't edit the build.prop. I have tried to edit the build.prop in the rom file, but it didn't work, what can I do? Thanks.
Click to expand...
Click to collapse
The only way I know is root it again, and edit it, then update. After update, you will lose root access again.

Excellent.
Sent from my DROID RAZR HD using Tapatalk

WOW,Amazing!
Sent from my XT902 using Tapatalk

I did this and then also factory restored so it acted like it was brand new, but the google app icons were still there, just not working. How can I make it totally back to out of the box? The Amazon Appstore still wasn't working after resetting.

bricked...
copied build.prop to system using root explorer. rebooted and now its bricked... i can adb but thats about it... i can get into recovery but it just gives my option to reboot or system default. im afraid system default will kill it completely... anything i can do?

jeffsrawr said:
copied build.prop to system using root explorer. rebooted and now its bricked... i can adb but thats about it... i can get into recovery but it just gives my option to reboot or system default. im afraid system default will kill it completely... anything i can do?
Click to expand...
Click to collapse
Connect with adb and chmod 644 build.prop
Envoyé de mon GT-N7100 en utilisant Tapatalk

Cpasjuste said:
Connect with adb and chmod 644 build.prop
Click to expand...
Click to collapse
i typed
adb shell
it says [email protected]:/ $
i typed
chmod 644 /system/build.prop
and it just goes to next line with blinking cursor... what am i doing wrong?
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
C:\adbfiles>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
10|[email protected]:/ #
---------- Post added at 01:48 AM ---------- Previous post was at 01:38 AM ----------
got it thanks very much
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/build.prop
success!

jeffsrawr said:
i typed
adb shell
it says [email protected]:/ $
i typed
chmod 644 /system/build.prop
and it just goes to next line with blinking cursor... what am i doing wrong?
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
C:\adbfiles>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
10|[email protected]:/ #
---------- Post added at 01:48 AM ---------- Previous post was at 01:38 AM ----------
got it thanks very much
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/build.prop
success!
Click to expand...
Click to collapse
Glad to hear that

After I updated, I copy that rom file to computer, (the rom file's name : update-kindle-thor-13.3.1.0_user_310079820.bin)
and then i changed the name :update-kindle-thor-13.3.1.0_user_310079820.ZIP, install it to STOCK ROM, SUCCEEDED!
thanks.

nvm

Ads Return To Lockscreen
I have used this method twice to reset the OS build. I also did a factory reset once and the other time just installed the current build of the OS. However, what I have noticed is that the Amazon ads return although I have re-named the file to turn them off.
The lockscreen wallpaper at first showed a black screen, but this is only when the device goes into hibernation so to speak. You can see the navigation bar, but no image before you unlock the screen.
After sitting idle overnight, now instead of the screen being black, ads now show until I unlock the device and go into the home page. This happens when I also do a factory reset with this method. I've restored with and without a factory reset and both times the ads return.
When doing a manual reboot, the regular lock screen wallpaper will show before unlocking the device and going onto the home page. The ads are shown only when the device falls asleep or you just press the power button to wake it up.
I have changed the name of the file that would prevent the ads from showing, but it’s like something is over riding the change in file name.
Anyone else have this issue? Any suggestions?
I did find a post where the person suggested changing permissions on the file, but what happens there is that you get stuck with one lockscreen wallpaper (beige pencil and paper one), they stop rotating at that point.

ratbert90 said:
Here is a build.prop for the 8.9HDX.
Click to expand...
Click to collapse
I don't see a link to the file.
Have you tried it?

jeffsrawr said:
i typed
adb shell
it says [email protected]:/ $
i typed
chmod 644 /system/build.prop
and it just goes to next line with blinking cursor... what am i doing wrong?
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
C:\adbfiles>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
10|[email protected]:/ #
---------- Post added at 01:48 AM ---------- Previous post was at 01:38 AM ----------
got it thanks very much
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/build.prop
success!
Click to expand...
Click to collapse
How i can have adb access in a bricked KF HDX?
I need to install any thing?
I turn on the tablet and plug in with the usb but dont recognize the FK

[GUIDE][XSP]Easy init.d support for Stock ROMs

Easy init.d support for Stock ROMs
Disclaimer: Credits belong to original authors. I'm sharing this intending that others might benefit. This worked for me without problems, but I'm not responsible for any unwanted effects others might experience. Keep a CWM backup just in case.
What is this?
This is an easy method to add init.d support to our stock ROMs running on stock kernels. Then, scripts placed in /system/etc/init.d/ folder will be executed automatically at boot.
Requirements:
1.Rooted phone.
2.Root explorer or similar app.
3.Busybox installed.
check:
Type "busybox run-parts" (without quotes) in a terminal emulator and press enter. If you get an output similar to what's shown below you're all set. It means that busybox is installed and the command is present. (It's needed for the MOD).
Code:
1|[email protected]:/ $ busybox run-parts
BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
Usage: run-parts [-t] [-l] [-a ARG] [-u MASK] DIRECTORY
Run a bunch of scripts in DIRECTORY
-t Print what would be run, but don't actually run anything
-a ARG Pass ARG as argument for every program
-u MASK Set the umask to MASK before running every program
-l Print names of all matching files even if they are not executable
1|[email protected]:/ $
If busybox not installed, install it from Google play.
How to:
1) Open root explorer, go to /system/etc/ folder.
2) Mount /system as R/W by pressing the button at upper right corner.
3) Open init.qcom.post_boot.sh file for editing. (Long-press> Open in Text Editor)
4) Add this line to the bottom end of that file.
Code:
busybox run-parts /system/etc/init.d/
**Add an empty line after that. It's very important**​
{
"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"
}
5) Save the file. (You can delete the .bak file that Root explorer creates).
Then..
6) Create 'init.d' folder in /system/etc/ if not already present.
7) Change it's permissions to 755/rwxr-xr-x (Long-press> permissions)
That's it!
Testing:
To see whether it works, extract the test script (from attachment) to init.d folder, change script's permissions to 755/rwxr-xr-x and reboot the phone. You should see a file called Test.log in /data/ with a message saying that it's working.
(Tested on Android 4.3 (.201). Should work in others.)
How it works:
It's quite obvious. The init.qcom.post_boot.sh is one of the scripts that runs at boot, which in turn executes the busybox command to execute the scripts in init.d folder. Simple!
Credits & Sources
1) @iridaki and original thread here.
2) @smokin1337 and original thread here.
Note: Following the first tutorial broke my root. Second method executed only the first script in the list. So, I combined the needed parts of two guides!
Alternative methods:
#'Universal init.d' app from Google play would also execute init.d scripts, but at the app level.
#'SManager' is another app that can execute scripts at boot.
There maybe other methods...
You may point out any shortcomings/improvements.
Thanks and Regards!

mrhnet said:
Easy init.d support for Stock ROMs
Disclaimer: Credits belong to original authors. I'm sharing this intending that others might benefit. This worked for me without problems, but I'm not responsible for any unwanted effects others might experience. Keep a CWM backup just in case.
What is this?
This is an easy method to add init.d support to our stock ROMs running on stock kernels. Then, scripts placed in /system/etc/init.d/ folder will be executed automatically at boot.
Requirements:
1.Rooted phone.
2.Root explorer or similar app.
3.Busybox installed.
check:
Type "busybox run-parts" (without quotes) in a terminal emulator and press enter. If you get an output similar to what's shown below you're all set. It means that busybox is installed and the command is present. (It's needed for the MOD).
Code:
1|[email protected]:/ $ busybox run-parts
BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
Usage: run-parts [-t] [-l] [-a ARG] [-u MASK] DIRECTORY
Run a bunch of scripts in DIRECTORY
-t Print what would be run, but don't actually run anything
-a ARG Pass ARG as argument for every program
-u MASK Set the umask to MASK before running every program
-l Print names of all matching files even if they are not executable
1|[email protected]:/ $
If busybox not installed, install it from Google play.
How to:
1) Open root explorer, go to /system/etc/ folder.
2) Mount /system as R/W by pressing the button at upper right corner.
3) Open init.qcom.post_boot.sh file for editing. (Long-press> Open in Text Editor)
4) Add this line to the bottom end of that file.
Code:
busybox run-parts /system/etc/init.d/
**Add an empty line after that. It's very important**​
5) Save the file. (You can delete the .bak file that Root explorer creates).
Then..
6) Create 'init.d' folder in /system/etc/ if not already present.
7) Change it's permissions to 755/rwxr-xr-x (Long-press> permissions)
That's it!
Testing:
To see whether it works, extract the test script (from attachment) to init.d folder, change script's permissions to 755/rwxr-xr-x and reboot the phone. You should see a file called Test.log in /data/ with a message saying that it's working.
(Tested on Android 4.3 (.201). Should work in others.)
How it works:
It's quite obvious. The init.qcom.post_boot.sh is one of the scripts that runs at boot, which in turn executes the busybox command to execute the scripts in init.d folder. Simple!
Credits & Sources
1) @iridaki and original thread here.
2) @smokin1337 and original thread here.
Note: Following the first tutorial broke my root. Second method executed only the first script in the list. So, I combined the needed parts of two guides!
Alternative methods:
#'Universal init.d' app from Google play would also execute init.d scripts, but at the app level.
#'SManager' is another app that can execute scripts at boot.
There maybe other methods...
You may point out any shortcomings/improvements.
Thanks and Regards!
Click to expand...
Click to collapse
Will try thanks!!

I doesnt have the init.qcom file
Just have a init.goldfish and the init.d folder, but is always empty...
Help please...

janolucero said:
I doesnt have the init.qcom file
Just have a init.goldfish and the init.d folder, but is always empty...
Help please...
Click to expand...
Click to collapse
Do you have any other file with "post_boot" part, in system/etc/ folder? What's your ROM?

mrhnet said:
Do you have any other file with "post_boot" part, in system/etc/ folder? What's your ROM?
Click to expand...
Click to collapse
.254
i will try to reflash and start fresh.-

janolucero said:
.254
i will try to reflash and start fresh.-
Click to expand...
Click to collapse
I haven't tested it on 4.1.2. You may list what are the files in /system/etc folder..
(Just do this command in a terminal emulator, it will save the filelist to a file in sdcard. Post that file here.)
Code:
ls /system/etc/ >> /sdcard/filelist.txt

mrhnet said:
I haven't tested it on 4.1.2. You may list what are the files in /system/etc folder..
(Just do this command in a terminal emulator, it will save the filelist to a file in sdcard. Post that file here.)
Code:
ls /system/etc/ >> /sdcard/filelist.txt
Click to expand...
Click to collapse
Y not add the runparts command in install-recovery.sh file?
Sent from my C5303 using Tapatalk

Siddhesh said:
Y not add the runparts command in install-recovery.sh file?
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Yes, was thinking like that. Wanted to know whether any other post_boot script is there in 4.1.2

mrhnet said:
Yes, was thinking like that. Wanted to know whether any other post_boot script is there in 4.1.2
Click to expand...
Click to collapse
No needed if everyone uses supersu then there will be a file called install-recovery.sh but don't add runparts command in it make another file named install-recovery-2.sh(Only for supersu users) and add the runparts command. Our init.rc makes install-recovery.sh to start on boot
Sent from my C5303 using Tapatalk

Thanks for the tip. Adding runparts to the second file would prevent breaking init.d even if SuperSU update is flashed again. Good idea!

mrhnet said:
Thanks for the tip. Adding runparts to the second file would prevent breaking init.d even if SuperSU update is flashed again. Good idea!
Click to expand...
Click to collapse
Yes but its only for SuperSU users if someone using Superuser from koush then this trick will not work so u have to edit the original install-recovery.sh in that situation and please test this trick coz on my previous Xperia phones Wt19i and arcs only first script is executed never used scripts on XSP
Sent from my C5303 using Tapatalk

Siddhesh said:
Yes but its only for SuperSU users if someone using Superuser from koush then this trick will not work so u have to edit the original install-recovery.sh in that situation and please test this trick coz on my previous Xperia phones Wt19i and arcs only first script is executed never used scripts on XSP
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
This the situation. Xperia Arc on C-rom KK ver 5.6 with nAa ver 3.4...
There is already a init.d file in system/etc.
Upon viewing the file install-recovery.sh there is a directive to create another install-recovery.2sh - i.e. as pix below:
Using SuperSU ver 1.94
So I will try this and report.
Sent from my Xperia Arc using XDA Free mobile app

Thanks for the post.. I'm going to try your method for adding init.d support but I have a question :
I found the "init.qcom.post_boot.sh" script in the root directory not "system/etc" nor "system/" is that an issue? should I edit it with no concerns? or should i edit the "install-recovery.sh" found in "system/etc/" ?
my device is HTC desire 816 with stock rom, rooted & with unlocked bootloader

Siddhesh said:
No needed if everyone uses supersu then there will be a file called install-recovery.sh but don't add runparts command in it make another file named install-recovery-2.sh(Only for supersu users) and add the runparts command. Our init.rc makes install-recovery.sh to start on boot
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Where to add the runparts command?
the other sh script is not running

In grand prime SM-G530FZ ( 5.0.2 ), This file exists ( i.e, qcom.....)
Did the mentioned steps. But not working

[GUIDE] CWM & Root Lenovo Yoga 2 (8/10/13)

Temp CWM-recovery​
1. Download and put the UPDATE-SuperSU-vX.Xx.zip on internal/external SdCard
2. Download, extract the folder IntelAndroid-FBRL and put on the C drive
3. Follow this guide (Use the option T3)
This is new version fixed by social-design-concepts (Please support its work with donations)
Now backup kernel with recovery too:
View attachment IntelAndroid-FBRL-01-17-2015.7z
Root, backup & restore on the external card works well:
{
"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"
}

bodivas said:
Temp CWM-recovery​
1. Download and put the UPDATE-SuperSU-vX.Xx.zip on internal/external SdCard
2. Download, extract the folder IntelAndroid-FBRL and put on the C drive (do not use other versions)
3. Follow this guide (Use the option T3)
View attachment 3107550
Backup & restore on the external card works well
Click to expand...
Click to collapse
Maybe I could get you to send dumps of this device it be nice to get to the bottom of why the the updated version doesn't work on this device.
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
why the the updated version doesn't work on this device.
Click to expand...
Click to collapse
Perhaps because the new version lacks the table mount points in recovery.zip/etc:
View attachment fstab.rar
Thanks for the great work!! 2P810+++++79361W

bodivas said:
Perhaps because the new version lacks the table mount points in recovery.zip/etc:
View attachment 3107582
Thanks for the great work!!
Click to expand...
Click to collapse
Give me moment I like to get the dump of fastboot.img recovery.fstab should be generated from the fstab droidboot / fastboot uses to handle partitions I'm making changes to the recovery.fstab generation so like to include fixes for this if their using other name or something.
If you could this should dump boot recovery fastboot and system
https://www.androidfilehost.com/?fid=95887005526788692
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
If you could this should dump boot recovery fastboot and system
https://www.androidfilehost.com/?fid=95887005526788692
Click to expand...
Click to collapse
I saw that when starting new version generates mount point right (mmcblk1p1) but fails to mount internal sd card the same. I added recovery.fstab in recovery.zip/etc and your new version 12-29-2014 works without problems!
All versions of yoga 2 (8,10,13) there year numbers and partitions sizes equal ..
For the kernel, recovery and fastboot, I had to use:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/droidboot.img
Download dump_yoga2_830L
This is full stock firmware

Can we use this to dual boot with Yoga 2 tablet with Windows?

bodivas said:
I saw that when starting new version generates mount point right (mmcblk1p1) but fails to mount internal sd card the same. I added recovery.fstab in recovery.zip/etc and your new version 12-29-2014 works without problems!
All versions of yoga 2 (8,10,13) there year numbers and partitions sizes equal ..
For the kernel, recovery and fastboot, I had to use:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/droidboot.img
View attachment 3107675
Download dump_yoga2_830L
This is full stock firmware
Click to expand...
Click to collapse
Thanks I'll download and see if i can resolve the issue
Sent from my XT907 using XDA Free mobile app

redhern said:
Can we use this to dual boot with Yoga 2 tablet with Windows?
Click to expand...
Click to collapse
First you have to have the dump of bios..

Is the bios available? I havent seen it mentioned in any of the posts.

redhern said:
Is the bios available? I havent seen it mentioned in any of the posts.
Click to expand...
Click to collapse
BIOS is present here but you have to know where to put. And then the windows do not care so much - I want CMmod
Here the guide for ONDA V975i
I do not want to risk (I've already lost imei on my 830L) with these experiments

successfully rooted but... no adb root nor adb remount
Hello,
I successfully rooted my 1050F device following this guide
Now I'd like to run adb as root and to be able to remount rw /system to put and remove staff there but the usual method don't work.
I tried adb root and adb remount but lenovo adb cannot run as root in production build.
I tried installing adb-insecure 2.0 which usually do the trick but when I patch the kernel from the app and use adb insecure demon the device is not seen by the PC with adb .
I also tried to remount with "sudo mount -o remount rw /system" but I cannot write in the /system partition
any suggestion?
thanks,
Dario

blackdir said:
Hello,
I successfully rooted my 1050F device following this guide
Now I'd like to run adb as root and to be able to remount rw /system to put and remove staff there but the usual method don't work.
I tried adb root and adb remount but lenovo adb cannot run as root in production build.
I tried installing adb-insecure 2.0 which usually do the trick but when I patch the kernel from the app and use adb insecure demon the device is not seen by the PC with adb .
I also tried to remount with "sudo mount -o remount rw /system" but I cannot write in the /system partition
any suggestion?
thanks,
Dario
Click to expand...
Click to collapse
adb shell
su
mount -o rw,remount /system

vampirefo said:
adb shell
su
mount -o rw,remount /system
Click to expand...
Click to collapse
sure, that will work, but if you need to push several files it is very tim consuming as you need to copy to a temporary location on the device and then move them to /system
if you are able to get adb insecure you can create a batch file that you can run from the PC
Any idea about the reason why dab insecure is not working on this device?
Is it because the device is intel based and not Arm?
(if this is a stupid question, please forgive me as it is my first experience on Android Intel development)

blackdir said:
sure, that will work, but if you need to push several files it is very tim consuming as you need to copy to a temporary location on the device and then move them to /system
if you are able to get adb insecure you can create a batch file that you can run from the PC
Any idea about the reason why dab insecure is not working on this device?
Is it because the device is intel based and not Arm?
(if this is a stupid question, please forgive me as it is my first experience on Android Intel development)
Click to expand...
Click to collapse
Correct you need a adbd binary for intel fully rooted meaning its always root, or you need to have an unlocked bootloader, that allows flashing of modified boot.img.

I updated the system via OTA and root again but it said Failed: too many links or something like that but it continued and cwm is installed. Is this ok?

redhern said:
Is the bios available? I havent seen it mentioned in any of the posts.
Click to expand...
Click to collapse
Have you tried flashing the bios yet or did you find any other ways to run windows on this tablet?

bodivas said:
BIOS is present here but you have to know where to put. And then the windows do not care so much - I want CMmod
Here the guide for ONDA V975i
I do not want to risk (I've already lost imei on my 830L) with these experiments
Click to expand...
Click to collapse
bodivas, could you post a guide on how to install windows on external sd card? The guide you posted when translated to english it is very hard to understand, and the onda is built on a different chipset, slower ones, so we would need to find intel baytrail drivers for it to work right. Also would the bios for the 1050 work on the 1350?

Rooted my Yoga 2 10" with the Jan. 10 OTA update installed, worked like a charm and the next best thing to a one-click root for noobs like me!
Thanks!

Here the same. 1380F with last OTA and root is rock solid [emoji106]

I have a problem
After I root my YT2-1050f, I can't enter recovery mode.