Hello,
Basically my prime was running fine, GooManager then told me to update gApps which i then did. And now my device will only boot into Recovery. It totally skips the bootloader screen, and even holding down just goes into recovery.
I did manage to fix it using the following command:
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
But then i accidentally flashed the gApps again (i know, I'm an idiot)
I could just run the command again and fix it, but adb will not run. Just keeps saying device not found. The drivers are installed, and it shows up in Device Manager fine.
Any ideas on what to do?
Scottymeuk said:
Hello,
Basically my prime was running fine, GooManager then told me to update gApps which i then did. And now my device will only boot into Recovery. It totally skips the bootloader screen, and even holding down just goes into recovery.
I did manage to fix it using the following command:
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
But then i accidentally flashed the gApps again (i know, I'm an idiot)
I could just run the command again and fix it, but adb will not run. Just keeps saying device not found. The drivers are installed, and it shows up in Device Manager fine.
Any ideas on what to do?
Click to expand...
Click to collapse
try to uninstall the drivers and install again
leime68 said:
try to uninstall the drivers and install again
Click to expand...
Click to collapse
Thanks for your reply.
I have done many times Doesnt seem to want to work at all. I dont know what to do
Related
after downgrade to .15, root , instnall cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.It lets me backup from recovery but when i reboot again it takes me back to recovery.I am totally inexperienced in these things.If someone can make a small program for me to making my asus prime 201 to work again i donate to him $100.
chasosa said:
after downgrade to .15 root install cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.
Click to expand...
Click to collapse
Uh oh lol, kinda sounds like boynamedstacy's issue. Maybe not though, you could try whatever methods he was unsuccessful with and hopefully you're not bricked.
chasosa said:
after downgrade to .15 root install cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.
Click to expand...
Click to collapse
first of all install the naked drivers and search for a workimg adb.
then connect your tablet with you pc and make sure your prime is in recovery.
open up your cmd (make sure you are on win7) and typ: adb shell
now: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 hit enter.
now typ: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 enter.
exit cmd and now reboot via cwm.
if it stuck on the eee pad screen, just typ in the adb: adb push romname \sdcard\ romname again.
now flash the rom and your done.
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]
I was in Nougat with root. I tried to encrypt the phone after root.. Big mistake, it was stuck in T-Mobile splash screen for a while. It was not showing encryption progrress. So, I rebooted the phone by pulling the battery out and it asked me to reset the phone.
Booted into TWRP and formatted the file systems and reinstalled ROM. When I reboot, it ONLY boots to TWRP. Tried few tricks but nothing worked. Every time, it only boots to TWRP.
Any ideas? Tried booting to bootloader and oem lock/unlock but nothing helped. Frustrating!
There has to be an easier way to get out of TWRP but simply wouldn't budge!
RainGater said:
I was in Nougat with root. I tried to encrypt the phone after root.. Big mistake, it was stuck in T-Mobile splash screen for a while. It was not showing encryption progrress. So, I rebooted the phone by pulling the battery out and it asked me to reset the phone.
Booted into TWRP and formatted the file systems and reinstalled ROM. When I reboot, it ONLY boots to TWRP. Tried few tricks but nothing worked. Every wtime, it only boots to TWRP.
Any ideas? Tried booting to bootloader and oem lock/unlock but nothing helped. Frustrating!
There has to be an easier way to get out of TWRP but simply wouldn't budge!
Click to expand...
Click to collapse
Ok, found a solution for those who are in the same boat as me.
Boot to TWRP recovery, open Terminal inside TWRP and type:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Reboot and voila, it works! Whew! So much trouble after a failed encryption.
THANK YOU!!!!
Had the same issue! You're a life saver!
RainGater said:
Ok, found a solution for those who are in the same boat as me.
Boot to TWRP recovery, open Terminal inside TWRP and type:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Reboot and voila, it works! Whew! So much trouble after a failed encryption.
Click to expand...
Click to collapse
I installed Oreo ROM and got stuck in TWRP. That command fixed it and let me go back to Nougat.
Thanks it worked!
Thanks Dear
Just to confirm again, It woked for me.
Thanks buddy
RainGater said:
Ok, found a solution for those who are in the same boat as me.
Boot to TWRP recovery, open Terminal inside TWRP and type:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Reboot and voila, it works! Whew! So much trouble after a failed encryption.
Click to expand...
Click to collapse
You are a Genius it worked on T-mobile Lg v10 coming from flashing KDZ in TWRP Nougat 7.0
love you man, you safed me a LOT of time. just did a complete wipe with twrp, restored the backup and the V10 always booted in twrp. i had this before but too long ago to remember. found your terminal code by looking around. lucky me. thanks man, have a cold one on my bill greetings
RainGater said:
Ok, found a solution for those who are in the same boat as me.
Boot to TWRP recovery, open Terminal inside TWRP and type:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Reboot and voila, it works! Whew! So much trouble after a failed encryption.
Click to expand...
Click to collapse
Cud this work for naugat stuck on samsung logo and error about cannot find boot device by name. Etc. No such file or directory
I've factory reseted Fulmics ROM but phone won't boot into system any more. Every time it boots into TWRP recovery. I did updated TWRP to the latest one, Flashed different roms but it didn't help. It still reboots into TWRP. What am I doing wrong?
Looks like your misc corruption might have corrupted. Go to twrp and open up an adb shell or terminal and enter the following:
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
You should be able to get out of twrp, but if you are using lineageOS, your Wifi may not work. To fix this, read this: How to fix mac reboot
Thanks! Will go from there and report back.
miguelsanchez79 said:
Thanks! Will go from there and report back.
Click to expand...
Click to collapse
DON'T do what the guy above you said to do. First, update twrp to 3.2.1-1 so this doesn't happen again. Second, use the more targeted command to fix your problem, which was in the link the guy above you posted but for whatever reason he didn't read himself.
autoprime said:
Command to safely get out of stuck TWRP would need to be updated for the G5:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
solution is very simple. In TWRP go to "Advanced" and then do "Fix Context". Enjoy
shunjou said:
DON'T do what the guy above you said to do. First, update twrp to 3.2.1-1 so this doesn't happen again. Second, use the more targeted command to fix your problem, which was in the link the guy above you posted but for whatever reason he didn't read himself.
Click to expand...
Click to collapse
Thanks for the warning! I'll see what I can do with it.
dazbor said:
solution is very simple. In TWRP go to "Advanced" and then do "Fix Context". Enjoy
Click to expand...
Click to collapse
I did try rhat already but didn't work
UPDATE.
Running above commands in terminal corrupted my phone.
I did bring it back to live using this tutorial: https://forum.xda-developers.com/lg-g5/help/device-corrupt-trusted-boot-t3669330/page2
Thanks for your help everyone.