Ok here's the deal, I left charging my phone in the night and in the morning nothing, don't turn on, no lights in charger, nothing... So I connected to PC and a hardware disconnecting connecting sound plays avery 5sec, no key combination work, only if i press power and connect to pc detects it in qualcomm download mode, so i tried to unbrick it with jet toolkit and i only get QDS reset, no more, i can't detect emmc partitions too, what i can do?
Enviado desde mi HTC One S usando Tapatalk 4
Jtagg service if you've really spammed the command for partition enumeration and are sure they won't come up.
Sent from my HTC One XL using xda app-developers app
exad said:
Jtagg service if you've really spammed the command for partition enumeration and are sure they won't come up.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I will try spam a little more lol, but just in case, here in Texas (El Paso) there's a dev doing this job?
Zero_Lord said:
I will try spam a little more lol, but just in case, here in Texas (El Paso) there's a dev doing this job?
Click to expand...
Click to collapse
mobiletechvideos.com is located in Bryan, Texas. My phone was hard bricked and couldn't enumerate the partitions, and he fixed it real quick, and no signs of opening the device.
Vcek said:
mobiletechvideos.com is located in Bryan, Texas. My phone was hard bricked and couldn't enumerate the partitions, and he fixed it real quick, and no signs of opening the device.
Click to expand...
Click to collapse
That's good I will send it to him then. it cost 50 bucks + shipping right? or his website is outdated?
Zero_Lord said:
That's good I will send it to him then. it cost 50 bucks + shipping right? or his website is outdated?
Click to expand...
Click to collapse
No it's upto date, and yes it will cost you 50 + shipping
Sent from my HTC One XL using XDA Premium 4 mobile app
You can try to hold down on the power button for ten seconds. Try that a couple times before jtagg. Mine will randomly shut off and this has brought it back for me.
Sent from my HTC One XL using XDA Premium 4 mobile app
Still making a last push before send it to JTAG, I spammed for 5 minutes from the JET Toolkit
Code:
sudo ./emmc_recover -r
And i get this
Code:
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
already see in the device manager with the cmd watch lsusb and the device changes in Qualcomm inc. to Qualcomm, Inc. Gobi Wireless Modem (QDL mode) and the device number change every time (from device 6 to 45 consecutively) already check the cmd
Code:
sudo ./jet -u
and i get this cmd
Code:
[email protected]:~/Downloads/jet$ sudo ./jet -u
JET - Jewel/Evita Toolkit v0.3.3beta
**Unbrick Mode**
Device detection started...
Waking Device...
Timeout. Retrying...
Timeout. Retrying...
Timeout. Retrying...
Cannot find emmc partitons. Exiting...
So the problem maybe can be EMMC corrupted?
Zero_Lord said:
Still making a last push before send it to JTAG, I spammed for 5 minutes from the JET Toolkit
Code:
sudo ./emmc_recover -r
And i get this
Code:
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
[email protected]:~/Downloads/jet$ sudo ./emmc_recover -r
================= emmc_recover 0.3 alpha 2 ==========================
Cannot reset device
already see in the device manager with the cmd watch lsusb and the device changes in Qualcomm inc. to Qualcomm, Inc. Gobi Wireless Modem (QDL mode) and the device number change every time (from device 6 to 45 consecutively) already check the cmd
Code:
sudo ./jet -u
and i get this cmd
Code:
[email protected]:~/Downloads/jet$ sudo ./jet -u
JET - Jewel/Evita Toolkit v0.3.3beta
**Unbrick Mode**
Device detection started...
Waking Device...
Timeout. Retrying...
Timeout. Retrying...
Timeout. Retrying...
Cannot find emmc partitons. Exiting...
So the problem maybe can be EMMC corrupted?
Click to expand...
Click to collapse
Try using unbrick rather than jet. Not sure if they do the same thing but with unbrick you'll be able to see if the partitions enumerate.
http://forum.xda-developers.com/showthread.php?t=1966850
exad said:
Try using unbrick rather than jet. Not sure if they do the same thing but with unbrick you'll be able to see if the partitions enumerate.
http://forum.xda-developers.com/showthread.php?t=1966850
Click to expand...
Click to collapse
Thanks I will give a try, last night searching about 2 hours in the jet thread and in google I didnt get to this thread.
Zero_Lord said:
Thanks I will give a try, last night searching about 2 hours in the jet thread and in google I didnt get to this thread.
Click to expand...
Click to collapse
Sorry to hear you wasted so much time! If you have any questions, don't hesitate to ask, I'm usually pretty quick about responding.
exad said:
Sorry to hear you wasted so much time! If you have any questions, don't hesitate to ask, I'm usually pretty quick about responding.
Click to expand...
Click to collapse
Well I have a question, in the thread says
You should go from seeing this..
to seeing this...
Click to expand...
Click to collapse
and no image lol, i searched in code page and the dropbox image says 404 not found, so im searching in google for other image because I cant continue if i dont know what im going to see lol.
UPDATE, i show this image, this what i get
{
"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"
}
http://kn3.net/3551F641552PNG.html
Zero_Lord said:
Well I have a question, in the thread says
and no image lol, i searched in code page and the dropbox image says 404 not found, so im searching in google for other image because I cant continue if i dont know what im going to see lol.
Click to expand...
Click to collapse
Ah right, I'm at work so I can't create a picture for you BUT I can give you an idea of what you'll see.
So when you spam the command. If will at first show something like:
sda1 sdb1 sbd2 sbc1 sde1 sdf1
You'll see something like 10 of them but when your partitions enumerate properly one of the letters will show a bunch of extra partitions.. so you'll have for example:
sda1 sdb1 sbd2 sbc1 sde1 sde2 sde3 sde4 sde5 sde6 sde7
sde8 sde9 sde10 sde11 sde12 sde13 sde14 sde15 sde16 sdf1
And the letter that shows all the numbered partitions will be your phone's emmc partition table.
Sort of making sence?
In linux sda1 sda2 is similar to windows lettering driver a, b, c but in linux sda1 sda2 sda3 will be one hard drive and if you have another physical hard drive it will then become sdb and every partiton will be a number so:
Drive 1 with 2 partitions will = sda1 sda2
Drive 2 with 4 partitions will = sdb1 sdb2 sdb3 sdb4
So the point is to list off all the partitions within your phones emmc "drive". If they don't enumerate, there's no way to write to them and recover from the brick.
*edit* so in accordance with your picture, if you successfully enumerate one of those sd*(a,b,c,d,h,whatever) will list a BUNCH of numbered partitions. Try a afew times because it's hard to catch it.
exad said:
Ah right, I'm at work so I can't create a picture for you BUT I can give you an idea of what you'll see.
So when you spam the command. If will at first show something like:
sda1 sdb1 sbd2 sbc1 sde1 sdf1
You'll see something like 10 of them but when your partitions enumerate properly one of the letters will show a bunch of extra partitions.. so you'll have for example:
sda1 sdb1 sbd2 sbc1 sde1 sde2 sde3 sde4 sde5 sde6 sde7
sde8 sde9 sde10 sde11 sde12 sde13 sde14 sde15 sde16 sdf1
And the letter that shows all the numbered partitions will be your phone's emmc partition table.
Sort of making sence?
In linux sda1 sda2 is similar to windows lettering driver a, b, c but in linux sda1 sda2 sda3 will be one hard drive and if you have another physical hard drive it will then become sdb and every partiton will be a number so:
Drive 1 with 2 partitions will = sda1 sda2
Drive 2 with 4 partitions will = sdb1 sdb2 sdb3 sdb4
So the point is to list off all the partitions within your phones emmc "drive". If they don't enumerate, there's no way to write to them and recover from the brick.
*edit* so in accordance with your picture, if you successfully enumerate one of those sd*(a,b,c,d,h,whatever) will list a BUNCH of numbered partitions. Try a afew times because it's hard to catch it.
Click to expand...
Click to collapse
Ok, i understand, but i keep spaming the cmd I still get nothing, the lusb cmd shows Qualcomm inc connecting and disconnecting about 30 times, and then disappears, i reconnect it and i get Qualcomm Inc. and about 3 to 9 times same connecting and disconnecting, and then Qualcomm Download bla bla driver, this shows the spam
Code:
/dev/sdb2
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*2
/dev/sdb2
[email protected]:~$
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
[email protected]:~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc /dev/sdc1
If they don't show up, it cannot be recovered. Jtagg or motherboard replacement are the only options
Sent from my HTC One XL using xda app-developers app
exad said:
If they don't show up, it cannot be recovered. Jtagg or motherboard replacement are the only options
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Well, thats shame.
Enviado desde mi HTC One S usando Tapatalk 4
Related
From a telnet session
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev futexfs
nodev tmpfs
nodev inotifyfs
nodev devpts
cramfs
nodev ramfs
vfat
yaffs
yaffs2
Click to expand...
Click to collapse
# cd bin
# ls
start
ioctl
smd
insmod
sleep
iftop
setprop
ifconfig
setconsole
id
sendevent
hd
schedtop
getprop
route
getevent
rmmod
dmesg
rmdir
df
rm
wpa_supplicant
wpa_cli
dd
wlan_loader
toolbox
telnetd
system_server
svc
surfaceflinger
renice
su
ssltest
sh
servicemanager
date
service
sdutil
sdptool
rild
radiooptions
qemud
reboot
pm
playmp3
ping
netcfg
cmp
mountd
monkey
mediaserver
logwrapper
logcat
linker
ps
itr
installd
input
htclogkernel
chmod
hostapd_cli
hostapd
hcid
hciattach
flash_image
fillup
printenv
dvz
dumpsys
dumpstate
dhcpcd
cat
dexopt
debuggerd
debug_tool
dbus-daemon
dalvikvm
app_process
notify
am
akmd
dumpcrash
netstat
mv
mount
wipe
mkdosfs
watchprops
mkdir
vmstat
lsmod
umount
ls
top
log
sync
ln
stop
kill
Click to expand...
Click to collapse
So from my understanding I can only mount sdcards with fat32, fat16, fat12 or yaffs2. Only formatting of fat is supported as well. cramfs doesn't seem that interesting as it is read-only. yaffs2 is made for NAND and I don't know how similar it is to SD-cards. I formatted my card with ext3 before I saw this info and it didn't work. I'm using fat32 for now, but as a (almost) linux purist and the limitations of file size and names I'm interested in using something else.
The Kaiser, Vogue and Freerunner can use both ext2 and ext3 because of a custom kernel. Is that the only way?
There was someone in #android on Freenode that got a 4 GB partition in ext2 to work.
[email protected]:~/logs$ cat freenode_#android.log | grep "ext2"
[Mon Dec 1 2008] [00:11:55] <sparkle> i just cheat and have a 4gb ext2 partition, but that's not really an option for any app you want to ship to the masses
Click to expand...
Click to collapse
Try asking him.
(S)he has loaded the ext2 module. This can be done with root access, but all those without are out of luck (for now anyways )
Hello everyone, first time poster but longer time lurker
Last week I treated myself with the new NotePro 12.2 tablet after dreaming what might cn be done with it once it runs a complete desktop :fingers-crossed:
Since last saturday I have been trying to no availe to get ubuntu running and about to go crazy with the amount of failed attempts.
My hopes are on the Complete Linux Installer as it is being actively developed but I ran into a weird issue with permissions when running the boot script.
I would post in the developer thread, but as a new user I will have to do it here (original thread http://forum.xda-developers.com/showthread.php?t=1585009 )
On with the info:
{
"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"
}
Device: Galaxy NotePro 12.2 (SM-P900)
Android 4.4.2
Kernel: 3.4.39-433754
Rooted
SuperSu Pro: passed root
Busybox Pro: passed root
Complete Linux Installer + key (ofcourse!)
Linux version: Ubuntu 13.10 Large
The issue:
When executing the bootscript.sh the error "operation is not permitted"
Code:
Checking loop device... MISSING
Creating loop device... mknod: /dev/block/loop255: Operation not permitted
Command: /system/xbin/busybox mknod /dev/block/loop255 b 7 255
FAILED
Error: Unable to create loop device!
Doing my homework for few hours and seeing more people have had this problem, but after some head scratching I simply tried the command manually to see if I am going crazy or not:
Code:
/system/xbin/busybox mknod /dev/block/loop255 b 7 255
v/block/ |grep loop <
brw------- root root 7, 0 2014-04-02 19:20 loop0
brw------- root root 7, 1 2014-04-02 19:20 loop1
brw------- root root 7, 2 2014-04-02 19:20 loop2
brw------- root root 7, 255 2014-04-02 19:59 loop255
brw------- root root 7, 3 2014-04-02 19:24 loop3
brw------- root root 7, 4 2014-04-02 19:20 loop4
brw------- root root 7, 5 2014-04-02 19:20 loop5
brw------- root root 7, 6 2014-04-02 19:20 loop6
brw------- root root 7, 7 2014-04-02 19:20 loop7
Success! :victory:
Launch the app for a retry:
Code:
Checking loop device... FOUND
Command: /system/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
So I keep getting permission denied error one after the other, but when I execute the commands directly in the terminal it`s all fine and dandy and the only thing that doesn`t show anything is when I try to chroot.
With a little bit of linux knowledge I dived into the bootscript and started to look where something goes wrong, I even downloaded 2 different scripts but none made a difference.
Code:
Checking loop device... FOUND
Command: /system/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Command: /system/xbin/busybox mount -t ext4 /dev/block/loop255 /data/local/mnt
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or directory
Command: /system/xbin/busybox mount -t devpts devpts /data/local/mnt/dev/pts
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
Command: /system/xbin/busybox mount -t proc proc /data/local/mnt/proc
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Command: /system/xbin/busybox mount -t sysfs sysfs /data/local/mnt/sys
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
Command: /system/xbin/busybox mount -o bind /sdcard /data/local/mnt/sdcard
mkdir failed for /data/local/mnt/root/cfg, No such file or directory
mount: mounting /sdcard/ubuntu on /data/local/mnt/root/cfg failed: No such file or directory
Command: /system/xbin/busybox mount -o bind /sdcard/ubuntu /data/local/mnt/root/cfg
mount: mounting /sys/fs/selinux on /data/local/mnt/selinux failed: No such file or directory
Command: /system/xbin/busybox mount -o bind /sys/fs/selinux /data/local/mnt/selinux
mount: mounting /storage on /data/local/mnt/external_sd failed: No such file or directory
No user defined mount points
net.ipv4.ip_forward = 1
bootscript.sh[234]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
Error: Unable to write resolv.conf file!
Having all commands echo`d in the terminal made the manual work abit easier:
Code:
/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img <
xbin/busybox mount -t ext4 /dev/block/loop255 /data/local/mnt <
/xbin/busybox mount -t devpts devpts /data/local/mnt/dev/pts <
xbin/busybox mount -t proc proc /data/local/mnt/proc <
xbin/busybox mount -t sysfs sysfs /data/local/mnt/sys <
xbin/busybox mount -o bind /sdcard /data/local/mnt/sdcard <
xbin/busybox mount -o bind /sdcard/ubuntu /data/local/mnt/root/cfg <
xbin/busybox mount -o bind /sys/fs/selinux /data/local/mnt/selinux <
meserver 8.8.4.4" >> $mnt/etc/resolv.conf <
tmp-mksh: can't create /etc/resolv.conf: Read-only file system
27.0.0.1 localhost" > $mnt/etc/hosts <
tmp-mksh: can't create /etc/hosts: Read-only file system
Code:
ls -la /data/local/mnt/
al/mnt/ <
drwxr-xr-x root root 2013-10-09 12:19 android
drwxr-xr-x root root 2013-10-23 04:45 bin
drwxr-xr-x root root 2013-04-25 18:08 boot
drwxr-xr-x root root 2013-10-09 12:01 dev
drwxr-xr-x root root 2013-10-23 04:46 etc
drwxr-xr-x root root 2013-10-10 14:03 external_sd
drwxr-xr-x root root 2013-10-09 12:18 home
drwxr-xr-x root root 2013-10-10 18:35 lib
drwx------ root root 2013-10-09 11:51 lost+found
drwxr-xr-x root root 2013-10-09 11:54 media
drwxr-xr-x root root 2013-04-25 18:08 mnt
drwxr-xr-x root root 2013-10-09 11:54 opt
dr-xr-xr-x root root 1970-01-01 01:00 proc
drwx------ root root 2013-10-23 04:55 root
drwxr-xr-x root root 2013-10-23 04:55 run
drwxr-xr-x root root 2013-10-23 04:45 sbin
drwxrwx--x root sdcard_r 2014-04-01 19:49 sdcard
drwxr-xr-x root root 1970-01-01 01:00 selinux
drwxr-xr-x root root 2013-10-09 11:54 srv
dr-xr-xr-x root root 2014-04-02 19:20 sys
drwxrwxrwt root root 2013-10-23 04:55 tmp
drwxr-xr-x root root 2013-10-09 11:54 usr
drwxr-xr-x root root 2013-10-09 11:54 var
Looks very familiar :fingers-crossed:
Code:
Checking loop device... FOUND
Command: /system/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Command: /system/xbin/busybox mount -t ext4 /dev/block/loop255 /data/local/mnt
mount: mounting devpts on /data/local/mnt/dev/pts failed: Permission denied
Command: /system/xbin/busybox mount -t devpts devpts /data/local/mnt/dev/pts
mount: mounting proc on /data/local/mnt/proc failed: Permission denied
Command: /system/xbin/busybox mount -t proc proc /data/local/mnt/proc
mount: mounting sysfs on /data/local/mnt/sys failed: Permission denied
Command: /system/xbin/busybox mount -t sysfs sysfs /data/local/mnt/sys
mount: mounting /sdcard on /data/local/mnt/sdcard failed: Permission denied
Command: /system/xbin/busybox mount -o bind /sdcard /data/local/mnt/sdcard
mount: mounting /sdcard/ubuntu on /data/local/mnt/root/cfg failed: Permission denied
Command: /system/xbin/busybox mount -o bind /sdcard/ubuntu /data/local/mnt/root/cfg
mount: mounting /sys/fs/selinux on /data/local/mnt/selinux failed: Permission denied
Command: /system/xbin/busybox mount -o bind /sys/fs/selinux /data/local/mnt/selinux
mount: mounting /storage on /data/local/mnt/external_sd failed: Permission denied
No user defined mount points
net.ipv4.ip_forward = 1
bootscript.sh[231]: can't create /data/local/mnt/etc/resolv.conf: Permission denied
bootscript.sh[232]: can't create /data/local/mnt/etc/hosts: Permission denied
chroot: can't change root directory to '/data/local/mnt': Operation not permitted
Command: /system/xbin/busybox chroot /data/local/mnt /root/init.sh ubuntu.img
Shutting down Linux ARM
umount: can't umount /data/local/mnt/root/cfg: Permission denied
umount: can't umount /data/local/mnt/sdcard: Permission denied
umount: can't umount /data/local/mnt/external_sd: Invalid argument
umount: can't umount /data/local/mnt/dev/pts: Permission denied
umount: can't umount /data/local/mnt/dev: Invalid argument
umount: can't umount /data/local/mnt/proc: Permission denied
umount: can't umount /data/local/mnt/sys: Permission denied
umount: can't umount /data/local/mnt/selinux: Permission denied
umount: can't umount /data/local/mnt: Permission denied
Still nothing and now it goes on to the shutdown section
Doing the chroot command does nothing and to be honest, I wouldn`t even know if it was supposed to do anything as this function is new for me.
Code:
/system/xbin/busybox chroot /data/local/mnt /root/init.sh ubuntu.img
All the commands work with just being root (command su) or through busybox.
All the files have root owner/group and they are executable.
Debug so far:
Rename supplied busybox version to busybox.org => removed it entirely with a fixed link to busybox itself.
3 different bootscript.sh
Changed ext2 to ext4, latest was ext4.
Reinstalled, rebooted, kicked it a few times.
Checked perms on everything and it *looks* all good.
All commands the bootscript.sh tries to call do work when doing it manually in the command shell, but even "sh bootscript.sh" fails on all.
Changed "setenforce 0" as some one has suggested.
Here is my butcherd bootscript.sh script that I try to run it with:
Code:
###########################################
# Linux boot script V8 for Android v4.3 #
# Built by Zachary Powell (zacthespack) #
# and Martin M..ller (Tuxling) #
# Thanks to: #
# Johan Vromans #
# Marshall Levin #
# Vaykadji #
# and to everyone at XDA! #
# Feel free to edit/use this script as you#
# like but credit Linuxonandroid.org #
###########################################
# $ver: V8 #
###########################################
###########################################
# This is a function we use to stop the #
# script in case of errors #
###########################################
error_exit() {
echo "Error: $1"
exit 1
}
###########################################
# Set up variables #
###########################################
export bbox=/system/xbin/busybox
# echo $bbox
export usermounts=android # Base folder all user mounts are done in, should be moved to app later
export imgfile=/sdcard/ubuntu/ubuntu.img # Default image file, another can be set by using an argument
export bin=/system/xbin9
export mnt=/data/local/mnt
export USER=root
if [[ ! -d $mnt ]]; then mkdir $mnt; fi
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/root
###########################################
# Handle arguments if present #
###########################################
if [ $# -ne 0 ]; then
if [ -f $1 ]; then # Is full path present?
imgfile=$1
elif [ -f $(dirname $0)/$1 ]; then # Is only a filename present?
imgfile=$(dirname $0)/$1
else
error_exit "Image file not found!($1)"
fi
fi
###########################################
# If a md5 file is found we check it here #
###########################################
#if [ -f $imgfile.md5 ]; then
# echo "MD5 file found, use to check .img file? (y/n)"
# read answer
# if [ $answer == y ]; then
# echo -n "Validating image checksum... "
# $bbox md5sum -c -s $imgfile.md5
# if [ $? -ne 0 ];then
# echo "FAILED!"
# error_exit "Checksum failed! The image is corrupted!"
# else
# echo "OK"
# rm $imgfile.md5
# fi
# fi
#
#fi
################################
# Find and read config file #
# or use defaults if not found #
################################
use_swap=no
cfgfile=$imgfile.config # Default config file if not specified
if [ -f $imgfile.config ]; then
source $imgfile.config
fi
###########################################
# Set Swap up if wanted #
# #
###########################################
if [ $use_swap == yes ]; then
if [ -f $imgfile.swap ]; then
echo "Swap file found, using file"
echo "Turning on swap (if it errors here you do not have swap support"
swapon $imgfile.swap
else
echo "Creating Swap file"
dd if=/dev/zero of=$imgfile.swap bs=1048576 count=1024
mkswap $imgfile.swap
echo "Turning on swap (if it errors here you do not have swap support"
swapon $imgfile.swap
fi
fi
###########################################
# Set up loop device and mount image #
###########################################
echo -n "Checking loop device... "
if [ -b /dev/block/loop255 ]; then
echo "FOUND"
else
echo "MISSING"
# Loop device not found so we create it and verify it was actually created
echo -n "Creating loop device... "
$bbox mknod /dev/block/loop255 b 7 255
echo -n "Command: $bbox mknod /dev/block/loop255 b 7 255 \n"
if [ -b /dev/block/loop255 ]; then
echo "OK"
else
echo "FAILED"
error_exit "Unable to create loop device!"
fi
fi
$bbox losetup /dev/block/loop255 $imgfile
echo -n "Command: $bbox losetup /dev/block/loop255 $imgfile \n"
if [ $? -ne 0 ];then error_exit "Unable to attach image to loop device! (Image = $imgfile)"; fi
$bbox mount -t ext4 /dev/block/loop255 $mnt
echo -n "Command: $bbox mount -t ext4 /dev/block/loop255 $mnt \n"
if [ $? -ne 0 ];then error_exit "Unable to mount the loop device! \n"; fi
###########################################
# Mount all required partitions #
###########################################
$bbox mount -t devpts devpts $mnt/dev/pts
echo -n "Command: $bbox mount -t devpts devpts $mnt/dev/pts \n"
if [ $? -ne 0 ];then $bbox mount -o bind /dev $mnt/dev; $bbox mount -t devpts devpts $mnt/dev/pts; fi
if [ $? -ne 0 ]; then error_exit "Unable to mount $mnt/dev/pts!"; fi
$bbox mount -t proc proc $mnt/proc
echo -n "Command: $bbox mount -t proc proc $mnt/proc \n"
if [ $? -ne 0 ];then error_exit "Unable to mount $mnt/proc!"; fi
$bbox mount -t sysfs sysfs $mnt/sys
echo -n "Command: $bbox mount -t sysfs sysfs $mnt/sys \n"
if [ $? -ne 0 ];then error_exit "Unable to mount $mnt/sys!"; fi
$bbox mount -o bind /sdcard $mnt/sdcard
echo -n "Command: $bbox mount -o bind /sdcard $mnt/sdcard \n"
if [ $? -ne 0 ];then error_exit "Unable to bind $mnt/sdcard!"; fi
if [[ ! -d $mnt/root/cfg ]]; then mkdir $mnt/root/cfg; fi
$bbox mount -o bind $(dirname $imgfile) $mnt/root/cfg
echo -n "Command: $bbox mount -o bind $(dirname $imgfile) $mnt/root/cfg \n"
$bbox mount -o bind /sys/fs/selinux $mnt/selinux
echo -n "Command: $bbox mount -o bind /sys/fs/selinux $mnt/selinux \n"
###########################################
# Checks if you have a external sdcard #
# and mounts it if you do #
###########################################
if [ -d /sdcard/external_sd ]; then
$bbox mount -o bind /sdcard/external_sd $mnt/external_sd
fi
if [ -d /Removable/MicroSD ]; then
$bbox mount -o bind /Removable/MicroSD $mnt/external_sd
fi
# This is for the HD version of the Archos 70 internet tablet, may be the same for the SD card edition but i dont know.
if [ -d /storage ]; then
$bbox mount -o bind /storage $mnt/external_sd
fi
###########################################
# Mount all user defined mounts if any #
###########################################
if [ -f $imgfile.mounts ]; then
olddir=$(pwd)
echo "Mounting user mounts"
cd $mnt
if [[ ! -d $mnt/$usermounts ]]; then $bbox mkdir -p $usermounts; fi
echo "# Script to unmount user defined mounts, do not delete or edit!" > $imgfile.shutdown
echo "cd $mnt/$usermounts" > $imgfile.shutdown
cd $mnt/$usermounts
for entry in $(cat "$imgfile.mounts"); do
ANDROID=${entry%;*}
LINUX=${entry#*;}
if [[ -d $ANDROID ]]; then
echo -n "Mounting $ANDROID to $usermounts/$LINUX... "
if [[ ! -d $mnt/$usermounts/$LINUX ]]; then $bbox mkdir -p $LINUX; fi
$bbox mount -o bind $ANDROID $mnt/$usermounts/$LINUX &> /dev/null
if [ $? -ne 0 ];then
echo FAIL
if [[ -d $mnt/$usermounts/$LINUX ]]; then $bbox rmdir -p $LINUX; fi
else
echo OK
echo "$bbox umount $mnt/$usermounts/$LINUX" >> $imgfile.shutdown
echo "$bbox rmdir -p $LINUX" >> $imgfile.shutdown
fi
else
echo "Android folder not found: $ANDROID"
fi
done
echo "cd $mnt" >> $imgfile.shutdown
echo "$bbox rmdir -p $usermounts" >> $imgfile.shutdown
cd $olddir
else
echo "No user defined mount points"
fi
###########################################
# Sets up network forwarding #
###########################################
$bbox sysctl -w net.ipv4.ip_forward=1
if [ $? -ne 0 ];then error_exit "Unable to forward network!"; fi
# If NOT $mnt/root/DONOTDELETE.txt exists we setup hosts and resolv.conf now
#if [ ! -f $mnt/root/DONOTDELETE.txt ]; then
# echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
# if [ $? -ne 0 ];then error_exit "Unable to write resolv.conf file!"; fi
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "127.0.0.1 localhost" > $mnt/etc/hosts
# if [ $? -ne 0 ];then error_exit "Unable to write hosts file!"; fi
#fi
###########################################
# Chroot into ubuntu #
###########################################
$bbox chroot $mnt /root/init.sh $(basename $imgfile)
echo -n "Command: $bbox chroot $mnt /root/init.sh $(basename $imgfile) \n"
###########################################
# Shut down ubuntu #
###########################################
echo "Shutting down Linux ARM"
#for pid in `lsof | grep $mnt | sed -e's/ / /g' | cut -d' ' -f2`; do kill -9 $pid >/dev/null 2>&1; done
for pid in `$bbox lsof | $bbox grep $mnt | $bbox sed -e's/ / /g' | $bbox cut -d' ' -f2`; do $bbox kill -9 $pid >/dev/null 2>&1; done
sleep 5
###########################################
# Unmount all user defined mounts if any #
###########################################
if [ -f $imgfile.shutdown ]; then
echo "Unmounting user defined mounts"
sh $imgfile.shutdown
rm $imgfile.shutdown
fi
$bbox umount $mnt/root/cfg
$bbox umount $mnt/sdcard
$bbox umount $mnt/external_sd
$bbox umount $mnt/dev/pts
$bbox umount $mnt/dev
$bbox umount $mnt/proc
$bbox umount $mnt/sys
$bbox umount $mnt/selinux
$bbox umount $mnt
I am at my whips end, the 12.2 is an awsome device to finally run a desktop on as a tablet, my mom already calls it a "TabTop" tablet+laptop, all I see though is a hole in the wall that is the size of my head
Could anyone please assist me with this strange issue? Pretty please? :angel:
With the new beta coming soon™ for CLI and that there won`t be many people like me that buy this toy for fun, I also volunteer to help to make this app idiot proof (point to self) as the work is awsome, even if it didn`t run out of the box :highfive:
No one an idea?
Kamuchi said:
No one an idea?
Click to expand...
Click to collapse
I also have this problem... I think it's caused by the kernel that is set to enforcing... ; (
But you can use Debian no root it uses a fakechroot so you can use it without root and it uses the X server and you needn't to vnc in it. Hope I could help
prohackerbro said:
I also have this problem... I think it's caused by the kernel that is set to enforcing... ; (
But you can use Debian no root it uses a fakechroot so you can use it without root and it uses the X server and you needn't to vnc in it. Hope I could help
Click to expand...
Click to collapse
did you get debian to work ?
great!!
I am having problems trying to mount /system rw on my rooted phone. This is making my app, which need to do this , fail.
When i try to debug i notice this:
# adb shell
[email protected]:/ $ su -
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ # busybox mount /system -o remount,rw
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
Now trying to re-run adb in root mode:
# adb root
restarting adbd as root
# adb shell
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ # busybox mount /system -o remount,rw
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
Still no go
Now i use adb to remount it by itself
# adb remount
remount succeeded
# adb shell
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
After remounting using adb, i can remount ro/rw at will using busybox.
[email protected]:/ # busybox mount /system -o remount,ro
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ # busybox mount /system -o remount,rw
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
What am i doing wrong ? Why rw mounting appears to be available only after a 'adb remount' command ?
Thanks !
salatiel said:
I am having problems trying to mount /system rw on my rooted phone. This is making my app, which need to do this , fail.
When i try to debug i notice this:
# adb shell
[email protected]:/ $ su -
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ # busybox mount /system -o remount,rw
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
Now trying to re-run adb in root mode:
# adb root
restarting adbd as root
# adb shell
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ # busybox mount /system -o remount,rw
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
Still no go
Now i use adb to remount it by itself
# adb remount
remount succeeded
# adb shell
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
After remounting using adb, i can remount ro/rw at will using busybox.
[email protected]:/ # busybox mount /system -o remount,ro
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ # busybox mount /system -o remount,rw
[email protected]:/ # mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
What am i doing wrong ? Why rw mounting appears to be available only after a 'adb remount' command ?
Thanks !
Click to expand...
Click to collapse
mount -o remount,rw /system
I think it was in the wrong order. One thing to remember is that busybox is a bit... finicky when compared to the full-featured, stand-alone Unix commands.
:laugh:
I've been there. Sometimes ya just gotta take a break.
hello,
i have downloaded:
UL-K00G-WW-10.16.1.28.10-user.zip
and the other WW zip`s from the asus website
i can start only droidboot when i boot.
Then:
fastboot works
adb shell works (can chmod, mkdir, mount, fdisk an all the other files from the /sbin directory )(searched the device and internet for parted does not found a file that works)
twrp with modifikations and mount external_sd works
cwm with mount external_sd works
i can flash with xFSTK (unzipped the update.zip like UL-K00G-WW-10.16.1.28.10-user.zip and use the contained files of the iwifi.zip )
(i think all the recommend tools how i need can i use)
i can`t mount any partition of the /dev/block/mmcblk0
fdisk /dev/block/mmcblk0 shows me:
Command (m for help): ←[6np
Disk /dev/block/mmcblk0: 15.7 GB, 15741222912 bytes
4 heads, 16 sectors/track, 480384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
Command (m for help): ←[6n
the reason was i erased this block device.
i have no backup
Hello, can anyone help me with a raw image of my telephone, or help to recover my partition table? I have erased my partition table.
The best for me is a idea, not a how to. After this doesn`t work i ask again.
on the device i found these one:
partition_table=gpt
create -z /dev/block/mmcblk0
create /dev/block/mmcblk0
boot -p /dev/block/mmcblk0
reload /dev/block/mmcblk0
add -b 34 -s 524288 -t efi -u 80868086-8086-8086-8086-000000000000 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 524322 -s 65536 -t efi -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 589858 -s 262144 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 852002 -s 1024000 -t data -u 80868086-8086-8086-8086-000000000003 -l APD -T 0 -P 0 /dev/block/mmcblk0
add -b 1876002 -s 16384 -t data -u 80868086-8086-8086-8086-000000000004 -l ADF -T 0 -P 0 /dev/block/mmcblk0
add -b 1892386 -s 16384 -t data -u 80868086-8086-8086-8086-000000000005 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 1908770 -s 2883584 -t data -u 80868086-8086-8086-8086-000000000006 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 4792354 -s 524288 -t data -u 80868086-8086-8086-8086-000000000007 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 5316642 -s 4194304 -t data -u 80868086-8086-8086-8086-000000000008 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 9510946 -s $calc($lba_end-16384) -t data -u 80868086-8086-8086-8086-000000000009 -l data -T 0 -P 0 /dev/block/mmcblk0
reload /dev/block/mmcblk0
so i have to ask how to create with the fdisk tool a new one.
my problem is with th primary and extented partition, how many of this and which one of the mmcblk0(p) partition is where to create.
thank you for your effort
Hello, So I've been kind of dissapointed with the performance of my rooted shield. I've worked with Linux before and threw together "script" which works when run from recovery with /system /data and /cache removed.
I know there are some redundancies with it so if any one knows how to optimize or trim the fat off it please let me know where I went wrong. Other than losing adb and sbin functions the read write speed without journaling kills every benchmark app thats i've tested from the play store. any ways heres what I threw together, it works but it could work a whole lot better. Thanks. This is for the Nvidia Shield K1 and OG. File systems can't be mounted when running this, I learned that the hard way, I've been running it from twrp terminal and it seems to work but when run as an init.d script it soft bricks hard. I've appended *.txt to the file format so I can attach, e2fsck,tune2fs are busybox applets that works with our version of twrp and can be run from adb shell. or just add them to /sbin/ don't forget to remove the .sh from the end, ie e2fsck.txt turns into e2fsck
sync;
/sbin/busybox umount -l /system
/sbin/busybox umount -l /cache
/sbin/busybox umount -l /data
/sbin/busybox umount -l /dev/block/mmcblk0p13
/sbin/busybox umount -l /dev/block/mmcblk0p14
/sbin/busybox umount -l /dev/block/mmcblk0p23
/sbin/tune2fs -m 0 /dev/block/mmcblk0p13
/sbin/tune2fs -m 0 /dev/block/mmcblk0p14
/sbin/tune2fs -m 0 /dev/block/mmcblk0p23
/sbin/tune2fs -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
/sbin/tune2fs -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/sbin/tune2fs -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sbin/e2fsck -yf /dev/block/platform/sdhci-tegra.3/by-name/APP
/sbin/e2fsck -yf /dev/block/platform/sdhci-tegra.3/by-name/CAC
/sbin/e2fsck -yf /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sbin/e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/APP
/sbin/e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/CAC
/sbin/e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sbin/e2fsck -p /dev/block/mmcblk0p13
/sbin/e2fsck -p /dev/block/mmcblk0p14
/sbin/e2fsck -p /dev/block/mmcblk0p23
/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p13
/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p14
/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p23
/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p13
/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p14
/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p23
/sbin/e2fsck -Dfy /dev/block/platform/sdhci-tegra.3/by-name/APP
/sbin/e2fsck -Dfy /dev/block/platform/sdhci-tegra.3/by-name/CAC
/sbin/e2fsck -Dfy /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sbin/e2fsck -Dfy /dev/block/mmcblk0p13
/sbin/e2fsck -Dfy /dev/block/mmcblk0p14
/sbin/e2fsck -Dfy /dev/block/mmcblk0p23
/sbin/busybox mount -t ext4 -o suid,dev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc,data=writeback,discard /dev/block/mmcblk0p13
/sbin/busybox mount -t ext4 -o suid,dev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc,data=writeback,discard /dev/block/mmcblk0p14
/sbin/busybox mount -t ext4 -o suid,dev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc,data=writeback,discard /dev/block/mmcblk0p23
sync;