Database Info

Need help installing CWM

ok so i have tried all types of CWM versions and all methods and all with errors or fails. zip method failed to verify whole file signature. ADB install: succesfull pushing and installing CWM try to boot into CWM and the device just boots up without going to recovery and using the volume down power and get stock recovery. RKflash tool flash succesfull try to boot into CWM to no avail it dosent and it dosent boot in CWM neither stock just a black screen. So as you can see im all out of ideas as of how to install CWM and need help and i have an Ematic EGP007

[Q] Can't install TWRP recovery

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.

[Completed] Help! Stuck on Samsung boot screen!

Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!

Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk

dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.

Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..

In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps

I cant install TWRP on SM-P900 ;(

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.

Unable to install TWRP

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.