I tried pretty much everything now, CWM, TRWP, PhilZ, all the same result: recovery is not sticking when I flashed via Odin (3.07). I just get the normal recovery and the download counter increases, so drivers are out of question. When I try to flash via .zip it says the file isn't signed. I hope someone can help me get CWM or something working, since I want CyanogenMod on this Tablet.
Thanks in advance,
FingerMove
Nevermind, I fixed this using CF Auto Root and then installing CWM over Rom Manager.
Thanks anyway!
If someone else having this Problem:
Uncheck "Auto-Reboot" in Odin.
If Odin finished flashing: disconnect your Tab from pc and reboot directly from Downloadmodus into recovery.
Related
(SOLVED) I flashed the CWM tar file via Odin and wiped cache and davlik...booted up normal.
HELP!
I recently bought a GT-p6800 to use as a phone option. I wanted to root the ROM so I applied the universal root for ICS method and the device was rooted without any issue.
Here is where my problem exists
I wanted to backup the stock rooted ROM so I used GOOMANAGER to flash TWRP 3.4.0.0 on the device through the use of the GOO app. The process seemed to work according to the app.
When I rebooted into recovery, the tablet stuck on the splash screen logo Samsung galaxy tab 7.7. NOW I am unable to get the tablet to BOOT or get to a recovery. HOWEVER I am able to get into the download mode.
My thoughts are that I could recover the STOCK recovery by flashing it via ODIN?
Any thoughts that could help. I am posting here rather than trying something unnecessary.
Thanks in advance.
This exact same thing just happened to me. Haven't used odin before. Can you tell me exactly how you restored your tab? I sourced the CWM TAR file.
Thanks in advance!
I am trying to install the Clockwork Recovery on my Galaxy tab 7" series 2. I followed the instructions at http://forum.xda-developers.com/showthread.php?t=1861838 and used heimdall to flash the recovery.img from cwm-6.0.1.1-p3110.tar (obtained from http://rootzwiki.com/topic/33069-gt-p31xx-clockworkmod-recovery-6011/) .
Heimdall seems to indicate that flashing the recovery went just fine:
Uploading RECOVERY
100%
RECOVERY upload successful
But when I reboot into recovery mode, it seems that I have the standard "Android System Recovery" and not the clockwork recovery. Trying to install an update (to root the tablet) from external storage results in a signiture verification failure. I'd appreciate any help in starting to troubleshoot this.
Well, I got the Clockwork Recovery done by trying another few times. I'm not sure why it suddenly worked without my doing anything different, but it did.
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 was installing TWRP via ODIN 3.10.7. I rebooted my phone, went into the recovery only to find that TWRP was not installed and I was in the default recovery. I selected "Reboot" and now all i get is a repeating Note5 logo. Does anyone know how I can fix this? Thanks for any & all replies.
Edit: I was following this guide: http://forum.xda-developers.com/tmo...easy-steps-n920t-aoge-odin-twrp-root-t3187422
Kaveri said:
I was installing TWRP via ODIN 3.10.7. I rebooted my phone, went into the recovery only to find that TWRP was not installed and I was in the default recovery. I selected "Reboot" and now all i get is a repeating Note5 logo. Does anyone know how I can fix this? Thanks for any & all replies.
Edit: I was following this guide: http://forum.xda-developers.com/tmo...easy-steps-n920t-aoge-odin-twrp-root-t3187422
Click to expand...
Click to collapse
Search around that thread. I had the same issue as well as many others. You can flash TWRP in Odin by extracting the Tar from the zip (on your computer).
However, (as of yesterday at least) people are still experiencing frequent reboots - likely kernel related. Personally, I went back to unrooted stock for the time being. You can also check the other development thread (in development section).
Sent from my SM-N920T using Tapatalk
Go into download mode and reflash the team win recovery. The stock recovery reinstalled before I could install supersu. So I had to odin flash it twice.
Worse comes to worse Odin to stock and start the root process over.
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.