My device is a Samsung A12 model SM-a127m, I unlocked the bootloader and installed root through Odin following several tutorials on this forum. My initial and current goal is to install LineageOS on the phone and the moment I'm stuck with is installing TWRP or any custom recovery.
I went from forum to forum looking for files to install through Odin, I tried as AP all the ones I could find one by one and what happens is that the phone works, I can enter the download mode and I can start Android but I cannot start the mode recovery, neither the TWRP nor the original stock, when I try to enter the screen simply goes black.
The output of the "adb devices" command says that my device is in recovery mode but TWRP is not showing up and I don't know any other way to install Lineage.
Related
Hello everyone!!
After doing a lot of extensive research I finally decided to flash Cyanogenmod 11 on my device (btw it's Moto G XT1033). I followed all the instructions of an xda member. Unfortunately my phone fails after flashing the recovery image. It shows on the cmd prompt that the flashing was successful but everytime I go to recovery mode I am no longer able to access the recovery.img
All I get is a blank screen with occasional blanks, freezes and various types of patterns on the screen. I followed each and every instruction to the letter still I do not know why this is happening. cannot even access the default bootloader now!
Here are the steps I used:
1. Unlock the bootloader
2. Installed adb and fastboot and copied the img file to the adb directory
3. Restarted my phone to the boot menu
4. used the command "fastboot flash recovery recovery.img"
5. got a message that the operation was successful.
However after these steps, I am unable to access the cwm bootmenu. Even the default one is no longer accessible.
Please help!!!:crying::crying:
After flashing recovery, do not reboot the phone. Use the phone's volume buttons to enter fastboot from the phone's fastboot menu.
I would install trwp instead.
I agree on Kannz2's suggestion for TWRP.
AFAIK, the recovery you're trying to flash is closed sourced and is no longer being updated.
Here's a link to TWRP:
http://techerrata.com/browse/twrp2/xt1032
Link to ADB and Fastboot that I use:
http://forum.xda-developers.com/showthread.php?t=2588979
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
basically this is my first time trying to flash a custom recovery and after a while of trying multiple methods, none worked
i have firstly install adb,unlocked the bootloader and enabled usb debbuging
the first approach was from xda site following the tutorial, the adb reboot bootloader command just normally restarted the phone and wouldnt put me into bootloader mode, then after manually going to bootloader mode i tried to flash the img with no luck at all and the phone wasnt showing up on adb devices aswell on bootloader mode
then i tried using odin and gave it the tar file but never completed the flashing so im kind of stuck not being able to flash twrp and root the phone aswell so id appreciate your help
thanks for your time
edit: after trying again today and looking at the log, whenever i use odin it will either stop at setupConnection or recovery.img, the phone is also a galaxy j3 SM320FN
check the drivers while in download mode. fastboot devices shows you the phone while in download mode, adb devices shows you the phone while in system mode. these are different drivers. from fastboot you can boot the recovery.img without flashing for testing purposes
While installing TWRP on my Samsung tab, my tablet shut off and I got this error. So after tons of research, I want to help the people that come into this problem!
Case 1:
Can't boot into the device but can boot into download mode or recovery
Solution:
Simple, go into download and use Odin/ADB to flash stock ROM.
Case 2:
Can't boot into device, download mode, or recovery
Solution:
Download ADB, and run "ADB devices"
If it shows a device, you're in luck, use "ADB reboot bootloader" and use Odin/ADB to flash stock ROM.
If it does not show up, try these tricks: https://technastic.com/samsung-download-recovery-mode/
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
luka0954 said:
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
Click to expand...
Click to collapse
Just to be sure, do you have USB debugging enabled?
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
I do, and of course I went and enabled it again after I bootloaded the device
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
You said you tried volume down+power, on most devices, that is the combination to boot into bootloader mode, fastboot mode or download mode, depending on the device. Volume up+power is generally the combination to boot into recovery mode. This doesn't seem to be your issue though. Are you sure you flashed TWRP to the correct partition? If your device is an A/B partitioned device, you may have flashed to one of these partitions when you needed to flash to the other partition.
Try flashing a copy of your stock recovery then see if that repairs the recovery partition and allows stock recovery to boot. If it works correctly after flashing stock recovery, you may not be flashing TWRP correctly or the actual flash might be being blocked by something that you're overlooking. Are you certain that your bootloader is unlocked?