Seeking help to solve an issue with the SM-900H. Most of the time when the phone is booted into recovery by either the button combo or a recovery reboot the partitions (usually cache and data) are not detected in recovery, it will say they cannot mount. The partitions are all correct in the fstab file. Sometimes they will mount properly with no problem. I have not been able to figure out the exact cause of the issue. Happens in both Philz touch recovery and TWRP. Offering $300 for someone who can figure out or may already know the solution.
bump
Related
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
did you make a back up?
I didn't unfortunately, I can get into recovery and as long as I leave it as 'Read-Only' it seems to mount everything. I think I need to get a stock image.
Resolved - used a Toolkit to go completely back to stock, kind of scared to try again now.
Follow directions and that won't happen again. Make sure you are on the correct version MDB08K BEFORE you start (you have the OTA), format not wipe in TWRP and you won't get caught in the boot loop.
Failing to do those two things will put you in a boot loop.
What toolkit did you use because i myself have this issue with my nexus 6p
Swatto86 said:
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
Click to expand...
Click to collapse
That warning is normal, and should be ignored if you want unlocked bootloader, custom ROMs, etc.
Here TWRP couldn't mount because you forgot to decrypt after flashing the modified boot.img.
If you have further issues, let me know.
A quick advise - Avoid toolkits. They are handy and easy, but if something goes wrong, it will be hard to track down the cause. On the contrary, doing thing manually, will not only make it easy, but will also help you learn more about your Android, and how it works.
After messing up a rom flash somehow (phone was stuck on a gray screen after logo), I used the stock recovery factory reset function, but after doing so my phone is stuck in an 'erase loop'. The phone alternates between the "Erasing..." screen (with the little droid) and the "Bootloader Unlocked" screen.
I can enter the main menu for recovery mode, but if I try to go into the actual recovery mode (where you can wipe and install from sd/adb) the loop starts up again. I haven't seen this issue mentioned many other places, but the one forum I did find (for a different phone) just said to wait it out (20+ hours).
I was wondering if anyone else had ever encountered this, or if anyone had any suggestions for me.
TCZaro said:
After messing up a rom flash somehow (phone was stuck on a gray screen after logo), I used the stock recovery factory reset function, but after doing so my phone is stuck in an 'erase loop'. The phone alternates between the "Erasing..." screen (with the little droid) and the "Bootloader Unlocked" screen.
I can enter the main menu for recovery mode, but if I try to go into the actual recovery mode (where you can wipe and install from sd/adb) the loop starts up again. I haven't seen this issue mentioned many other places, but the one forum I did find (for a different phone) just said to wait it out (20+ hours).
I was wondering if anyone else had ever encountered this, or if anyone had any suggestions for me.
Click to expand...
Click to collapse
Try flashing TWRP recovery image using fastboot. I presume you have bootloader unlock otherwise you wouldn't ended up in this mess in first place.
First reboot your phone into the bootloader (POWER+VOL-) from here you can connect your phone to PC and issue fastboot commands.
Code:
fastboot flash recovery /path/to/TWRP.img
After that don't reboot the phone , just select from the already present bootloader the Recovery option... And from there try to factory reset !
If that doesn't work, and the phone doesn't boot (bootloops), you might have the /system partition messed up. At this stage get your hand on the latest Stock Firmware for your phone and flash all the system chunks (no data will be lost, but might need to wipe cache after if you get too many Force Closed)
That is for sure if you want to have stock, you could also try and flash using TWRP a custom ROM, that by itself will restore your system partition ( wipe system before flashing to be sure, by going into wipe -> Advanced -> tick System and the two Cache options and Wipe)
Hope I was clear, ask if you need more step-through details!
Thank you very much, flashing TWRP worked!
I just flashed TWRP for the first time but it comes up with "Unmodified System Partition" but touchscreen doesn't work for some reason so I cant select anything. I tried removing the battery and rebooting my phone (Galaxy S4 19505) But it just boots back into recovery for TWRP in the "Unmodified System Partition" . Please Help, thanks.
Edit: Should I delete the TWRP disk image from my pc? (My phone also keeps vibrating while turned off). I have also noticed that there is a non physical home back and menue button, did I download the wrong version? I used the TWRP app to download and flash the image.
Hi,
Download the latest image or tar from here: https://dl.twrp.me/jfltexx/ and flash it with either Odin or Heimdall.
Not quite sure about the notice, is it on the screen that asks you if you want to keep the system partition read-only? Then you either need to swipe or click ok.
Normally flashing a recovery should not produce the problems you are describing, did you only flash the recovery?
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this
I'm trying to reflash an original firmware file to a Nexus 10 but after unlocking the bootloader and restarting the bootloader it's locked again.
Can anyone shed any light on why this could be happening?
Device is stuck in a bootloop process whereby it gets so far in to setting up Android then reboots.
Googled but can find nothing . TIA
Cannot boot recovery partition failed
Hi everyone,
I have an issue,
Yesterday I tried to install LineageOS 16 and GappsPico
Since my Manta Nexus 10 only have space for 700M, I couldnt install any type of Gapps.
So I do a partition changed.
After deleting and recreating partition, I mistakenly reboot the linux kernel. So it means my Nexus doesnt have any TWRP or anything
Right now, if I pressed power + volume up - hoping to get the recovery option - which I dont get, I only got start.
Is theres a way to fix this? or its just doom for me?
really appreciate it