I'm stuck with only the ability to go into recovery while the rom doesn't boot and backups are stored on the uSD.
It's the Clockworkmod Recovery 5.8.3.4, and it looks like it doens't read from my uSD. I am able to connect via adb and push an other recovery.zip, that does work with the uSD, but it looks like the flashing goes ok, but when i reboot, i just end up in clockworkmod recovery 5.8.3.4 again.
adb push works to push multiple recovery.zip, but when i try with some rom.zip, i get, maybe because of the filesize, a 'protocol failure'.
I tried easyflasher 0.8.3, but it also doesn't have any effect.
Is there anyone who can help me guiding what else i can try or what the problem could be?
Try these steps
1: use adb to push a new recovery file (which you already did)
2: flash the zip
3: use the adb shell to execute the following command
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
I ran the boot loader unlock exploit successfully. Had troubles flashing recovery. I don't own a computer. Hence my dilemma. Is it possible to flash custom recovery with terminal emulator? I have searched other forums and sites for hours now. I've tried the flash_image command. And just about any other options that I've found. What am I doing wrong? Its it even possible on the RAZR M? Do I have to use fastboot? Any help would be appreciated.
Here are some flashable recoveries. I have not tried them out, but I heard they work.
http://batakang.com/ftp/?dir=devs/mhous33/XT907/recovery-flashable_recoveries
You need to use the dd command and the full /by-name path to the recovery partition in terminal from root shell.
If you download the latest TWRP recovery image for scorpion-mini and rename it to twrp.img for simplicity then place it on the root of the sdcard then you would use the following commands to write the file with dd in the terminal emulator.
su
dd if=/storage/sdcard1/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096
I strongly recommend backing up the current stock recovery first because without access to a PC you may need it to restore yours in the event of a problem.
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/storage/sdcard1/recovery_original.img bs=4096
That will save your stock recovery and you can restore it using the first command and that file as if.
My gf is on the ls980 with sprint and she is rooted on the optimus rom. twrp 2.3.4. lokified. she took the sprint ota and now the phone only boots into recovery no matter what i do. restore or load a new rom wont work. Please help..
umm
you said TWRP 2.3.4 did you mean 2.6.3.4? i know TWRP 2.6.3.4 supports OTG cables. If you have an OTG cable you could put a rom on a flash drive and it and try to flash it.
jarhead0231 said:
My gf is on the ls980 with sprint and she is rooted on the optimus rom. twrp 2.3.4. lokified. she took the sprint ota and now the phone only boots into recovery no matter what i do. restore or load a new rom wont work. Please help..
Click to expand...
Click to collapse
Search and read: http://forum.xda-developers.com/showthread.php?t=2451696
Saving LG G2 after unwanted OTA caused boot loop
doktor buknasty said:
Search and read: http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
This works on International D802. I had stock rooted rom with CWM (6.0.4.4), Xposed ( G2 Xposed, G2 tweakbox, Advanced Power Settings, App Settings), Tasker w/ Secure Settings and whatnot. So I applied OTA. Not good for the phone and the Ingress Ressistance. I was stuck at LG screen for 2 sec, reboot, rinse and repeat. Download mode was no go. Luckily I was able to enter recovery mode. Tried to restore..no luck. And after staying up till 4AM (thanx to the xda forum). I tried G2 back to stock with kdz thread. Couldn't enter download mode. I changed few USB cables, three comps and voila it entered DL mode. Unfortunately that was on Linux box...so no LG flash tool. Arghhhhh.
Next step...Linux needed, no knowledge, just sensible use of copy/paste. Enter recovery, wipe everything you can. Reboot to recovery and yes, root please. Now you should have adb. Do the following (thank you thecube)
Code:
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
If you get any errors...don't worry. I managed to execute only line 2.
Reboot to recovery w/ root and again wipe everything (it worked for me, might not be needed), and copy/paste again.
Code:
adb shell
mount /data (disregard errors)
mkdir -p /data/media/0
exit (do not forget to exit shell)
adb push rom.zip /data/media/0
adb push rom.zip /data/media/0 ( where rom.zip is up to you..i used Black Pearl ROM)
Now watch that coursor. If it is not blinking...you are almost there. When push is completed, install rom. zip as usuall.
Franketo said:
This works on International D802. I had stock rooted rom with CWM (6.0.4.4), Xposed ( G2 Xposed, G2 tweakbox, Advanced Power Settings, App Settings), Tasker w/ Secure Settings and whatnot. So I applied OTA. Not good for the phone and the Ingress Ressistance. I was stuck at LG screen for 2 sec, reboot, rinse and repeat. Download mode was no go. Luckily I was able to enter recovery mode. Tried to restore..no luck. And after staying up till 4AM (thanx to the xda forum). I tried G2 back to stock with kdz thread. Couldn't enter download mode. I changed few USB cables, three comps and voila it entered DL mode. Unfortunately that was on Linux box...so no LG flash tool. Arghhhhh.
Next step...Linux needed, no knowledge, just sensible use of copy/paste. Enter recovery, wipe everything you can. Reboot to recovery and yes, root please. Now you should have adb. Do the following (thank you thecube)
Code:
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
If you get any errors...don't worry. I managed to execute only line 2.
Reboot to recovery w/ root and again wipe everything (it worked for me, might not be needed), and copy/paste again.
Code:
adb shell
mount /data (disregard errors)
mkdir -p /data/media/0
exit (do not forget to exit shell)
adb push rom.zip /data/media/0
adb push rom.zip /data/media/0 ( where rom.zip is up to you..i used Black Pearl ROM)
Now watch that coursor. If it is not blinking...you are almost there. When push is completed, install rom. zip as usuall.
Click to expand...
Click to collapse
DOES NOT WORK says adb not found.
jarhead0231 said:
DOES NOT WORK says adb not found.
Click to expand...
Click to collapse
Are you even on Linux? And have adb / Android sdk
Sent from my LG-D802
So I did a number on my phone in a half asleep stupor I allowed an official update to go through while running a custom recovery and debloated kitkat. I can't believe I did this to myself. Is there anyway to repair the installation other than wiping the phone again? It was one of those mini updates, but now I boot straight to recovery instead of the operating system.
I am in the same boat you are man. I hit update now instead of later and the phone reboot into recovery and won't boot the ROM. I tried restoring a previous backup with no luck. I'm on a rooted stock ROM running twrp 2.7. Hope someone can shed some light on this.
I found an answer!
Gnex81 said:
I am in the same boat you are man. I hit update now instead of later and the phone reboot into recovery and won't boot the ROM. I tried restoring a previous backup with no luck. I'm on a rooted stock ROM running twrp 2.7. Hope someone can shed some light on this.
Click to expand...
Click to collapse
I found the answer in another thread after an exhaustive search. Serious thanks goes out to the user 6ril1
6ril1 said:
Have you typed the two commands in TWRP
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
and
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
?
Click to expand...
Click to collapse
Here is the thread:
[FIX] Installed TWRP and now you're stuck after OTA?
So here is what you do:
1) Boot into recovery (TWRP)
2) Go to Advanced and then Terminal Command
3) VERY CAREFULLY TYPE IN EXACTLY THIS:
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" then RETURN
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc" then RETURN
Reboot and it should have fixed it up for you.
Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE
bhattyash32 said:
Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution:
Click to expand...
Click to collapse
Seems to happen a lot with people. Could others chime in on this solution?
Sent from my LGE LG-H830 using XDA Labs
Nick216ohio said:
Seems to happen a lot with people. Could others chime in on this solution?
Click to expand...
Click to collapse
I got my phone less than 24 hrs ago and have dealt with this the entire time. Not only do I get stuck in recovery but when I do use the terminal code to get out of it, I get stuck in reboots after any ROM installation. I have seen many users having both issues and find it hard to believe there hasn't been some kind of fix. I know not all are caused by the same thing but many I'm sure are.
Boot to TWRP recovery, open Terminal inside TWRP and type:
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
Than reboot.
(May in rare causes loose TWRP but u will get out loop - be patient takes sometimes 7 Minutes+ for boot up the ROM)
Worked for me.
jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
4r44444 said:
Boot to TWRP recovery, open Terminal inside TWRP and type:
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
Than reboot.
(May in rare causes loose TWRP but u will get out loop - be patient takes sometimes 7 Minutes+ for boot up the ROM)
Worked for me.
Click to expand...
Click to collapse
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Worked for me as well, funny thing was I almost didn't search thoroughly and was going to enter the other commands.
Ducter said:
Worked for me as well, funny thing was I almost didn't search thoroughly and was going to enter the other commands.
Click to expand...
Click to collapse
+1
jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
I got in that Bootloop by doing a Factory Reset with Root and TWRP. Formatting and Flashing the LG-H85020D-Flashable.COMPLETE.zip just ended in TWRP again.
Your Command fixed that issue!
jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Thank you jeffsga88 your code worked!
Also here to give my thanks!
recovering from dding into soc devices...
@4r44444 , @jeffsga88, Thanks for the guidance here. I could get out of the TWRP recovery boot loop with the dd dumps to soc devices. You have saved my phone from bricking. Cheers for your great help and guidance to the community !!!
@jeffsga88 Where is this guide for fixing the misc parition properly? ""but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for)""
nitkam said:
@jeffsga88 Where is this guide for fixing the misc parition properly? ""but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for)""
Click to expand...
Click to collapse
The permanent fix is in the same thread as the temporary one, specifically THIS post
Nimueh said:
The permanent fix is in the same thread as the temporary one, specifically THIS post
Click to expand...
Click to collapse
Thanks for the link. It has made my almost dead phone working again.
I got stuck yesterday in that same loop your code worked for me thanks...
No such file or directory, HELP ME!! Code isn't work
nitkam said:
@4r44444
@jeffsga88 Where is this guide for fixing the misc parition properly? ""but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for)""
Click to expand...
Click to collapse
Yeah - be careful with this - I did this and bricked mine - it went from unable to boot into Android to unable to boot fullstop... eventually managed to get it restored to factory (using LGUP), but MAC addresses all reset to 0's on every reboot - so now need to run macchanger on every boot...
jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
I tried this command after flashing lineage rom on my Nexus 5x. After flashing the rom, you initially see the Lineage logo, but it never boots, it just goes on into recovery. I flashed the rom 2 times, but same effect. After this I tried the command up here from the terminal, but nothing changes. Every time I reboot, it just boots back into TWRP. What do I have to do if this command does not work? Anyone have an idea? I saw the other commands in this thread, but it seems like most people don't think it's wise to execute those, so i'm just asking to be sure.
I also tried restoring the original backup of the phone I made in the first place before flashing lineage, but that just ends up in a bootloop where I end up in a screen with the google logo and the unlock sign. I followed these instructions to the letter, but somehow the phone is now bricked.. https://wiki.lineageos.org/devices/bullhead/install
So, no ideas here? I frantically tried getting the phone to boot into the bootloader, and after I don't know how many reboots it finally responded to my holding the vol down button, and got into the bootloader. From there I was able to flash back the entire phone to factory settings (I did not want to risk having to try over and over again to get it into the bootloader) and I'll keep it at that for now. I'm pretty experienced with custom roms on several Nexus 4, 5 and Galaxy Note II, but I've never had anything like this after flashing a rom.
Worked like magic the first time around. Thank you so much your your skills and sharing it
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
[/QUOTE]
FYI: If you run into these problems when using a MediaTek powered device, replace the of= path with
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para
Enjoy!