i9070 broken lcd + after working with adb shell doesnt boot (nosound) ..

Hey xda-community,

might be a long text to read but i want to make it as detailed as possible :/.

I have an i9070 with broken lsd (+touch not working) and pattern lock.
To acces to the internal storage i hat to delete the pattern lock.
So first of all i booted into recoverymode (TWRP) and removed the pattern lock via adb shell ("rm /data/system/gesture.key").
After a reboot i was able to acces to the internal storage with my PC , finally.

But then i had the genious idea to use Droid@Screen...
Since i hadn't USB Debugging activated i tried to activate it with the adb.
I searched in the www, found something and tried it right away.
The 1st step was "adb pull /system/build.prop build.prop"
Then edit the build.prop and add the line "persist.service.adb.enable=1"
and after that i had to push ot back, but i couln't.
So i searched again in the www and found a way to mount /system ..... (prob for the false device ,_, )

The commands where:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
and
mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system

so i tried the 1st command and forgot the 4 after ext, so i typed it in the adb shell like:
# mount -o rw,remount -t ext /dev/block/mmcblk0p8 /system
and after that
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system

after that i was able to push the build.prob back, and i used
# mount -o ro,remount -t ext /dev/block/mmcblk0p8 /system
and
# mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system

afterwards.
After a reboot it kind of stuck while booting :/ (since i cant see anything i didnt heard the sound while booting).
So i tried the push back the original build.prop without the extra line.
Still not booting..

I ended trying all commands without any order:
# mount -o ro,remount -t ext /dev/block/mmcblk0p3 /system
# mount -o rw,remount -t ext /dev/block/mmcblk0p3 /system
# mount -o ro,remount -t ext4 /dev/block/mmcblk0p3 /system
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p3 /system
# mount -o ro,remount -t ext /dev/block/mmcblk0p8 /system
# mount -o rw,remount -t ext /dev/block/mmcblk0p8 /system
# mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
chmod 755 system
chmod 777 system
sync


i used also mount..../mmcblk0p3 instead of mmcblk0p8 because after using "mount" it showed behind the /system mmcblk0p3 ...
i think i messed too much around as a newbie :crying:
I am still able to use adb in recovery mode but cant acces the internal storage.

Would be nice if someone could help me :)
Ty if you read the whole text .. ^^

Adb Shell Pm Hide as much bloat and amazon as you can

I wanted to find out how much of Amazon can be stripped out from the Fire 7 without having root access. Bearing in mind that my Fire 7 is currently connected via OTG Ethernet and I have not joined Amazon and associated my device. Basically a standalone device only with OTA Update disabled via ADB Shell. Considering we do not have root yet available we are limited in options and please bear in mind that this example is for my own personal preference.

I now have a Fire 7 with the Amazon footprint removed as much as possible with the exception of services that cannot safely be hidden and the dreaded Fire Launcher. Everything else I have hidden via ADB Shell. Please see first screenshot of my stripped down Fire 7. Key essential services/programs for me such as Google Play, Google Calendar, Fire 7 Settings all work smoothly after I removed the others.

I do not need the following on the Fire 7 as I will either install my own program from Google Play or remove the service completely. The following have been hidden [Amazon Email client, Calender, Camera, Help Files, Silk Browser, Amazon Video, Amazon Music, Amazon WEather etc]

In the XDA Develpers Fire HD 6 & & Forum I came across a list of safe com.amazon processes that can be stopped on the Fire HD6 & 7 tablet. So I thought I would give them a go plus a few of my own attempts as well.
http://forum.xda-developers.com/fire...-list-t3009492

com.amazon.kindle.otter
com.amazon.kindle
com.audible.application.kindle
com.amazon.kindle.kso
com.amazon.tahoe
com.amazon.kindle.otter.oobe
com.amazon.client.metrics
com.amazon.device.backup
com.amazon.platform
com.amazon.photos
com.nuance.edr.androidservice.service
com.amazon.whisperlink.core.android
com.goodreads.kindle

I then proceeded to highlight specific services such as the Calendar, Email Client and other associated Amazon services that I do not require. I used XDA Developers and Google as a reference as to what is actually safe to hide, made a note of the actual system process name and then hid them via ADB Shell and went from there.

Attached Thumbnails