Hi everyone,
I retrieved a Galaxy Tab 2 10.1 GT-P5110 which has a strange behavior: it boots up correctly, but always reboots after around one minute. In order to try being able to use it, I uninstalled a few apps before it rebooted, but after the reboot the uninstalled apps were still there. After that, I tried a more radical method: I booted into the stock recovery mode, and wiped data and cache. It doesn't seem to have any effect as the tablet boots with the same customized background and all the apps are still installed.
As these steps weren't successful, I wanted to wipe everything and install a new ROM: in order to do that, I need to install TWRP. I followed the instructions of the Lineage wiki to do it, but it doesn't work. Here are the steps I followed:
Boot into download mode
Flash the TWRP image with heimdall on Ubuntu:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
Wait for download success
Reboot into recovery mode
The stock recovery is still launched instead of TWRP
I have read a lot of possible issues and tried quite everything I've read and think of:
Use heimdall with different USB ports to download TWRP to be sure that it's not an USB issue
Use different images of TWRP (and even CWM) to be sure that the recovery image is not the cause of the recovery not being installed:
Code:
TWRP GT-P5110 3.0.0-0, TWRP espresso common 3.1.1-1, CWM 6.0.5.1
Disconnect the battery between the different steps described above, and particularly after downloading TWRP in order to avoid the tablet overwriting TWRP with the stock recovery at boot
Use Windows and different versions of Odin (3.10.6, 3.11.1, 3.12.2) with the No reboot option checked to download TWRP, instead of Ubuntu and heimdall
Even flash the kernel along TWRP with heimdall:
Code:
heimdall flash --KERNEL lineage/boot.img --RECOVERY recovery.img --no-reboot
It seems that whatever I try, the TWRP recovery image is overwritten by the stock recovery after I download it. Or that the tablet is protected in some way avoiding wiping data and downloading new images.
Any ideas of what I could do to be able to install TWRP on this tablet?
dohseven said:
Hi everyone,
I retrieved a Galaxy Tab 2 10.1 GT-P5110 which has a strange behavior: it boots up correctly, but always reboots after around one minute. In order to try being able to use it, I uninstalled a few apps before it rebooted, but after the reboot the uninstalled apps were still there. After that, I tried a more radical method: I booted into the stock recovery mode, and wiped data and cache. It doesn't seem to have any effect as the tablet boots with the same customized background and all the apps are still installed.
As these steps weren't successful, I wanted to wipe everything and install a new ROM: in order to do that, I need to install TWRP. I followed the instructions of the Lineage wiki to do it, but it doesn't work. Here are the steps I followed:
Boot into download mode
Flash the TWRP image with heimdall on Ubuntu:
Wait for download success
Reboot into recovery mode
The stock recovery is still launched instead of TWRP
I have read a lot of possible issues and tried quite everything I've read and think of:
Use heimdall with different USB ports to download TWRP to be sure that it's not an USB issue
Use different images of TWRP (and even CWM) to be sure that the recovery image is not the cause of the recovery not being installed:
Disconnect the battery between the different steps described above, and particularly after downloading TWRP in order to avoid the tablet overwriting TWRP with the stock recovery at boot
Use Windows and different versions of Odin (3.10.6, 3.11.1, 3.12.2) with the No reboot option checked to download TWRP, instead of Ubuntu and heimdall
Even flash the kernel along TWRP with heimdall:
It seems that whatever I try, the TWRP recovery image is overwritten by the stock recovery after I download it. Or that the tablet is protected in some way avoiding wiping data and downloading new images.
Any ideas of what I could do to be able to install TWRP on this tablet?
Click to expand...
Click to collapse
sounds like a broken emmc
http://andi34.github.io/faq.html (scroll to the bottom of the site)
the best solution for this problem is, buy a new motherboard on ebay.
smart-t78 said:
sounds like a broken emmc
http://andi34.github.io/faq.html (scroll to the bottom of the site)
the best solution for this problem is, buy a new motherboard on ebay.
Click to expand...
Click to collapse
Thanks, it seems to be exactly my problem. Guess I will try to find a new motherboard if it's not too expensive.
Related
Can anyone tell me how I flash a recovery to the device from a zip file? Going into CWM and flashing the TWRP recovery initially seems to work, but if I then interrupt the reboot and go straight into recovery, I still see CWM, not TWRP. I'm stuck on the CWM recovery and need TWRP to try to install the Kitkat upgrade.
Should I unzip the components first and then flash the image using fastboot, or is there another way? I'm wary of fastboot as I've already (temporarily) "bricked" the Xoom by flashing a zip instead of an image that way. None of the instructions I've read has much advice on getting round installation problems.
I'm guessing the persistent CWM was caused by my selecting (at an earlier stage) the CWM option to fix the problem of the stock recovery being reinstated at each reboot. Can this be undone? Although I've installed Xoom-Universal-Root, apps that require root access - including GooManager - also fail with an access error. It's hard to tell whether the device is now rooted or not, so if there's any method of getting further without root access, that would be great.
====================
Edit: it looks as if the instructions I saw online, which mentioned two separate TWRP recoveries, were incorrect. To get Android Kitkat 4.4 onto my Xoom I didn't need the initial TWRP recovery, only the BigPart version. Once I skipped to the BigPart recovery, the problem described above did not recur.
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
light401 said:
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
Click to expand...
Click to collapse
did you also installed a rom??
No. I'm running the stock rom, no root. I just wanted to get the twrp installed because I need to copy my personal files to an sd card. My stock rom is rebooting itself after completing the normal system startup. I can barely open any app. So I need to backup my files and do a factory reset. Any ideas? Thanks!
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Ka-B00M said:
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Click to expand...
Click to collapse
That doesn't make sense. Odin exists for the exact purpose of flashing through a PC, in case your recovery or anything gets damaged.
I have unlocked the boot loader on oneplus one long back. I tried to upgrade my rom to Resurrection Remix 7.1.1
I successfully upgraded the ROM and also flashed SuperSu in it. I wanted to flash the Opengaps Aroma 7.1 and that is where I ran into issue because of my stupidity.
I found from GitHub that there were some issues with twrp versions to run the aroma installer thus I tried multiple TWRP versions via (Google play - official TWRP recovery app) by downloading them and flashing it to recovery.
I have taken the full nandroid backup but unfortunately didn't keep it on external devices. So it was in the phone itself.
Now the issue -
When I tried flashing TWRP 3.0.2.0 from existing 2.8.4.1 I tried to run the Aroma but it didn't work. Then I tried to flash the recovery with TWRP 2.8.6.1 but Aroma failed again.
However, on the GitHub there was a info stating that known working TWRP recovery on Oneplus one is of TWRP 2.8.4.1
I tried to flash that into recovery and flash the Aroma, but it didn't boot into recovery with that image. Later I restarted the phone, and again flashed the latest recovery version 3.0.2.0
From here I ran into issue. When tried again to flash the Aroma, it didn't work. So I booted recovery again and in that I selected the recovery version 2.8.4.0 for both recovery and boot partition.
After that, phone is neither booting the system nor into recovery. I don't want to loose my data (which is in phone backup) and neither want to try Aroma again. (Even if all the 900mb data needs to be deleted.).
Can the XDA members confirm can I reinstall recovery working image (2.8.4.1) once again through the adb flash recovery <image>. And boot into recovery mode so that I can delete the boot partition once again and reinstall the ROM and data ?
I tried doing that once but one of the laptops which I had access didn't recognize the adb devices. May be the driver was not working for Win10 OS. However, on my personal laptop earlier I was able to run adb commands through CMD prompt. Currently, I don't have personal laptop and may get it by next week.
Can anybody please share me the links of working android driver so that I can install them on current laptop and then try adb commands from SDK to connect my phone.
Any suggestion from members would be of great help.
Note: Please don't suggest the methods to factory reset or lock bootloader to factory settings. As I don't want to loose all my contacts and data.
If there is a way to get just recovery working on the phone, it would be of great help. So that I can wipe other partitions and rebuild it again.
Thank You.
Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.
It's an old device. I got it for free since it was just laying around in friend's home. Worked OK after factory reset with stock ROM. Wanted to upgrade Android.
Previously successfully flashed TWRP from andi34.github.io/recoveries_tab2.html for Samsung Galaxy Tab 2 GT-P3100 using heimdall on Linux. Could start the TWRP recovery. Then I followed FAQ andi34.github.io/faq.html
backup all important files (e.g. contacts) and store them on your MicroSD-Card or on your PC/Laptop
copy the rom and gapps you like to install to your MicroSD-Card (make sure Gapps match the Android version of the Rom!)
boot into your custom recovery
make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop (some of the following are named slight different depending on the recovery you use)
wipe cache
wipe dalvic cache
wipe/format system
wipe/format data
reboot your recovery once!
Click to expand...
Click to collapse
After reboot, I could no longer start recovery.
Perhaps I should not have formatted system?
Perhaps I should not have rebooted before flashing the ROM zip?
I can still enter download (ODIN) mode. Re-flashed the TWRP recovery. Rebooted. Still cannot enter TWRP. But can still enter download mode.
What do you recommend now?
Can I flash LinageOS ROM zip from andi34.github.io/roms_tab2_lineage.html using heimdall? But heimdall does not really support zip files? It's harder than that? Any guide for that?
Or do I have to re-flash the stock ROM? Can I flash the stock ROM using heimdall?
Get the stock rom for the device then use ODIN to flash the stock rom back, the stock rom should fix it as it also flashes the stock recovery back.
Did you reboot System instead of Recovery? What TWRP version was this? I also thought of scenarios like this.
Can you still boot to recovery (twrp)