Related
After moving the folders (app, app-private, data, dalvik-cache) to the sd, it seems I cannot write to it, only read.
for the symlinks, the permissions are: root.root lrwxrwxrwx (777)
for the folders on sd, the permissions are: system.system drwxrwx--x (771)
Are these the permissions you guys have on your g1?
Symptoms:
- cant download apps
- receive mms but cant download pics
Mine are:
drwxrwx--x 2 1000 1000 4096 Apr 15 13:43 app
drwxrwx--x 2 1000 1000 4096 Apr 8 21:39 app-private
drwxrwx--x 2 1000 1000 8192 Apr 15 13:43 dalvik-cache
drwx------ 2 0 0 16384 Apr 7 17:28 lost+found
What method did you use to copy over the files? It would appear that the permissions did not get transferred.
daveid said:
Mine are:
drwxrwx--x 2 1000 1000 4096 Apr 15 13:43 app
drwxrwx--x 2 1000 1000 4096 Apr 8 21:39 app-private
drwxrwx--x 2 1000 1000 8192 Apr 15 13:43 dalvik-cache
drwx------ 2 0 0 16384 Apr 7 17:28 lost+found
What method did you use to copy over the files? It would appear that the permissions did not get transferred.
Click to expand...
Click to collapse
I believe the permissions were transfered right. just in case though, I chown the directories to system.system .
what does your symlinks show in /data/?
*edit* I did it through the recovery console with instructions from this post
*edit 2* I got mms to work by the chmod'ing the dirs. Looks like a lot more people are having issues with the market place so this may not be causing the issue.
lchanmanl said:
After moving the folders (app, app-private, data, dalvik-cache) to the sd, it seems I cannot write to it, only read.
for the symlinks, the permissions are: root.root lrwxrwxrwx (777)
for the folders on sd, the permissions are: system.system drwxrwx--x (771)
Are these the permissions you guys have on your g1?
Symptoms:
- cant download apps
- receive mms but cant download pics
Click to expand...
Click to collapse
Only superuser and the owner(the app itself) should be able to write anything to those. So it looks like permissions are o.k. to me. For the not downloading problem, it seems google is upgrading the market and downloads are going crazy slow(11 hours for an app) for people with the cupcake builds. You might be experiencing this. Not sure about the MMS stuff, haven't ever sent or received an mms.
EDIT: nm, didn't read the post right above mine...
Google Blocks Cupcake From Market
[email protected] said:
Only superuser and the owner(the app itself) should be able to write anything to those. So it looks like permissions are o.k. to me. For the not downloading problem, it seems google is upgrading the market and downloads are going crazy slow(11 hours for an app) for people with the cupcake builds. You might be experiencing this. Not sure about the MMS stuff, haven't ever sent or received an mms.
EDIT: nm, didn't read the post right above mine...
Click to expand...
Click to collapse
http://www.boygeniusreport.com/2009...gle-blocks-cupcake-users-from-android-market/
I installed virtousity, it hangs 2 times, the 2nd time it wont boot anymore, stuck on white htc screen.
so i tried to reboot on recovery clockworkmod recovery v5.0.2.0 but it only shows the hat and arrow and "clockworkmod recovery v5.0.2.0" and nothing after that.
so i tried to install clockworkmod recovery via fastboot and it just hangs on "writing recovery..."
i dont know what else to try, anybody can help me?
i tried this method of installing via PG88IMG on bootloader, and its stuck in "updating..."
does it look like eMMC problem?
ruu says it cant detect my phone? and i notice that when i connect my phone it cant find/install "android phone" usb driver.
so i run adb command and this what came out, is this good news or bad news?
cat /proc/kmsg | grep mmc0
<3>[ 7.698364] mmc0: No card detect facilities available
<6>[ 7.698913] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.699127] mmc0: Platform slot type: MMC
<6>[ 7.699279] mmc0: 4 bit data mode disabled
<6>[ 7.699401] mmc0: 8 bit data mode enabled
<6>[ 7.699615] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.699737] mmc0: Slot eject status = 0
<6>[ 7.699890] mmc0: Power save feature enable = 1
<6>[ 7.700012] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0baf0000
<6>[ 7.700134] mmc0: DM cmd busaddr 0x0baf0000, cmdptr busaddr 0x0baf0300
<6>[ 7.853759] mmc0: new high speed MMC card at address 0001
<6>[ 7.854980] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Click to expand...
Click to collapse
Did you wipe data and cache before you flashed virtuous unity?
Sent from my HTC Desire S using XDA App
matthewsucks said:
Did you wipe data and cache before you flashed virtuous unity?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
no, so thats the problem? what should i do know? the adb command seems saying that its not an eMMC problem.
Now, go into recovery and factory reset. Then, redownload rom manager and flash your rom from your sd card. To go into recovery mode, remove your battery and put it in, then hold the lock button and volume down button.
Sent from my HTC Desire S using XDA App
i cant factory reset, it just hangs when factory reset is selected.
Did you backup your stock rom? If you didn't, your phone's bricked. You gotta send it for repair.
Sent from my HTC Desire S using XDA App
matthewsucks said:
Did you backup your stock rom? If you didn't, your phone's bricked. You gotta send it for repair.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
i backed up it, via clockwork mod recovery. but i cant install it cause clockwork mod recovery hangs and cant start.
Hang? How does. It hang?
Sent from my HTC Desire S using XDA App
matthewsucks said:
Hang? How does. It hang?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
the factory reset hangs when i select it.
the clockworkmod recovery hangs when i go to recovery mode, its just says "clockworkmod recovery v5.0.2.0 recovery" with a hat and an orange circle arrow then nothing, i left it for a long time, still nothing
now all i can do is adb shell commands.
Now, don't enter recovery. Go to your bootloader and hit factory reset.
Sent from my HTC Desire S using XDA App
Not actually sure if this works on the Desire S (never had to use it) but have you tried:
adb reboot fastboot
fastboot erase cache
fastboot reboot
Whilst the HTC logo is displaying:
adb reboot recovery
Presuming it now enters recovery properly, you might want to do a full factory reset and another cache wipe from the main recovery menu.
I wish you luck!
LaKraven said:
Not actually sure if this works on the Desire S (never had to use it) but have you tried:
adb reboot fastboot
fastboot erase cache
fastboot reboot
Whilst the HTC logo is displaying:
adb reboot recovery
Presuming it now enters recovery properly, you might want to do a full factory reset and another cache wipe from the main recovery menu.
I wish you luck!
Click to expand...
Click to collapse
adb reboot fastboot - reboots the phone to htc logo and hangs, so what i did was go into hboot, select fastboot and connect usb, then fastboot turns to fastboot usb. after that i run fastboot erase cache which hangs the phone.
it seems this is not a burned eMMC problem, its just that the files are messed up/ maybe if theres a "scandisk" or repair partition i can use. but i dont know linux commands that well.
also tried this command inside adb shell:
mount data
mount: can't read '/etc/fstab': No such file or directory
so it seems im missing some files
matthewsucks said:
Now, don't enter recovery. Go to your bootloader and hit factory reset.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
factory reset hangs
cd /dev/block
/dev/block # ll
ll
/sbin/sh: ll: not found
/dev/block # ls -l
ls -l
brw------- 1 root root 7, 0 Sep 11 05:40 loop0
brw------- 1 root root 7, 1 Sep 11 05:40 loop1
brw------- 1 root root 7, 2 Sep 11 05:40 loop2
brw------- 1 root root 7, 3 Sep 11 05:40 loop3
brw------- 1 root root 7, 4 Sep 11 05:40 loop4
brw------- 1 root root 7, 5 Sep 11 05:40 loop5
brw------- 1 root root 7, 6 Sep 11 05:40 loop6
brw------- 1 root root 7, 7 Sep 11 05:40 loop7
brw------- 1 root root 179, 0 Sep 11 05:40 mmcblk0
brw------- 1 root root 179, 1 Sep 11 05:40 mmcblk0p1
brw------- 1 root root 179, 10 Sep 11 05:40 mmcblk0p10
brw------- 1 root root 179, 11 Sep 11 05:40 mmcblk0p11
brw------- 1 root root 179, 12 Sep 11 05:40 mmcblk0p12
brw------- 1 root root 179, 13 Sep 11 05:40 mmcblk0p13
brw------- 1 root root 179, 14 Sep 11 05:40 mmcblk0p14
brw------- 1 root root 179, 15 Sep 11 05:40 mmcblk0p15
brw------- 1 root root 179, 16 Sep 11 05:40 mmcblk0p16
brw------- 1 root root 179, 17 Sep 11 05:40 mmcblk0p17
brw------- 1 root root 179, 18 Sep 11 05:40 mmcblk0p18
brw------- 1 root root 179, 19 Sep 11 05:40 mmcblk0p19
brw------- 1 root root 179, 2 Sep 11 05:40 mmcblk0p2
brw------- 1 root root 179, 20 Sep 11 05:40 mmcblk0p20
brw------- 1 root root 179, 21 Sep 11 05:40 mmcblk0p21
brw------- 1 root root 179, 22 Sep 11 05:40 mmcblk0p22
brw------- 1 root root 179, 23 Sep 11 05:40 mmcblk0p23
brw------- 1 root root 179, 24 Sep 11 05:40 mmcblk0p24
brw------- 1 root root 179, 25 Sep 11 05:40 mmcblk0p25
brw------- 1 root root 179, 26 Sep 11 05:40 mmcblk0p26
brw------- 1 root root 179, 27 Sep 11 05:40 mmcblk0p27
brw------- 1 root root 179, 28 Sep 11 05:40 mmcblk0p28
brw------- 1 root root 179, 3 Sep 11 05:40 mmcblk0p3
brw------- 1 root root 179, 4 Sep 11 05:40 mmcblk0p4
brw------- 1 root root 179, 5 Sep 11 05:40 mmcblk0p5
brw------- 1 root root 179, 6 Sep 11 05:40 mmcblk0p6
brw------- 1 root root 179, 7 Sep 11 05:40 mmcblk0p7
brw------- 1 root root 179, 8 Sep 11 05:40 mmcblk0p8
brw------- 1 root root 179, 9 Sep 11 05:40 mmcblk0p9
brw------- 1 root root 179, 64 Sep 11 05:40 mmcblk1
brw------- 1 root root 179, 65 Sep 11 05:40 mmcblk1p1
drwxr-xr-x 4 root root 80 Sep 11 05:40 platform
/dev/block # fsck/?
fsck/?
/sbin/sh: fsck/?: not found
/dev/block # mount -a
mount -a
mount: mounting /recovery on emmc failed: No such file or directory
mount: mounting /boot on emmc failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /sdcard on vfat failed: No such file or directory
mount: mounting /system on ext4 failed: No such file or directory
/dev/block #
Click to expand...
Click to collapse
anybody know why cant i mount?
Hopefully this thread might help you out.
http://forum.xda-developers.com/showthread.php?t=1150917
zeekiz said:
Hopefully this thread might help you out.
http://forum.xda-developers.com/showthread.php?t=1150917
Click to expand...
Click to collapse
it seems im getting the same error from this thread when mounting /data and /cache. so its burned emmc?
since its s-off i have no more warranty, how available is this emmc from cellphone repair shops?
btw, i didnt pulled out the battery when the phone started not to boot, i used the vol+ vol- and power button. only used the pull out battery when the vol+ vol- power wont work.
this problem started when i use rom manager to "automatically" install virtuosity, and didnt clean my cache and data. also might be market related cause i was downloading and installing a lot of market apps when the phone hanged.
BratPAQ said:
it seems im getting the same error from this thread when mounting /data and /cache. so its burned emmc?
since its s-off i have no more warranty, how available is this emmc from cellphone repair shops?
btw, i didnt pulled out the battery when the phone started not to boot, i used the vol+ vol- and power button. only used the pull out battery when the vol+ vol- power wont work.
this problem started when i use rom manager to "automatically" install virtuosity, and didnt clean my cache and data. also might be market related cause i was downloading and installing a lot of market apps when the phone hanged.
Click to expand...
Click to collapse
Sorry to hear of this, it does sound very like yet another fired eMMC chip and it sounds like you did two of the possible things that I've read can cause eMMC fried chip. one) Remove battery and two) multiple market download.
Not that it's important anymore, but, wiping CACHE and DALVIK CACHE should always be done on a new ROM install, wiping DATA is just sometimes recommend. But not doing so should not lead to a bricked device. It sounds very like the battery pull has done it again - which to my reckoning is a hardware/software design flaw and SHOULD be covered under warranty!
Surely its worth returning just trying to return the device under warranty just to see if they don't notice that you've S-OFF you may be lucky!
If you cannot get past the HTC logo, and the eMMC's are indeed fried... there's no real way for HTC to know you've S-OFF'd your phone.
As Ben stated above, given that it's the removal of the battery (which is a user-intended activity and is SUPPOSED to be safe), this should certainly be accepted under warranty (or whatever your country's version is of "Statutory Rights") anyway.
Send it in for replacement/repair! The worst that'll happen is HTC refuse to do anything with it, send it back to you (as legally required to do so) and you're out of pocket on some postage!
Since the phone is FUBAR anyway, you've got nothing more than postage cost to lose!
LaKraven said:
If you cannot get past the HTC logo, and the eMMC's are indeed fried... there's no real way for HTC to know you've S-OFF'd your phone.
As Ben stated above, given that it's the removal of the battery (which is a user-intended activity and is SUPPOSED to be safe), this should certainly be accepted under warranty (or whatever your country's version is of "Statutory Rights") anyway.
Send it in for replacement/repair! The worst that'll happen is HTC refuse to do anything with it, send it back to you (as legally required to do so) and you're out of pocket on some postage!
Since the phone is FUBAR anyway, you've got nothing more than postage cost to lose!
Click to expand...
Click to collapse
Mine had the same symptoms, and I sent it to technical service. But, HTC's technicians can enter in recovery mode and realize that the terminal is s-off, has happened with my terminal. If so, warranty is void.
{
"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"
}
Root for Gear2 R380
Packed rootfs.img
NE5
R380XXU0BNE5rootfs_root.tar (Needs Gear 2 R380XXU0BNE5 installed)
NDD
R380XXU0BNDDrootfs_root.tar (Needs Gear 2 R380XXU0BNDD installed)
ND8
R380XXU0BND8rootfs_root.tar (Needs Gear 2 R380XXU0BND8 installed)
Gear2 NEO:
NE5
R381XXU0BNE5rootfs_root.tar (Needs Gear 2 NEO R381XXU0BNE5 installed)
Load into Odin and flash.
Done
Need sdb.exe from Tizen-SDK?
sdb.exe
What is this good for?
Disable camera sounds:
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
sdb shell mount -o remount,ro /
Custom ringtones:
sdb root on
sdb push your_ringtone.ogg /opt/share/settings/Ringtones/
reboot watch
Keep in mind free diskspace is 80MB for /opt/ don't fill it up!
fibs said:
Root for Gear2 R380 (fw: R380XXU0BNDD)
Packed rootfs.img: http://www.mediafire.com/download/2wxvnezieg7025x/r380rootfs_root.tar
Load into Odin and flash.
Done
Click to expand...
Click to collapse
thx!
are the terminal commands needed after the flash?
would this also be ok for the new E5 release?
TML1504 said:
thx!
are the terminal commands needed after the flash?
would this also be ok for the new E5 release?
Click to expand...
Click to collapse
No, commands are not needed. It's just to show the version and howto check if it worked.
This will not work if E5 is installed since you will flash the whole root filesystem.
I can build for E5 if needed. Did not upgrade my watch yet..
fibs said:
I can build for E5 if needed. Did not upgrade my watch yet..
Click to expand...
Click to collapse
I appreciate your good work on this. Unfortunately I'm in the US and still stuck on ND8. As a suggestion, since you're going to build this for new ROMs as they come out, could you start adding the last three letters/numbers of the ROM to your tar files?
JimSmith94 said:
I appreciate your good work on this. Unfortunately I'm in the US and still stuck on ND8. As a suggestion, since you're going to build this for new ROMs as they come out, could you start adding the last three letters/numbers of the ROM to your tar files?
Click to expand...
Click to collapse
Thx, already included version build for the E5 .tar uploading right now. The sad part is that the only "useful" way to use the root access right now is to get rid of the camera sounds
But if you need root access to your ND8 I can upload.
fibs said:
Thx, already included version build for the E5 .tar uploading right now. The sad part is that the only "useful" way to use the root access right now is to get rid of the camera sounds
But if you need root access to your ND8 I can upload.
Click to expand...
Click to collapse
If you have easy access to ND8, that would be great. Otherwise I can wait for the newer builds to hit. I'll be upgrading as soon as I can anyway.
fibs said:
I can build for E5 if needed. Did not upgrade my watch yet..
Click to expand...
Click to collapse
Please, thx!
TML1504 said:
Please, thx!
Click to expand...
Click to collapse
I kept my first post updated. E5 added.
Can this be used with NEO as well?
mpogr said:
Can this be used with NEO as well?
Click to expand...
Click to collapse
i guess not, due to different hardware. although: perhaps it would work, because the hardware is very similar except the cam. depends on the partition layout, and that could be the same...
this is the partition layout of the gear one (with tizen), i guess "our" layout will be very similar...
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
fibs said:
I kept my first post updated. E5 added.
Click to expand...
Click to collapse
thx again very much! worked flawlessly!
can you please provide the "sdb.exe" from the tizen-sdk as well?
TML1504 said:
this is the partition layout of the gear one (with tizen), i guess "our" layout will be very similar...
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
Click to expand...
Click to collapse
Partition layout of Gear 2 is like this:
lrwxrwxrwx 1 root root 15 Jun 4 00:27 boot -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 4 00:27 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 4 00:27 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 4 00:27 csa -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 4 00:27 csc -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 4 00:27 fota -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 4 00:27 module -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 4 01:13 param -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Jun 4 00:27 ramdisk1 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 4 00:27 ramdisk2 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 4 00:27 recovery -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 16 Jun 4 00:27 rootfs -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Jun 4 00:27 system -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 4 00:27 system-data -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 4 00:27 user -> ../../mmcblk0p14
It is different, but I have no idea how layout of gear neo looks like.
TML1504 said:
thx again very much! worked flawlessly!
can you please provide the "sdb.exe" from the tizen-sdk as well?
Click to expand...
Click to collapse
Sure, link will be added to main post.
This is to make a change in ringtone sound?
dansafe said:
This is to make a change in ringtone sound?
Click to expand...
Click to collapse
Is possible.
push your ringtones to: /opt/share/settings/Ringtones/
When in .ogg only filename will be displayed. When in .mp3 it will show up like ring.mp3
I think a reboot is needed to find your new ringtones in the list.
But keep in mind free diskspace is 80MB for /opt/ don't fill it up!
Super good work ! THX.
Ok, im a noob at watch rooting. Is there a special version of odin for the watch or a special way to do this? Does it wipe everything? All I wish to do is wipe the camera sounds.
Sent from my SM-N900T using Tapatalk
Safe to assume this won't work with the Neo? If it does awesome work. If not still awesome work lol.
Compusmurf said:
Ok, im a noob at watch rooting. Is there a special version of odin for the watch or a special way to do this? Does it wipe everything? All I wish to do is wipe the camera sounds.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
no special odin needed! i used 3.07
to enter download mode: press and hold the watch-button, when the watch reboots quickly press the button a few times, select download, then flash.
it does no wipe.
important: first flash the official rom, then the according rootfs from the first post.
enable usb debugging in watch settings
afterwards you need the sdb.exe, open a command prompt where the exe is located and enter the following commands:
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
it worked perfectly for me!
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
fogame said:
Safe to assume this won't work with the Neo? If it does awesome work. If not still awesome work lol.
Click to expand...
Click to collapse
neo would need a specific rootfs, otherwise the procedure is the same!
TML1504 said:
neo would need a specific rootfs, otherwise the procedure is the same!
Click to expand...
Click to collapse
Fantastic! Now I just need to find the rootfs lol. Someone will probably beat me to it.
This is to make a change in alerts sound?
btw. silent camera and change ringtones works verry good ! THX
So, I just managed to get the Bootloader unlocked, flashed CWRM and then accidentally hit the factory reset button from the system settings menu, and am now stuck in the reset recovery screen.
I have access to adb but not fastboot. I have not done anything with NVFLASH
Am I permanently screwed for this motherboard or can I still be recovered?
ls -l /dev/block/mmc*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- 1 root root 179, 0 Aug 29 02:23 /dev/block/mmcblk0
brw------- 1 root root 179, 16 Aug 29 02:23 /dev/block/mmcblk0boot0
brw------- 1 root root 179, 32 Aug 29 02:23 /dev/block/mmcblk0boot1
brw------- 1 root root 179, 1 Aug 29 02:23 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 Aug 29 02:23 /dev/block/mmcblk0p10
brw------- 1 root root 179, 2 Aug 29 02:23 /dev/block/mmcblk0p2
brw-rw---- 1 root system 179, 3 Aug 29 02:23 /dev/block/mmcblk0p3
brw-rw---- 1 root system 179, 4 Aug 29 02:23 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 Aug 29 02:23 /dev/block/mmcblk0p5
brw------- 1 drm drm 179, 6 Aug 29 02:23 /dev/block/mmcblk0p6
brw-rw---- 1 root system 179, 7 Aug 29 02:23 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 Aug 29 02:23 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 Aug 29 02:23 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Code:
adb shell
~ #cd sys
/sys # ls
ls
block class devices fs module tf_driver
bus dev firmware kernel power
/sys #cd block
/sys/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0boot1
loop1 loop3 loop5 loop7 mmcblk0boot0 zram0
can I use this to edit something and unbrick?
Stephenopolos said:
Code:
adb shell
~ #cd sys
/sys # ls
ls
block class devices fs module tf_driver
bus dev firmware kernel power
/sys #cd block
/sys/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0boot1
loop1 loop3 loop5 loop7 mmcblk0boot0 zram0
can I use this to edit something and unbrick?
Click to expand...
Click to collapse
If you reboot by long pressing the power button, does it boot straight back to recovery?
If so you can try these commands to clear the Wipe Data command from the misc partition:
Code:
adb shell
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
reboot
Good luck!
Thanks for the quick response. Yes it does drop immediately into the recovery/reset wipe data screen on reboot.
It's pretty late and I want to avoid making any mistakes in typing commands so I'm going to try that in the morning.
Also, while i'm not the best at the command line side, I am comfortable opening things up, so if it doesn't work I'm not entirely opposed to just buying a replacement MB and swapping it out. Hopefully it'll work though.
Stephenopolos said:
Thanks for the quick response. Yes it does drop immediately into the recovery/reset wipe data screen on reboot.
It's pretty late and I want to avoid making any mistakes in typing commands so I'm going to try that in the morning.
Also, while i'm not the best at the command line side, I am comfortable opening things up, so if it doesn't work I'm not entirely opposed to just buying a replacement MB and swapping it out. Hopefully it'll work though.
Click to expand...
Click to collapse
If you use Wipe Data from the bootloader or the Factory reset from Settings a command gets written to misc to start the recovery and wipe data.
Problem is, custom recoveries don't really "get" the command and do not execute it so the command does not get erased from misc and you're stuck in booting to recovery because the bootloader executes that command on each boot.
If your recovery is CWM you can try just leaving it on the wipe data screen for a few hours. With past CWM versions that usually worked and it eventually finished the wipe. Not with TWRP though.
Connect the tab to power and leave it on the wipe data screen until tomorrow. Then you can still try to clear the command with dd.
Copy and paste it. You don't want to have any typos with a dd command...
berndblb said:
Problem is, custom recoveries don't really "get" the command
Click to expand...
Click to collapse
Only if your recovery kernel is too old to work with the bootloader, in which case it can't access any partitions.
berndblb said:
If your recovery is CWM you can try just leaving it on the wipe data screen for a few hours. With past CWM versions that usually worked and it eventually finished the wipe. Not with TWRP though.
Click to expand...
Click to collapse
TWRP should do its "Factory Reset" (which doesn't clear /sdcard). I've never tried it because I don't want to restore everything from a backup.
ran command this morning, and it hung in the shell... just sits there without finishing the command.
frustrating... I thought i'd read everything and triple read it again, but the main thread for custom recoveries for this tablet, didn't really mention anything about avoiding factory reset from device.
oh well. found a MB on ebay cheap i'll try the command again in a bit and if it doesn't work then next week i'll be installing a mb myself.
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
1+0 records in
1+0 records out
64 bytes (64B) copied, 402.164494 seconds, 0B/s
I'm assuming this means success...
will see in a bit... tablet is now claiming it has a low battery after I told it to reboot.
Hallelujah! it worked! berndblb You're my new favorite person in the world today.
_that said:
Only if your recovery kernel is too old to work with the bootloader, in which case it can't access any partitions.
TWRP should do its "Factory Reset" (which doesn't clear /sdcard). I've never tried it because I don't want to restore everything from a backup.
Click to expand...
Click to collapse
I have never tried it either. Just seen users reporting that with CWM installed the command eventually went through if you left it alone long enough. That doesn't seem to work with TWRP. But that's just hearsay....
Stephenopolos said:
Hallelujah! it worked! berndblb You're my new favorite person in the world today.
Click to expand...
Click to collapse
Very good!
But you have to thank @_that ^^^ for the command. He's the one I stole it from
berndblb said:
I have never tried it either. Just seen users reporting that with CWM installed the command eventually went through if you left it alone long enough. That doesn't seem to work with TWRP. But that's just hearsay....
Very good!
But you have to thank @_that ^^^ for the command. He's the one I stole it from
Click to expand...
Click to collapse
... you got to me first though...
Anyway, I had difficulty getting CM11 and CM12 to install eventually managed to get zombipop to install by dropping it onto a USB stick and using the keyboard dock. Had to flash a new recovery image as well.. apparently the one I put on there the first time around was screwy.
Stephenopolos said:
... you got to me first though...
Anyway, I had difficulty getting CM11 and CM12 to install eventually managed to get zombipop to install by dropping it onto a USB stick and using the keyboard dock. Had to flash a new recovery image as well.. apparently the one I put on there the first time around was screwy.
Click to expand...
Click to collapse
Luck for you that I was here first. _that would have made you pull all kinds of logs before giving you the same command :laugh: :cyclops:
berndblb said:
Luck for you that I was here first. _that would have made you pull all kinds of logs before giving you the same command :laugh: :cyclops:
Click to expand...
Click to collapse
The required logs in this case are already in the OP. But thank you for taking over first level support.
Update - March 23rd, 2019.
There is now an excellent offline rooting method for HD10 (2017), HD8(2016-2018), all current FireOS versions, thanks to the fantastic effort by @diplomatic - link. This new root is obtained within a few seconds, so it is very fast. To install permanent root after mtk-su for HD10 (2017), HD8 (2016-2017), use the scripts by @Rortiz2 in here: v2.1, or v1.0 (see this link for a Linux script). For HD8 (2018), there is a dedicated full bootloader unlocking and permanent root guide - link. For HD10 (2017) there is also a full bootloader unlocking procedure available - link. The historical Kingoroot rooting procedure for HD10 (2017) is below. As a friendly reminder, once you have a root shell (obtained by any means), ensure that you disable OTA updates as to avoid getting an unrootable update (except for HD8 (2018) - do not run the commands below before you unlock the bootloader!!!):
Code:
mount -w -o remount /system
mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
ls -l /system/priv-app/DeviceSoftwareOTA/
The original Kingoroot method for HD10 (2017), all current FireOS versions - EASY SuperSu
Update v0.9, 12/29/18 As empasized by shonkin in this post, the method still works for FireOS 5.6.3.4. Enjoy!!! I would never have expected the hole to last his long ...
Update v0.8, 01/26/18 - as first reported by @najoor in this post, FireOS 5.6.0.1 is rootable! Today I verified this myself after a somewhat unsuccessful FlashFire update.
Update v0.7, 01/14/18 - @freaky2xd made a video with these rooting instructions, please follow it if you prefer a visual guide (here or here)
Update v0.6, 01/09/18 - there were reports that dr.fone app seems to be able to root the device as well. I took dr.fone for a spin, and based on its bloatedness and a few other annoying features, my personal recommendation is that you stick with the devil we know - Kingoroot (link)
Update v0.5, 01/04/18 - add a DOS bat file to remove any possible updates to Amazon packages
Update v0.4, 01/02/18 - title update
Update v0.3, 12/31/17 - light clean up; I got into a bootloop, and had to sideload a stock ROM & re-root - a.k.a. "eat my own dogfood" - Everything works fine.
Update v0.2, 12/30/17 - some redundant commands are removed.
Update v0.1, 12/30/17 - the rooting procedure is essentially taken from @retyre (here and here). Except, the instructions below include a lot of details, and handle mostly everything from the PC/ADB side. Try, and report back. GOOD LUCK!
Here is the guide to the painless root (while out of the box FireOS allows it; right now all FireOS versions up to and including 5.6.0.1 - the current OTA - are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).
Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!
The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)
Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet
Low tech way (thanks to @Blaiser47 and @retyre for suggestions!):
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Choose any option on that WiFi screen, press cancel, and then skip
Once Alexa shows up, swipe down from the top, turn on Airplane mode just to be sure
High tech way:
Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Connect Fire to your slow router
Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
Sign in to Amazon account when prompted
Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!
Part II (rooting via Kingoroot, disabling OTA, and getting SuperSu replacement, as per @retyre recommendations)
Take your Fire HD as is, do not do anything dramatic such as "factory reset", Amazon ROM sideloading, etc
Swipe down from the top, turn on Airplane mode - to ensure that there are no OTA updates during the procedure
In "Settings/Device Options", tap "Serial Number" 7 times, a menu "Developer Options" will appear
In "Settings/Device Options/Developer Options", turn ADB debugging to ON (under "Debugging")
In "Settings/Security", turn "Apps from Unknown Sources" to ON
Download ADB to your PC (link)
Setup ADB drivers on your PC, connect Fire to your PC, make sure "adb devices" command shows your Fire device, authorize ADB connection on Fire
Download SuperSu 2.79 (this exact version!!!) to your PC from this link, place it into your ADB PC folder. The filename of this apk will be assumed to be SuperSU-v2.79-20161205182033.apk below
Download the attached su64.zip to your PC (see the attachment below), unzip to your ADB PC folder
Open a CMD window in ADB PC folder (this will be called ADB_cmd window in the following steps), type
Code:
adb devices
adb uninstall eu.chainfire.supersu
This is a clean up of possible old SuperSu (just in case), ignore any errors you may get (if SuperSu is absent ...)
Download Kingoroot to your PC (link), install, let it update
Connect Fire to your PC; launch Kingoroot on PC; before pushing the big "ROOT" button in Kingoroot, uncheck a small box in the lower left corner for "Install recommended app" ; push "ROOT" button; wait for Kingoroot to root
Once Kingoroot succeeds, open a 2nd CMD window in ADB PC folder to your Fire (this will be called ADB_root window in the following steps), get a root shell, and disable OTA updates
Code:
adb shell
su
mount -w -o remount /system
mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
ls -l /system/priv-app/DeviceSoftwareOTA/
ignore any errors you may get while doing this; after 'su', you should see root (#) prompt here
Switch to the first ADB_cmd window, type
Code:
adb uninstall com.lionmobi.powerclean
adb uninstall com.kingoapp.link
adb uninstall kingoroot.supersu
adb install SuperSU-v2.79-20161205182033.apk
adb shell "am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity"
Skip this step - it is not needed
Switch to the second ADB_root window (with # prompt), type
Code:
cd /data/local/tmp
mount -w -o remount /system
cp ./su64 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su64 /system/xbin/su
chmod 0755 /system/xbin/su
am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity
On your Fire, SuperSu should pop up. Update SuperSu binary as "Normal", it should report "Installation failed." Proceed to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Uninstall all the junk from Kingoroot on your Fire, thanks to @fstanis for detailed instructions (copied here, executed from PC):
Code:
adb uninstall com.nemo.vidmate
adb shell rm -rf /sdcard/VidMate
adb shell rm -rf /sdcard/.a
adb shell rm -rf /sdcard/.DataStorage
adb shell rm -rf /sdcard/.UTSystemConfig
Some troubleshooting options:
If you believe you have the correct FireOS, but Kingoroot (or SuperSu) still fail, download the attached no_amzn_updates.zip to your PC, unzip to your ADB PC folder, open a CMD window in ADB PC folder, and type
Code:
.\no_amzn_updates.bat
The script will attempt to uninstall any apk updates to the official Amazon packages. Then repeat the rooting procedure from Step 1 skipping as necessary. See this post for more additional info on what the script does.
If you mess up your /system too much and get into a bootloop with "Fire" logo - use this post for links to the official Amazon ROM files; these bin's can be sideloaded via "adb sideload" in recovery
Want to say thanks by clicking the "Thanks" button ?
{
"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"
}
Fire HD 10 ROM links & misc :
Update: Uploaded modified Supersu 2.82 SR5 ready to be flashed in FlashFire. It really represents the Chainfire's swan song, the last of the true SuperSu versions, the end of the era !!!
Fire HD 10 (7th Gen 2017) ROM links from Amazon (use for sideloading your preferred version in case you mess up). If possible, turn off WiFi before sideloading a bin file - you don't want to catch an OTA while it's loading!
FireOS 5.6.3.0 (reports say that it's still rootable, the downgrade behavior is not clear)
update-kindle-suez-40.6.2.6_user_626533320.bin
update-kindle-40.6.2.6_user_626533320.bin
FireOS 5.6.2.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.1.2_user_612495820.bin
FireOS 5.6.1.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.0.5_user_605485120.bin
System image (restore via FlashFire) link. Unzip files to /sdcard/FlashFire/Backups/5.6.1.0, rename the 2 img to bin extensions. Create md5 sum files (in a shell, type "md5 system.bin > system.md5", same for boot.bin) The system image includes SuperSu, Xposed, Busybox; OTA apk is NOT renamed.
FireOS 5.6.0.1
update-kindle-40.5.9.5_user_595550320.bin
System image (restore via FlashFire v0.24) - link. Unzip files to /sdcard/FlashFire/Backups/5.6.0.1. The system image includes SuperSu, Xposed, Busybox; OTA apk is renamed.
FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457320.bin
FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457020.bin
FireOS 5.5.0.0
update-kindle-40.5.9.1_user_591450020.bin
In addition, please find attach a SuperSu zip that works with Flash Fire v0.24 (tested with FireOS 5.5.0.0 & 5.6.0.0).
The file was created by taking SuperSu v2.82 zip from this link (file name - SuperSU-v2.82-201705271822.zip).
Then in META-INF\com\google\android\update-binary I replaced one line forcing SuperSu to install armv7 binaries instead of arm64:
Code:
if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=arm64; SYSTEMLIB=/system/lib64; APPPROCESS64=true; fi;
with this one:
Code:
if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=armv7; fi;
Everything else is identical to the official version.
Using the official SuperSu zip will cause a bootloop - it looks like Fire HD 10 is not quite arm64 yet, and needs armv7 version of su binaries to work.
Useful tips & information:
How to install Xposed & Flashfire for easy backups and ROM updates
Follow this post by @retyre (and thank him!!!): link
Note: With stock FlashFire versions, the latest Flashfire version you can use is v0.24 (see the attached v0.24 apk, it needs the date patch which requires Xposed installed). Alternatively, it is possible to replace a library in Flashfire v0.51, and make v0.51 work:
link1
link2
link3
For convenience, I've done this procedure to the free FlashFire v.51 version using free apktool, and attached the file below (the signature will not match with the original FlashFire signed by @Chainfire, so you will need to uninstall other FlashFire packages before installing this one!)
With v0.51, uncheck two options (as per link2):
1) Emulate framebuffer in Settings
2) Mount /system read/write (after you choose the update file).
If you don't do 2), Flashfire v.51 will just sit there and never do anything
How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom).
1) Edit /system/build.prop and change ro.build.version.number to have "9" as the first value instead of "5", as recommended in this link
2) Reboot
3) Enable OTA by ensuring that /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed back to apk from apk_
4) Reboot
At this point the Fire will download a lot of apk packages, and will update Amazon system components (keeping FireOS version the same).
Partition trivia:
Partition info (gdisk binary) :
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 907.7M 80.0K 907.6M 4096
/dev/logd 512.0K 96.0K 416.0K 4096
/sys/fs/cgroup 907.7M 12.0K 907.7M 4096
/mnt/asec 907.7M 0.0K 907.7M 4096
/mnt/obb 907.7M 0.0K 907.7M 4096
/system 1.5G 1.2G 317.9M 4096
/data 26.5G 1.1G 25.4G 4096
/data/metrics 5.8M 232.0K 5.6M 4096
/cache 410.7M 14.9M 395.8M 4096
/mnt/sqfs 79.8M 79.8M 0.0K 32768
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/mnt/shell/emulated 26.5G 1.1G 25.4G 4096
/storage/emulated 907.7M 0.0K 907.7M 4096
/storage/emulated/0 26.5G 1.1G 25.4G 4096
/storage/emulated/0/Android/obb 26.5G 1.1G 25.4G 4096
/storage/emulated/legacy 26.5G 1.1G 25.4G 4096
/storage/emulated/legacy/Android/obb 26.5G 1.1G 25.4G 4096
[email protected]:/data/local/tmp # ./gdisk -l /dev/block/mmcblk0
./gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): B1541C10-343E-474B-B5B2-05796C64E992
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 1024-sector boundaries
Total free space is 990 sectors (495.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 1024 7167 3.0 MiB 8300 proinfo
2 7168 16383 4.5 MiB 8300 PMT
3 16384 18431 1024.0 KiB 8300 kb
4 18432 20479 1024.0 KiB 8300 dkb
5 20480 22527 1024.0 KiB 8300 lk
6 22528 32767 5.0 MiB 8300 tee1
7 32768 43007 5.0 MiB 8300 tee2
8 43008 123903 39.5 MiB 8300 metadata
9 123904 124927 512.0 KiB 8300 MISC
10 124928 141311 8.0 MiB 8300 reserved
11 141312 174079 16.0 MiB 8300 boot
12 174080 208895 17.0 MiB 8300 recovery
13 208896 3515391 1.6 GiB 8300 system
14 3515392 4383743 424.0 MiB 8300 cache
15 4383744 61071326 27.0 GiB 8300 userdata
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 81664 loop0
7 1 1254 loop1
7 2 10240 loop2
179 0 30535680 mmcblk0
179 1 3072 mmcblk0p1
179 2 4608 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 40448 mmcblk0p8
179 9 512 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 17408 mmcblk0p12
179 13 1653248 mmcblk0p13
179 14 434176 mmcblk0p14
179 15 28343791 mmcblk0p15
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 33 2 mmcblk0boot0p1
179 34 2 mmcblk0boot0p2
179 35 256 mmcblk0boot0p3
179 36 747 mmcblk0boot0p4
[email protected]:/ # ls -l /dev/block
ls -l /dev/block
brw------- root root 7, 0 2017-12-28 11:05 loop0
brw------- root root 7, 1 2017-12-28 11:05 loop1
brw------- root root 7, 2 2017-12-28 11:05 loop2
brw------- root root 7, 3 2017-12-28 11:05 loop3
brw------- root root 7, 4 2017-12-28 11:05 loop4
brw------- root root 7, 5 2017-12-28 11:05 loop5
brw------- root root 7, 6 2017-12-28 11:05 loop6
brw------- root root 7, 7 2017-12-28 11:05 loop7
brw-rw---- root system 179, 0 2017-12-28 11:05 mmcblk0
brw-rw---- root system 179, 32 2017-12-28 11:05 mmcblk0boot0
brw------- root root 179, 33 2017-12-28 11:05 mmcblk0boot0p1
brw------- root root 179, 34 2017-12-28 11:05 mmcblk0boot0p2
brw------- root root 179, 35 2017-12-28 11:05 mmcblk0boot0p3
brw------- root root 179, 36 2017-12-28 11:05 mmcblk0boot0p4
brw-rw---- root system 179, 64 2017-12-28 11:05 mmcblk0boot1
brw------- root root 179, 1 2017-12-28 11:05 mmcblk0p1
brw------- root root 179, 10 2017-12-28 11:05 mmcblk0p10
brw------- root root 179, 11 2017-12-28 11:05 mmcblk0p11
brw------- root root 179, 12 2017-12-28 11:05 mmcblk0p12
brw------- root root 179, 13 2017-12-28 11:05 mmcblk0p13
brw------- root root 179, 14 2017-12-28 11:05 mmcblk0p14
brw------- root root 179, 15 2017-12-28 11:05 mmcblk0p15
brw------- root root 179, 2 2017-12-28 11:05 mmcblk0p2
brw------- root root 179, 3 2017-12-28 11:05 mmcblk0p3
brw------- root root 179, 4 2017-12-28 11:05 mmcblk0p4
brw------- root root 179, 5 2017-12-28 11:05 mmcblk0p5
brw------- root root 179, 6 2017-12-28 11:05 mmcblk0p6
brw------- root root 179, 7 2017-12-28 11:05 mmcblk0p7
brw------- root root 179, 8 2017-12-28 11:05 mmcblk0p8
brw------- root root 179, 9 2017-12-28 11:05 mmcblk0p9
brw-rw---- root system 179, 96 2017-12-28 11:05 mmcblk0rpmb
drwxr-xr-x root root 2017-12-28 11:05 platform
drwx------ root root 2017-12-28 11:05 vold
brw------- root root 254, 0 2017-12-28 11:05 zram0
[email protected]:/ # ls -l /dev/block/platform/mtk-msdc.0/by-name/
ls -l /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-12-28 11:05 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-12-28 11:05 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-12-28 11:05 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-12-28 11:05 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2017-12-28 11:05 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2017-12-28 11:05 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2017-12-28 11:05 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2017-12-28 11:05 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-12-28 11:05 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-12-28 11:05 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-12-28 11:05 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-12-28 11:05 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-12-28 11:05 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-12-28 11:05 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-12-28 11:05 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-12-28 11:05 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-12-28 11:05 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-12-28 11:05 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-12-28 11:05 userdata -> /dev/block/mmcblk0p15
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 3786.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 29 GB, 31268536320 bytes, 61071360 sectors
3786 cylinders, 256 heads, 63 sectors/track
Units: cylinders of 16128 * 512 = 8257536 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors
Size Id Type
/dev/block/mmcblk0p1 0,0,2 1023,255,63 1 4294967295 4294967295 2047G ee EFI GPT
bibikalka said:
Here is the guide to the painless root (while out of the box FireOS allows it - right now all versions up to FireOS 5.6.0.0 are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).
Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!
The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)
Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet
Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Connect Fire to your slow router
Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
Sign in to Amazon account when prompted
Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!
Done
Click to expand...
Click to collapse
Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.
Blaiser47 said:
Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.
Click to expand...
Click to collapse
Even simpler: Choose any option on that WiFi screen, press cancel, and then skip.
No offense to the OP, but given the kind of questions that get asked on these root threads, s/he probably lost half the visitors at "dedicated slow router."
Blaiser47 said:
Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.
Click to expand...
Click to collapse
retyre said:
Even simpler: Choose any option on that WiFi screen, press cancel, and then skip.
No offense to the OP, but given the kind of questions that get asked on these root threads, s/he probably lost half the visitors at "dedicated slow router."
Click to expand...
Click to collapse
Great! Awesome tip!!! Even better than messing with the router - I've updated the post! XDA is no strangers to people with routers, especially if it involves blocking Amazon updates.
Curious does this work for the Fire 8? If not why?
ginfest said:
Curious does this work for the Fire 8? If not why?
Click to expand...
Click to collapse
The key difference is that the 2017 Fire HD 10 has an 'arm64-v8a' compiled system (with 64 bits), while all the older Fires are running 'armeabi-v7a' (with 32 bits). So a 64 bit bug must have slipped in. But let's be clear, if history is any guide, an Amazon update plugging this rootable bug is imminent at this point in time. That is why I urge everybody with root to disable OTA for good by renaming /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to *apk_
Unfortunately, all the other Fires seem to be on lock down, for now I have disabled updates on all of mine (including Fire TV 2 sticks) in case an exploit becomes available in the future.
bibikalka said:
Great! Awesome tip!!! Even better than messing with the router - I've updated the post! XDA is no strangers to people with routers, especially if it involves blocking Amazon updates.
Click to expand...
Click to collapse
Thanks very much for your simple approach to rooting the hd 10, starting from unboxing it, and giving step by step guide.
What apps/tweaks/settings did you do after you rooted your HD 10 that you recommend we do, you seem to have a way of writing that is concise and to the point, very much appreciated. Any other suggestions for protecting the HD 10 from Amazon OTA updates or other hazards?
Thanks again.
Are you saying at the beginning that 5.6.0.0 is or is not rootable?
encephalon9986 said:
Are you saying at the beginning that 5.6.0.0 is or is not rootable?
Click to expand...
Click to collapse
It is rootable, I clarified, thanks!
Amazing, much easier than the previous guide!
For those interested, I wrote here how to remove the Kingoroot junk: https://forum.xda-developers.com/hd8-hd10/general/added-kingoroot-t3721482
After rooting can I remove FireOS and install Oreo?
Stansted said:
After rooting can I remove FireOS and install Oreo?
Click to expand...
Click to collapse
No. That requires an unlocked boot loader and a custom oreo rom. Neither are available yet and likely will not be
This guide didn't work for me. While KingoRoot reported achieving root, I couldn't run SuperSU because the SuperSU binary is already occupied (presumably by KingoRoot's version of SuperSU).
Stansted said:
This guide didn't work for me. While KingoRoot reported achieving root, I couldn't run SuperSU because the SuperSU binary is already occupied (presumably by KingoRoot's version of SuperSU).
Click to expand...
Click to collapse
Thanks!
I was not sure if unrooting was necessary, it now looks like you should launch SuperSu from the root shell after running unroot with Kingoroot:
Unroot Fire via Kingoroot on PC
Can you try and report back?
bibikalka said:
Thanks!
I was not sure if unrooting was necessary, it now looks like you should launch SuperSu from the root shell after running unroot with Kingoroot:
Unroot Fire via Kingoroot on PC
Can you try and report back?
Click to expand...
Click to collapse
I already tried that. It didn't work. After unrooting, SuperSU won't do anything because it doesn't detect root.
Stansted said:
I already tried that. It didn't work. After unrooting, SuperSU won't do anything because it doesn't detect root.
Click to expand...
Click to collapse
How about going back to su commands - link
Yeah, so I just double-checked to make sure I hadn't made a mistake. This doesn't work. While SuperSU launches just fine from the root shell, it won't do anything after you've unrooted with KingoRoot. And if you haven't unrooted with KingoRoot, the SuperSU binary is occupied. For the record, I'm using a 7th Gen Fire HD 10 running Fire OS 5.6.0.0. I might try retyre's method later, but I don't currently understand what he's asking me to do.
Stansted said:
Yeah, so I just double-checked to make sure I hadn't made a mistake. This doesn't work. While SuperSU launches just fine from the root shell, it won't do anything after you've unrooted with KingoRoot. And if you haven't unrooted with KingoRoot, the SuperSU binary is occupied. For the record, I'm using a 7th Gen Fire HD 10 running Fire OS 5.6.0.0. I might try retyre's method later, but I don't currently understand what he's asking me to do.
Click to expand...
Click to collapse
Download the 5.6.0.0 update .bin from here, adb sideload that file, and follow these steps to the letter. It will work.