Hi guys I've successfully rooted my Lg L9 P768 using this guide http://forum.xda-developers.com/showthread.php?t=2173465
I made a mistake when I tried to root another LG L9 device because a I didnt used related Hex-Edited BIN file and KDZ file.
The device stop on screen with android logo and a red mark exclamation.
How can I do?
willep86 said:
Hi guys I've successfully rooted my Lg L9 P768 using this guide http://forum.xda-developers.com/show....php?t=2173465
I made a mistake when I tried to root another LG L9 device because a I didnt used related Hex-Edited BIN file and KDZ file.
The device stop on screen with android logo and a red mark exclamation.
How can I do?
Click to expand...
Click to collapse
Enter S/W mode http://forum.xda-developers.com/showthread.php?p=36069646#post36069646 and you will be able to restore your phone with lg tool or offline method
Lelus said:
Enter S/W mode http://forum.xda-developers.com/showthread.php?p=36069646#post36069646 and you will be able to restore your phone with lg tool or offline method
Click to expand...
Click to collapse
Hi, thank you! But I cant access SW mode (with Vol UP + Power).
I used a diferent kdz file and on step 11 I've just replaced "LGP768_AP[6].bin" availble in the guide.
Do you know what could be happened witth the device?
willep86 said:
Hi, thank you! But I cant access SW mode (with Vol UP + Power).
I used a diferent kdz file and on step 11 I've just replaced "LGP768_AP[6].bin" availble in the guide.
Do you know what could be happened witth the device?
Click to expand...
Click to collapse
Are you familiar with adb ?
You can dump x-loader and u-boot from your working rooted p768 by doing following :
Code:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
then follow this thread starting with #34 except use your own p1 and p2
Lelus said:
Are you familiar with adb ?
You can dump x-loader and u-boot from your working rooted p768 by doing following :
Code:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
then follow this thread starting with #34 except use your own p1 and p2
Click to expand...
Click to collapse
I'm sorry. Adb is not familiar for me.
Could you explain how to do or suggest another way?
Thank you again.
willep86 said:
I'm sorry. Adb is not familiar for me.
Could you explain how to do or suggest another way?
Thank you again.
Click to expand...
Click to collapse
Hi Lelus, thank you. I successfully recovered the phone.
Related
Hi,
another leaked ICS rom from Huawei (leaked here, thx @ th.f from AndroidHilfe.de). Download mirror: http://84.23.79.243/downloads/
There is a .rar file which contains the dload folder and a fastboot flashable boot.img that allows to adb remount and push a su binary.
Have fun!
mblaster
Could you please provide instruction for the boot.img?
lilaliend said:
Could you please provide instruction for the boot.img?
Click to expand...
Click to collapse
You need a working fastboot and adb to fully root the tablet with this. If you don't have it configured yet please search how to do it, there are lots of tutorials for that. Make sure you read them carfully, it's possible to totally screw your tablet if something goes wrong.
1) Boot into fastboot mode (hold vol- while booting the tablet) -> Screen says Fastboot bla bla...
2) fastboot flash boot B010SP03-rootboot.img
3) fastboot reboot
4) adb remount
5) adb push su /system/xbin/su
6) adb shell chmod 6755 /system/xbin/su
7) Install Superuser from Play Store
8) ???
9) Profit!
You will find the su binary in the download folder from my first link in a few minutes.
mblaster
Thanks for the files and instructions.
Hey.. so still a newb Droid tablet owner.. I did the 06 and then 08 build update, simply by throwing the dLOAD file in a SD card and rebooting. I assume the same with this build and is it worth it to migrate from 08?
Thanks!
Confirmed by me, working root (Did this tonight and works!):
http://forums.hardwarezone.com.sg/t...pad-3g-7-tablet-now-singapore-3384632-63.html
can anybody please upload a dload folder with root image complete i cant adb because I have no contact with the mediapad in fastboot
Just use the solution above from me. You don't need adb or fastboot!
I couldn't connect with adb either. So i went looking for another solution.
Good luck!
Eek
eekbb said:
Just use the solution above from me. You don't need adb or fastboot!
I couldn't connect with adb either. So i went looking for another solution.
Good luck!
Eek
Click to expand...
Click to collapse
I cant make that work either, if I exchange the boot.img I get FAIL on the mediapad when flashing so If any1 have a working dload with the rooted img without the games I would be happy.
stinger32 said:
I cant make that work either, if I exchange the boot.img I get FAIL on the mediapad when flashing so If any1 have a working dload with the rooted img without the games I would be happy.
Click to expand...
Click to collapse
Do you still need it? If so I will put it online for you.
Anyone please direct me on how to remove cwm recovery and go back to stock recovery?
I have the tmo p769 on 4.1.2
chispas109 said:
Anyone please direct me on how to remove cwm recovery and go back to stock recovery?
I have the tmo p769 on 4.1.2
Click to expand...
Click to collapse
are you rooted ?
Lelus said:
are you rooted ?
Click to expand...
Click to collapse
Yes i am.
chispas109 said:
Yes i am.
Click to expand...
Click to collapse
just to be sure you aren't talking about cwm recovery from http://forum.xda-developers.com/showthread.php?t=2095825 are you ??
download p769 stock recovery and copy it to your sdcard then do following
from your pc :
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p4_769.img of=/dev/block/mmcblk0p4
or phone :
Code:
su
busybox dd if=/sdcard/external_sd/p4_769.img of=/dev/block/mmcblk0p4
Lelus said:
just to be sure you aren't taking about cwm recovery from http://forum.xda-developers.com/showthread.php?t=2095825 are you ??
download p769 stock recovery and copy it to your sdcard then do following
from your pc :
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p4_769.img of=/dev/block/mmcblk0p4
or phone :
Code:
su
busybox dd if=/sdcard/external_sd/p4_769.img of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
Yes i am talking about that recovery. The locked bootloader cwm recovery. So i follow these directions?
chispas109 said:
Yes i am talking about that recovery. The locked bootloader cwm recovery. So i follow these directions?
Click to expand...
Click to collapse
You can use file manager to do this
remove /system/bootstrap directory
remove /system/bin/e2fck
rename /system/bin/e2fck.bin to e2fck
Lelus said:
You can use file manager to do this
remove /system/bootstrap directory
remove /system/bin/e2fck
rename /system/bin/e2fck.bin to e2fck
Click to expand...
Click to collapse
Thanks a lot your help.
Hi everyone,
So after deciding whether to do it or not, i finally unlocked my BL yesterday. At least when i dial the secret number and look at BL info, it says "UNLOCK".
But I've been trying to flash cwm and rooting but it seems my device is not being recognised in cmd.
And i am having difficulties to install fastboot drivers again because my device is not showing up at all in device manager.
If you could kindly list some simple instructions on how to flash cwm and rooting on unlocked BL (Before you ask, yes i went through all the guides with no avail) or help me to install flashboot drivers properly, it would be appreciated.
Thank you and good day.
EDIT 1: I can boot in fastboot mode, But when i do adb devices, driver installation fails and thus the command for flashing cwm says "waiting for device" and never flashes.
EDIT 2: From what i have searched from previous posts , i need to wait 30mins, I will do that and report.... Hopefully it will work
If you can boot into fastboot then do fastboot devices, adb devices are commands in adb mode, not fastboot mode, instead of flashing through adb use fastboot flash , hope I help!
Sent from my LG-P769 using xda app-developers app
EpicLordPhone said:
If you can boot into fastboot then do fastboot devices, adb devices are commands in adb mode, not fastboot mode, instead of flashing through adb use fastboot flash , hope I help!
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Sorry,
I actually did what u said.
But when i type the command (in cmd) : C:\Android>fastboot devices ---> The command is accepted and there is a driver installation which fails.
Even then i continued and typed : C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
But with the second command, it simply says "waiting for device" in the command window, but nothing happens.
kirakun said:
But with the second command, it simply says "waiting for device" in the command window, but nothing happens.
Click to expand...
Click to collapse
Put recovery.img on sdcard
Using Android Terminal Emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
P.S Sorry my ENG
Lgeob said:
Put recovery.img on sdcard
Using Android Terminal Emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
P.S Sorry my ENG
Click to expand...
Click to collapse
But I only have an unlocked BL and I do NOT have root either :/
kirakun said:
But I only have an unlocked BL and I do NOT have root either :/
Click to expand...
Click to collapse
What prevents get root?
Lgeob said:
What prevents get root?
Click to expand...
Click to collapse
When i enter fastboot mode, pc installs drivers but driver installation fails. Cannot use fastboot commands. I try to re-install fastboot drivers (omap4boot drivers) but i cannot find device in device manager
kirakun said:
When i enter fastboot mode, pc installs drivers but driver installation fails. Cannot use fastboot commands. I try to re-install fastboot drivers (omap4boot drivers) but i cannot find device in device manager
Click to expand...
Click to collapse
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Lgeob said:
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Click to expand...
Click to collapse
okay ill try this
Lgeob said:
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Click to expand...
Click to collapse
I don't have spritebud, so LGPwn.apk does not work
kirakun said:
I don't have spritebud, so LGPwn.apk does not work
Click to expand...
Click to collapse
Try this method.
Casserole said:
Try this method.
Click to expand...
Click to collapse
Thanks for the reply ^^ I was planning to use this as last resort XD Do u think its reliable o-o?
And also after installing this i can flash cwm ?
kirakun said:
And also after installing this i can flash cwm ?
Click to expand...
Click to collapse
Do it.Не ссы :good:
Tying to install a rom. keep getting this error on cwm. Im stuck in Cwm recovery loop. LG G2 (D802). Installing from otg as pc will not find phone. using adb to push rom
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
Keep it simple (Noob Friendly)
donation for fix
Thanks hope you can help
FIXED
if anyone is stuck here is the ADB command that fixed my phone.
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
hope it helps
hayjoesam said:
if anyone is stuck here is the ADB command that fixed my phone.
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
hope it helps
Click to expand...
Click to collapse
You know there's a LG G2 section right? And there's also an irc channel for these types of things.
Sent from an Xposed LG-G2/LS-980
Hi everyone,
i have the problem that i tried to install custom rom over twrp recovery ( root installed also ).
Installation starts and finishes.
On Reboot i always get back into recovery....
No chance anymore to install any custom rom.
What can be done to solve this ?
FranzB said:
Hi everyone,
i have the problem that i tried to install custom rom over twrp recovery ( root installed also ).
Installation starts and finishes.
On Reboot i always get back into recovery....
No chance anymore to install any custom rom.
What can be done to solve this ?
Click to expand...
Click to collapse
Just LGUP kdz bro
Sent from my LGE LG-H830 using XDA Labs
Hi
thks for answer But i get error message "no handset .... " when starting lgup
FranzB said:
Hi
thks for answer But i get error message "no handset .... " when starting lgup
Click to expand...
Click to collapse
Search for dd commands in the CM 14.1 thread on one of the last few pages. I've used these on my g3, g4 and G5 and its worked to reboot to system.
FranzB said:
Hi
thks for answer But i get error message "no handset .... " when starting lgup
Click to expand...
Click to collapse
You try flashing Twrp update? I did and started getting bootloops
Sent from my LGE LG-H830 using XDA Labs
It's been confirmed if you bootloop twrp
Connect usb then on computer run adb shell
And the 2 commands at bottom of op posts bout rooting: http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
They're the 2 commands beginning with dd one at a time and hit enter. Also, skip running su command. No need in recovery it's already good to go just copy/paste each one in to a command prompt with adb shell and should fix just bought phone today and saw this myself.
RealPariah said:
It's been confirmed if you bootloop twrp
Connect usb then on computer run adb shell
And the 2 commands at bottom of op posts bout rooting: http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
They're the 2 commands beginning with dd one at a time and hit enter. Also, skip running su command. No need in recovery it's already good to go just copy/paste each one in to a command prompt with adb shell and should fix just bought phone today and saw this myself.
Click to expand...
Click to collapse
Thank you very much bro. These two dd commands did it for me. But my directory was different .../platform/soc/624000.ufshc
I also have this problem after I tried to flesh H850 20A OPEN EU.
You can maybe explain to me how you overcame it ??
yossiyemin said:
I also have this problem after I tried to flesh H850 20A OPEN EU.
You can maybe explain to me how you overcame it ??
Click to expand...
Click to collapse
I installed H850 20 A too. But i always got into twrp after reboot.
I connected my lg with pc ( usb ). In TWRP "Advanced" - "Terminal" i wrote these two dd statements.
First i got error - directory was wrong !
I did these two statements one after another:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
and afterwards
reboot
Without entering twrp my phone installed H850 20A OPEN EU
Btw: My phone was locked again after this procedure and i had to unlock again, install twrp and supersu
RealPariah said:
It's been confirmed if you bootloop twrp
Connect usb then on computer run adb shell
And the 2 commands at bottom of op posts bout rooting: http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
They're the 2 commands beginning with dd one at a time and hit enter. Also, skip running su command. No need in recovery it's already good to go just copy/paste each one in to a command prompt with adb shell and should fix just bought phone today and saw this myself.
Click to expand...
Click to collapse
Absolutely awesome advice/info - THANKS Pariah! :good:
I did the exact command on a h850 with linage and twrp and now I get a phone is corrupt and will not boot message. I hate this phone so much.
FranzB said:
Hi
thks for answer But i get error message "no handset .... " when starting lgup
Click to expand...
Click to collapse
Use UpperCut for flashing by LGUP
FranzB said:
I installed H850 20 A too. But i always got into twrp after reboot.
I connected my lg with pc ( usb ). In TWRP "Advanced" - "Terminal" i wrote these two dd statements.
First i got error - directory was wrong !
I did these two statements one after another:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
and afterwards
reboot
Without entering twrp my phone installed H850 20A OPEN EU
Btw: My phone was locked again after this procedure and i had to unlock again, install twrp and supersu
Click to expand...
Click to collapse
Be careful, I completely bricked my phone attempting this.... only boot option was to go into the "Software Updating" screen. There was no working OS / Recovery / Fastboot at all.
Previously I've used LG Bridge to do full restore to LG stock image, then start again with OEM unlock, TWRP and then Lineage, but LG Bridge couldn't recover it (or detect it!) and although LGUP would detect it, it took me down a pretty long and messy path of having to download a lot of utilities to convert the stock image to something that LGUP would use and that kept failing 5-10% in to the update... so I ended up sending the phone off to be restored by somebody else (and cost myself £80).
FranzB said:
I installed H850 20 A too. But i always got into twrp after reboot.
I connected my lg with pc ( usb ). In TWRP "Advanced" - "Terminal" i wrote these two dd statements.
First i got error - directory was wrong !
I did these two statements one after another:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
and afterwards
reboot
Without entering twrp my phone installed H850 20A OPEN EU
Btw: My phone was locked again after this procedure and i had to unlock again, install twrp and supersu
Click to expand...
Click to collapse
Hey,
i also ran into a revocery bootloop and just tried out you two commands. Both replied something like "no space left...". After rebooting the phone now i am stuck with a even worse bootloop saying
[750]
[800]
[850] Boot verfifaction fail
[900] - cause MISMATCH_SIG_LEN
[950]
[1000]
I am not even able to boot into Recovery any more.....Is it now trash?!
I was able to recover it after hours of google and several tools and combinations of it when i finally found a solution that worked. Hopefully nothing is broken in the back that will "fall on my feet" someday...
!!! Solution !!!
Hi,
Today I faced the same problem and after google-ing and reading trough the forums I found the right command that has to be used in this case scenario, which I tried and all worked like a charm!
So if anybody faces twrp bootloop enter this inside terminal window in twrp:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Using the first commands staded above wipes your misc partition and then you end up with a Mac address that changes in every reboot!!! So don't use the first two commands stated above and use this one I posted here. Credits goes to jeffsga88 !!!
Thanks !
Yesterday I encountered the same bootloop after trying to perform an update from LineageOS 14.1 Nightly 20171024 to 20171031 through the system settings menu.
I had tried to wipe all partitions through TWRP and reinstalling the stock ROM, following a forum post (I don't find the link any more, sorry). This did not help.
I hesitated to use dd due to the reports that some phones were bricked after them. Then I found a description on teamsuperluminal dot org (the forum prevents me from posting the exact link) about the same issue occuring on a Xiaomi device; the commands proposed there only owerwrite the first 32 bytes of the two block devices, instead of 512 bytes / respectively everything. I tried to adapt it to the H850 case, as this was the least invasive option I found by a quick search.
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc bs=32 count=1
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota bs=32 count=1
This worked.
My setup:
- LG G5 (H850) EU
- TWRP 3.1.1-0
As this seems to be some kind of delicate issue, I would be curious about what I was actually doing with this. So I overwrote the first 32 bytes of the aforementioned two block devices with zeroes. What are these devices suppposed to contain? Where during the boot process are they read? What might be especially important not to owerwrite? I believe this can get into details quite quickly... but is there maybe any "high level" explanation how this works?
- wemi
recovery bootloop after LOS14.1 manual update (to 14.1-20171226-NIGHTLY-h850 via OTA) on G5-H850 EU with newest TWRP.
used only the first command from wemi, post #17 (on .../misc partition, with bs=32) in TWRP terminal, tried reboot and the problem seems to be solved. no idea why so no guarantee, of course.
Hi, I also got the recovery bootloop after using the dm-verity patch to decrypt the data partition. Can thus confirm that the first commands (overwriting "everything") lead to a corrupt phone and wemi's command let me restore it.
[deleted the rest, because I am obviously an idiot. If the problem proves to not be solved by being less of an idiot, I will edit the post once more and give more details]