you can find it in my AFH account Android File Host - Free file hosting for Android developersHi guys,
anyone with the Dirtysanta package missing from the first post?
you can find it in my AFH account Android File Host - Free file hosting for Android developersHi guys,
anyone with the Dirtysanta package missing from the first post?
you did'nt install the kernelI have a big problem, after following the guide and when booting after Step 3 the phone LCD is displaying bad like encrypted TV content what can be the reason please ?
Not sure on linux, but this tutorial is based on using Windows 10 (7 ? )Maybe I am just really stupid, but I am losing my mind over the Step1.bat. For context I have an h910 with the december 2016 software update so I highly I doubt that dirtysanta has been patched.
Here is what the terminal spits out after I run the first two instructions:
dirtysanta: 1 file pushed, 0 skipped. 14.9 MB/s (18760 bytes in 0.001s)
': remote couldn't create file: Permission deniedage/emulated/0
aboot.img: 1 file pushed, 0 skipped. 2129.9 MB/s (2097152 bytes in 0.001s)
': remote couldn't create file: Permission deniedge/emulated/0
dirtycow: 1 file pushed, 0 skipped. 94.1 MB/s (9984 bytes in 0.000s)
': remote couldn't create file: Permission deniedocal/tmp
my-run-as: 1 file pushed, 0 skipped. 120.3 MB/s (13796 bytes in 0.000s)
': remote couldn't create file: Permission deniedlocal/tmp
: No such file or directory
could not open /data/local/tmp/my-run-as
could not open /data/local/tmp/dirtycow
adb: unknown command shell
I tried running the bash as sudo and it litterally changed nothing, I did a bunch of other **** last time but then I gave up on this a few weeks ago only to pick it back up again now.
In all honestly I am just overwhelmed at this point, all I want a functional phone that isn't full of Gapps and bloatware, and honestly was not prepared for the ***** that the h910 is in this regard.
I get that it is a permissions/directory issue but don't know how to approach that as this is a stock h910 that other than having terminal emulator installed is completely untouched and obv unrooted.
Any help would be appreciated as I have dug for hours only to find nothing usefull online and also don't know who else to ask.
thx for your time
Using windows did fix the issue, I got all the way through to Step3. Thank you.Not sure on linux, but this tutorial is based on using Windows 10 (7 ? )
the error messages you posted look like you don't have permission to use the phone storage ( ge/emulated/0 ). Are you trying to run these commands in terminal on the phone ?
Its been a long time since I messed with the H910, but I can tell you it all works if you download all the correct files and do it on a windows 10 PC. All the missing downloads from this tutorial can be found in my AFH account.
Did you flash the correct MK2000 kernel ?Using windows did fix the issue, I got all the way through to Step3. Thank you.
I am now stuck on a greenscreen, so yay I bricked it, worth it tho.
Time to dig through the internet to see if this is salvagable.
Generally if anyone knows of a way to enter recovery mode from here that would be great, otherwise thanks for reading lol.
Edit: Nvm It booted into the password question, the problem I have is that the volume down button seems to be broken and adb is being useless so I cannot boot into recovery/fastboot mode. I really don't want to have to fix the button first as I don't know if it will boot into the password question again without problem.
Edit2: After messing with a thin tip of a pen around the buttons I was able to press the volume button. I tried booting into recovery but the phone just doesn't do it and on each boot the password counter counts these boots down as if they were false password attempts, this is stressfull, I am down to 15 attempt out of 30 and don't wanna mess this up.
Edit3: I got into fastboot mode and it's not TWRP but the standard android fastboot, on a scale of 0-10 how ****ed am I? I tried redoing step 3 already to no effect and adb claimes to not recognize the device.
Ok so in the mean time I did manage to get into TWRP, at some point it just offered me the factory reset, I manged to get into TWRP twice this way.Did you flash the correct MK2000 kernel ?
Did you flash 10r or 20G or 20H ?
each requires the correct kernel.
To bypass the login password screen just pull the battery out
all the files you need to make the phone work are in my AFH folders here >
Oreo > https://www.androidfilehost.com/?w=files&flid=281251
Older 10r > https://www.androidfilehost.com/?w=files&flid=281250
Everything else (TWRP,Kernels) here > https://androidfilehost.com/?a=show&w=files&flid=235271
Tip: Don't flash anything that's not for your model (H910) If your not sure don't flash it !
As to Fastboot mode ... adb commands don't work in fastboot
it's just fastboot comands
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
..etc
Tip once you get the phone working get a root reboot app to boot directly to fastboot / recovery / ect
If I recall correctly the command would beOk so in the mean time I did manage to get into TWRP, at some point it just offered me the factory reset, I manged to get into TWRP twice this way.
using the command fasboot reboot recovery just reboots the phone regularly.
On boot the phone does a Kernel panic, tho this is probably due to me flashing a ROM and has nothing do to with this thread anymore.
I assume I need to wipe the phone again and install a proper Kernel but can't boot into anything and it's really annoying. So I am back to square one at how I can get into TWRP without spending hours of my life rebooting the phone until it offers me a reset every blue moon? The fastboot command, tho a good tip, didn't work for some reason.
How do I flash the stock if I can't get into TWRP? ._.If I recall correctly the command would be
fastboot reboot bootloader
fastboot will not boot you to recovery but back to fastboot (bootloader)
thats why it's necessary to do it from the phone with a root reboot app.
stick to the AT&T roms until you figure all this stuff out, Lineage comes with it's own set of issues on this device
Well if you have TWRP on your device it means you didn't take an OTA update.can somebody tell me is it ok to flash H910 FIRMWARE WHICH THAT GUY GIVEN THE LINK ON FIRST POST IN MY LG V20 H910 10I OR 10l ID KIF IT IS L OR I TELL ME ALSO IS IT OK OR IT WILL AGAIN HARD BRICK MY PHONE LIKE IS BRICKED H918 MOTHERBOARD PREVIOUSLY I KNOW ITS TTO LATE BUT I NEED ANSWER ASAP.......
that is wut i am asking if i flash h915 20g firmware can it hard brick my phone again or it will be safe to flash in my no rooted and no twrp installed lg v20 h910 10I modelWell if you have TWRP on your device it means you didn't take an OTA update.
So I and L are both after H .. anything after H is not rooted yet.
You will have to return your phone to the H915 software to root it and install TWRP
link to rooting the H910 is in the first post
No, Theirs H910 20H why would you want H915 20G?that is wut i am asking if i flash h915 20g firmware can it hard brick my phone again or it will be safe to flash in my no rooted and no twrp installed lg v20 h910 10I model
adb logcat -s dirtysanta
STEP1.BAT
run-as con
chmod 0777 /storage/emulated/0/*
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
STEP2.BAT
STEP3.BAT
adb reboot recovery
@runningnak3d could you update the link from DirtySanta root package?