right now, just waiting for developer to crack this phone :/ so we all can enjoy full root access permanently
Upvote
0
And everything is reset back to normal upon reboot, no matter which changes you make. It's not a device worth the fight, sorry.yep, but macro app that require roots access will work still...as long you dont close app xD
Bangin'! Lemme know how it goes [emoji16]that works, ill take a look into it, i wanna see if i can find and destroy the ftm mode... i dont remember which device it was, might have been the warp 4g or something i dunno, but we figured out that you can destroy the ftm partition and then itll boot to fastboot instead, and once youre in fastboot... possibly unlock the bootloader and just boot the recovery without installing it which would bypass the protection and run it temporarily, at least allow modification of system, or if it unlocks the bootloader then hell we are in the clear install whatever the hell we want XD
shell@speed:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 196608 zram0
179 0 7634944 mmcblk0
179 1 16384 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 16384 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 49152 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 16384 mmcblk0p27
179 28 16384 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 819200 mmcblk0p30
179 31 1572864 mmcblk0p31
179 32 4456448 mmcblk0p32
179 33 65536 mmcblk0p33
179 64 4096 mmcblk0rpmb
179 128 7761920 mmcblk1
179 129 7755299 mmcblk1p1
shell@speed:/ $ ls -l /dev/block/platform/7824900.sdhci/by-name
ls -l /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1971-03-16 18:57 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1971-03-16 18:57 aboot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1971-03-16 18:57 abootbak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1971-03-16 18:57 boot -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1971-03-16 18:57 cache -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1971-03-16 18:57 carrier -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1971-03-16 18:57 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1971-03-16 18:57 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1971-03-16 18:57 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1971-03-16 18:57 hyp -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1971-03-16 18:57 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1971-03-16 18:57 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1971-03-16 18:57 misc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1971-03-16 18:57 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1971-03-16 18:57 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1971-03-16 18:57 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1971-03-16 18:57 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1971-03-16 18:57 pad -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1971-03-16 18:57 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1971-03-16 18:57 recovery -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1971-03-16 18:57 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1971-03-16 18:57 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1971-03-16 18:57 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1971-03-16 18:57 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1971-03-16 18:57 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1971-03-16 18:57 splash -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1971-03-16 18:57 ssd -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1971-03-16 18:57 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1971-03-16 18:57 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1971-03-16 18:57 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1971-03-16 18:57 userdata -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1971-03-16 18:57 ztecfg -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1971-03-16 18:57 ztelk -> /dev/block/mmcblk0p11
shell@speed:/ $
Bangin'! Lemme know how it goes [emoji16]
The ftm thing.. Wasn't that the LG Realm also?
Post note: BTW, it's good to see ya again @junkie2100 !!
Dunno, but have you tried this..??
http://androidforums.com/index.php?posts/7317521
Bahahahahah!!! hroark13 found that bit AFTER I got rid of my device.. Silly me. That's awesome on the permanent Root. Think that a TWRP will hold??ran the command hroark suggested, ran kingroot, boom, done, rebooted, still rooted
Bahahahahah!!! hroark13 found that bit AFTER I got rid of my device.. Silly me. That's awesome on the permanent Root. Think that a TWRP will hold??
If ya junkie that device, the Warp Sync is only $50 new. [emoji41]that i dont know... i assume the bootloader is still locked, BUT... theres always the ftm destruction option... im debating whether i can try it i need my phone for work but i want it so damned bad, i need a recovery before i go destroying the whole system partition lol. i dont have a backup phone but it might be worth trying still...
Sure, but I don't know which line to remove & where from..right but that is just a backup of hyp which doesnt seem to be relevant to our cause in a way we can use anyway, what im wondering is... is it even actually locked at this point or am i just flashing a bad recovery, i dont got the tools on me to modify a boot.img tho, you think you could crack the stock recovery open, change like one unimportant line of the init.rc or something, repack it and we see if that will boot?
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.