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]
Related
Hi
I have a rooted LG g5 h830
I was on 20c with NSS kernel
There was new notification of update available (20d i guess)
I pressed install and it rebooted the phone to twrp
No files were installed in twrp so I guess it didnt update
From Twrp , i chose to reboot to system but every time it reboots to TWRP
Please help
Edit:
found the fix
run these commands in the TWRP terminal (Advanced > Terminal)
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
reboot
arjunking said:
Hi
I have a rooted LG g5 h830
I was on 20c with NSS kernel
There was new notification of update available (20d i guess)
I pressed install and it rebooted the phone to twrp
No files were installed in twrp so I guess it didnt update
From Twrp , i chose to reboot to system but every time it reboots to TWRP
Please help
Edit:
found the fix
run these commands in the TWRP terminal (Advanced > Terminal)
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
reboot
Click to expand...
Click to collapse
Just so you know the above commands are actually not recommended to get out of TWRP boot loop anymore as those commands wipe the whole misc partition including your WiFi Mac address (as discussed by me and autoprime in my thread to fix the always changing Mac address issues).
To anyone stuck in TWRP, run the following command from TWRP to get out of TWRP boot loop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
This will get you out of TWRP boot loop and not wipe your while misc partition. If you already ran the previous commands and now your WiFi Mac address changes on every boot, visit my fix here:
https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841
...With a twist...
I'm in a similar situation with my h830. After trying to install a CM14.1 update, I kept having it boot into TWRP. Wiping system, or wiping everything, before trying multiple versions of CM14.1, didn't help (of course, now that I know this).
If I still had TWRP I'd be OK. The problem is that I next tried flashing the stock 20a ROM using LGUP, since I knew that if I had 20a running I could get root and re-install, and someone somewhere that the fix to the recovery loop is to reflash a ROM. However, now what happens is it keeps looping into the stock recovery instead of the custom recovery, and now I'm really stuck.
Right now, what I can do is get into fastboot mode, or get into LGUP download mode, or get into the stock recovery (which just keeps erasing things). The device is 'fastboot oem unlock'd already. If I try booting into the system, it shows the T-Mobile logo for about ten seconds and then boots back into recovery. I can flash the stock 20a ROM to heart's content but nothing changes.
Is there any way to wipe the misc partition without having TWRP? Or are there any other suggestions on how to proceed? I have the Android platform-tools, LGUP, and LG Flashtool installed.
jeffsga88 said:
Just so you know the above commands are actually not recommended to get out of TWRP boot loop anymore as those commands wipe the whole misc partition including your WiFi Mac address (as discussed by me and autoprime in my thread to fix the always changing Mac address issues).
To anyone stuck in TWRP, run the following command from TWRP to get out of TWRP boot loop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
This will get you out of TWRP boot loop and not wipe your while misc partition. If you already ran the previous commands and now your WiFi Mac address changes on every boot, visit my fix here:
https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841
Click to expand...
Click to collapse
I did this os Los 1.5.1 h830 but once it reboots google play services error come up and I cant resolve them even my reflashing with gapps???? any ideas???
Methinks, I've messed up my phone bad. Is there a fix for wiping the misc partition?
running root stock 21d and did a Factory Reset subsequently going into a boot loop
came across this thread and didn't READ it through and applied the incorrect fix
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
it wouldn't boot after that at all. display said Your device is corrupt etc and boot loader was locked
after a while:
boot loader -> flash the RS98810h_01_0303.kdz
unlock bootloader
installed twrp and flashed RS988_21d-Stock_Flashable-COMPLETE.zip
now its stuck in a boot loop. starts up normally, android upgrading till all apps complete. Then a few seconds after the boot is complete (setup process) it reboots and is stuck in the same a boot loop
I think it might have something to do with wiping the misc partition
Anyone know how to recover from that or have a backup of the misc partition to send? Or perhaps I'm off here, but that's the best I can think of
ps: I have the original MAC
If you look at the bottom of the 2nd post in this thread (https://forum.xda-developers.com/showpost.php?p=71797169&postcount=2) it has a link to info on fixing it.
tblade2 said:
Methinks, I've messed up my phone bad. Is there a fix for wiping the misc partition?
running root stock 21d and did a Factory Reset subsequently going into a boot loop
came across this thread and didn't READ it through and applied the incorrect fix
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
it wouldn't boot after that at all. display said Your device is corrupt etc and boot loader was locked
after a while:
boot loader -> flash the RS98810h_01_0303.kdz
unlock bootloader
installed twrp and flashed RS988_21d-Stock_Flashable-COMPLETE.zip
now its stuck in a boot loop. starts up normally, android upgrading till all apps complete. Then a few seconds after the boot is complete (setup process) it reboots and is stuck in the same a boot loop
I think it might have something to do with wiping the misc partition
Anyone know how to recover from that or have a backup of the misc partition to send? Or perhaps I'm off here, but that's the best I can think of
ps: I have the original MAC
Click to expand...
Click to collapse
jeffsga88 said:
Just so you know the above commands are actually not recommended to get out of TWRP boot loop anymore as those commands wipe the whole misc partition including your WiFi Mac address (as discussed by me and autoprime in my thread to fix the always changing Mac address issues).
To anyone stuck in TWRP, run the following command from TWRP to get out of TWRP boot loop:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
This will get you out of TWRP boot loop and not wipe your while misc partition. If you already ran the previous commands and now your WiFi Mac address changes on every boot, visit my fix here:
https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841
Click to expand...
Click to collapse
guys, Lenovo Tab 4 10 here, I've tried using Jeff's command in TWRP terminal, but I'm getting "dd: conv option disabled". What should I do now?
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.
Hi,
this is a small tutorial to show you how to flash the recovery, also eRecovery, via command line / adb shell within Android.
Flashify and other apps never worked for me, so I used commands to flash it without the need of fastboot.
It's a small tutorial for those who never worked with commands like this.
Please notify me if something went wrong or if you found any other issues.
I wanted to make a small script but I stopped it because of the lack of available commands in Android.
DISCLAIMER:
Read this tutorial first.
Never flash custom recovery to eRecovery.
Never flash recoveries from different devices.
Don't try to flash other partitions with this commands if you don't want to risk a brick.
Requirements:
- Oreo / EMUI 8 installed, Nougat hast other partition names. Pie isn't supported by me until final release.
- working root access
- terminal emulator app (I recommend Termius, it's easy to use and has nice features, it's free to use)
> or a PC, and USB cable and working ADB, also USB Debugging enabled in developer settings
- recovery img files on your phone, I recommend it to put them into your user root /data/media/0/ (internal memory)
NOTE: All commands are case sensitive!
Now open your terminal app or open the adb shell.
Type following command to enable root access:
Code:
su
SuperSU will ask you for root access, grant it.
Following command is needed to figure out, which type of memory your phone has:
Code:
ls /dev/block/platform
There are two possible outputs:
If you've a device with the faster UFS memory, it's ff3b0000.ufs, if eMMC it's hi_mci.0.
From now I'll write MEMORY instead of ff3b0000.ufs or hi_mci.0.
For flashing the recovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/RECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/recovery_ramdisk_a
Example: dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
The output should look like this:
Code:
65536+0 records in
65536+0 records out
33554432 bytes transferred in 0.247 secs (135847902 bytes/sec)
If not, check your command and file paths.
For flashin the eRecovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/ERECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/erecovery_ramdisk_a
Example: dd if=/data/media/0/ERECOVERY_RAMDI.IMG of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
IMPORTANT NOTE: DO NOT INSTALL TWRP IN THIS! Flash only stock eRecovery!
The dd command won't give you any progress output, so be a bit patient. It should be done in a few second, but don't close the terminal app or connection before you got any output.
Unix systems like Android will give an output if something went wrong, always.
I use this to flash new TWRP versions or to flash stock recovery before I update.
If you recently updated your phone, you still need to flash via fastboot, because you lost root during the update.
The dd commands also work with fastboot. Mostly you'll use "fastboot flash recovery_ramdisk", but if you need to flash eRecovery, you can use the dd command.
23. February 2019:
Pie should also work, but you have to remove the "_a" after the partition name.
Example:
dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk
Please report if it's working or not.
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
fr3ker said:
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Jannomag said:
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Click to expand...
Click to collapse
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
M1chiel said:
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
Click to expand...
Click to collapse
Also my thought, I wanted to add this to the requirements when I created this post but apparently I forgot this. Now it's added as first point.
Hi.
I have a hard bricked p10. When I connect to laptop it's says USB SER. It doesn't not turn on I can't access recovery with power + vol. I can't get into fastboot. Anyway I can access fastboot to flash kernel and erecovery?
Jannomag said:
I use this to flash new TWRP versions or to flash stock recovery before I update.
Click to expand...
Click to collapse
Is it mandatory to flash stock recovery before update? Is it applies only to ota update or ff method?
Yes, FF or OTA are using stock recovery to flash the update. With TWRP it won't work.
Updated?
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Blümchen Blau said:
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Click to expand...
Click to collapse
WTF....Why didn't I notice this terrible mistake! Thank you for reading my post completely, you're 100% correct, I'll correct this directly after I submit this post.
Huawei did also a small change at naming the recovery partition, which I'll update, too.
I had also the problem that I wasn't able to boot into fastboot by command before I fried my phone - I couldn't figure out the reason for this.
Again, thank you!
Jannomag said:
Again, thank you!
Click to expand...
Click to collapse
Your'e welcome! I did update now, but didn't need your (correct ) way to fastboot, because the method described by borgerapper did the trick for me to get into fastboot and flash the needed original recovery.
Thanks anyway!
I originally followed this thread LG V521 Root Guide and successfully rooted and installed Nougat on my LG V521.
I had to uninstall a module (Smalipatcher) from magisk recently because it wouldn't allow the phone to boot up. After uninstalling the phone wouldn't boot past recovery so i did a system format and now every time it boots it goes to recovery.
I tried flashing a stock LG Rom on it via sideloading...it says it worked successfully but still wouldn't boot up. I then ran these commands through terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
as found in another thread.
The phone successfully boots up but then tells me the encryption was unsuccessful and the tablet needs to be reset...which just brings me back to booting up to TWRP. I've been trying different things for two days and none have worked. Can anyone give me an idea of what else to try?