So I rooted using the one-touch script using Ubuntu. Stock rom. Never booted into recovery, just went to the market and installed Rom Manager and installed CWM recovery from there. Now when I boot into recovery, I get 3 options. flash zip, wipe dalvic, and wipe. If I try to flash anything, it returns "signature verification failed" error. Is the anyone that can help me?
-I use Ubuntu, so no ODIN
-epic 4g touch
-rooted, stock rom
if someone could tell me where the recovery is stored, I should be able to "flash_image" a new recovery and hope that works. any ideas would be helpful though. Thanks.
Sent from my SPH-D710 using XDA App
Your boot image (kernel+initramfs) is also your recovery.
It is stored in
/dev/block/mmcblk0p5
IMO you are better off just using the automated root in the sticky to install a stock kernel with CWM repacked in.
There are instructions to do a manual install in the reference section (manual in the sense that you run some automated scripts by hand, not completely manual)
Related
I've been struggling with this for a few days and thought it was about time I just broke down and asked.
What I'm trying to do is install the CM9 ROM on the my Telus model SGH-T989D.
I've been using CWM 5.0.2.6 as my recovery tool. I followed the instructions on the CM9 Page and formatted the various partitions and did a factory restore (all a few times) and then flashed the ROM. Everything seemed to go okay, however the phone would hang on the CM9 boot animation indefinitely.
I googled this issue and found that it was a problem with CWM not clearing cache properly. So I installed the latest CWM (6.0.1.5 non-touch) using ROM Manager and tried again. This time, the format cache function of CWM would hang.
After more research, I found that TWRP seems to work better. I downloaded gooManager but the Telus version is no supported by it. I did a manual install using dd (following instructions here) but now if I boot into recovery it hangs on the TeamWin splashscreen and the phone is unresponsive.
I think if I could find a decent recovery tool, I would be good to go so, in summary, can someone recommend a good recovery tool to use, or a version of CWM that will work for what I need it for, or a fix for the TWRP?
Thanks!
spizzak said:
I've been struggling with this for a few days and thought it was about time I just broke down and asked.
What I'm trying to do is install the CM9 ROM on the my Telus model SGH-T989D.
I've been using CWM 5.0.2.6 as my recovery tool. I followed the instructions on the CM9 Page and formatted the various partitions and did a factory restore (all a few times) and then flashed the ROM. Everything seemed to go okay, however the phone would hang on the CM9 boot animation indefinitely.
I googled this issue and found that it was a problem with CWM not clearing cache properly. So I installed the latest CWM (6.0.1.5 non-touch) using ROM Manager and tried again. This time, the format cache function of CWM would hang.
After more research, I found that TWRP seems to work better. I downloaded gooManager but the Telus version is no supported by it. I did a manual install using dd (following instructions here) but now if I boot into recovery it hangs on the TeamWin splashscreen and the phone is unresponsive.
I think if I could find a decent recovery tool, I would be good to go so, in summary, can someone recommend a good recovery tool to use, or a version of CWM that will work for what I need it for, or a fix for the TWRP?
Thanks!
Click to expand...
Click to collapse
there are only two choices of recovery and my choice is TWRP and I am quite sure if you went into the TWRP thread you will find someone with the same issue as yourself. Also no need to flash from the app when there are zip versions readily available in the TWRP thread.
I do not own the Telus version but I think asking in TWRP would be your best bet. Also what version did you try and install from goo manager app.
Also remember you are not the first person with this issue search search search again...
http://forum.xda-developers.com/showthread.php?t=1872679
http://rootzwiki.com/topic/33280-romstockt-mobile-t989uvlh1-telus-t989dtlle4odincwmtwrp/
http://forum.xda-developers.com/showthread.php?t=1768742
there were more but I figured these were enough to start,,,, PM me if you still need assistance, I used 5.0.2.7 with scripts for CM9 but that was before I gave touch recovery a shot
Thanks, that helped somewhat... I was able to get TWRP 2.2 installed using cwm but CM9 still hangs on the boot screen. I guess I didn't wipe all the sectors I was supposed to? Or maybe I should try the TDJ wipe.
For anyone interested here's what I did to get it all working:
Use Odin to install CWM
Use CWM recovery to install TWRP-2.2.0-hercules.zip
Use TWRP to flash Darkside Super Wipe and then flash custom rom
With this method I was able to get CM9 running on the Telus S2X
How about to get a jelly bean ROM to work.I flashed the new 2.3.1.1 ver. Of twrp but still can't get a jb rom to work..I keep getting boot loops..now ics roms flash flawlessly.. What could it be
Sent from my SGH-T989 using xda app-developers app
Open for suggestions here. I'm trying to flash cwr over twrp, but every time I boot into recovery I've still got twrp. Tried it using rom manager first, downloads and installs fine, says I'm using cwr 6.0.4.4, I boot into recovery using either the 3 button method or reboot recovery command, and I'm still on twrp.
Also downloaded the .img file from the cwr website and flashed in Odin, got a pass but I still boot into twrp. Any ideas?
Sent from my SGH-M919 using Tapatalk
That's weird. Its acting like you have a locked bootloader, which you don't.
Did you try using ROM manager app to install clockwork mod?
There are also flashable zips of clockwork that can flash in tarp recovery like like a ROM would be flashed. Tarp should stay after flashing but when you reboot to recovery cwm should be there.
If neither of those two things work, come back here with a very detailed step by step list of things you are doing to switch. We will see if younare missing a step
Sent from your phone. You should be careful where you leave that thing.
bfranklin1986 said:
Open for suggestions here. I'm trying to flash cwr over twrp, but every time I boot into recovery I've still got twrp. Tried it using rom manager first, downloads and installs fine, says I'm using cwr 6.0.4.4, I boot into recovery using either the 3 button method or reboot recovery command, and I'm still on twrp.
Also downloaded the .img file from the cwr website and flashed in Odin, got a pass but I still boot into twrp. Any ideas?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Go flash this from ODIN. Note, you can't flash a stock .img from ODIN, you'd do that with fastboot or a dd command.
http://www.androidfilehost.com/?fid=22946563261203781
Thanks guys, I downloaded a flashable of philz and flashed it though twrp and that finally worked. I had tried rom manager but that didn't work, and I had used this to package my .img file to an odin .tar
bfranklin1986 said:
Thanks guys, I downloaded a flashable of philz and flashed it though twrp and that finally worked. I had tried rom manager but that didn't work, and I had used this to package my .img file to an odin .tar
Click to expand...
Click to collapse
Still doesn't explain why CWM wouldn't flash over. You can use Mobile Odin to flash the CWM recovery img which should clear TWRP. This is just in case someone else has this issue. Don't be a denvercoder9
Sent from my SGH-M919 using XDA Premium 4 mobile app
$su
#mount -o rw,remount /system
#dd if=/path/to/recovery of=/dev/block/mmcblk0p21
#reboot recovery
Sent from Spaceball One.
Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock
hefilump said:
Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock
Click to expand...
Click to collapse
You will see E: Footer errors at stock recovery mode because stock recovery allows only samsung signed archive to sideload.
Or did you mean something different with E: Footer? You sentence is inaccurate.
For stock recovery image, I prepared a patched[/] stock recovery image, which will allow unsigned archives to sideload.
I was actually trying to find out why TWRP recovery is no longer available on my tablet. It was working but since loading a stock rom I no longer get the TWRP recovery only the stock one.
I have tried lots of combinations to try and get TWRP recovery working but nothing appears to work - I just get stock recovery.
I am using:
T700XXU1ANF9_T700BTU1ANG1_BTU stock rom
CF_AutoRoot_Port_T700_BeansTown106.tar.md5 to get root access with Super SU
TWRP 2.7
TWRP Manager from Play store with the recommended Busy Box installed
I am sure I am missing something but cannot see what it is - I obviously got it right before as I had it working but I have missed a step somewhere.
Try using Flashify from the playstore and flash the TWRP .img or .zip
The "dd" method is the most flawless method if your familiar with using terminal
http://teamw.in/project/twrp2/238
Nexus 5 via Tapatalk
Finally got things working. It would appear that it is all about the sequence you do things in.
1. Use odin to load stock rom
2. Set up tablet and let everything download and update
3. Use odin to get root
4. Ensure that root is working and up to date
5. Use odin to add TWRP
6. Install TWRP manager from play store
7. Install Busybox from play store and run installation in busybox
If you deviate from this sequence TWRP does not appear to work in recovery. Have now made successful backup and can start playing with custom roms again.
Thanks for all the advice.
Not to much excitement I hope. Limited to a couple Roms
Nexus 5 via Tapatalk
Just FYI twrp IS recovery, when u restore to stock twrp is overwritten by the stock recovery. Twrp is not overwritten when you flash custom roms because recovery is not packaged in the zip file. But remember stock firmwares overwrite your recovery. Also please remember not to take ota's if you are using a custom recovery like twrp
I noticed that when using the last dev preview for my N7 2013, it keeps killing TWRP and putting back the stock recovery. Now the final release does this. If I flash TWRP again, it just gets overwritten after a normal boot then back to recovery.
Why? Is there a way to stop this? This is the first time I've dealt with this. Nothing else does this to me. I haven't found a clear answer yet to this while searching this site or others.
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
rguilamo said:
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
Click to expand...
Click to collapse
Well it is just 5.0 that does this.
Since I posted this there is a sane reason for them to do this - it might be the way they enforce the factory reset protection. It has to use their recovery to do so. Still annoying.
But thanks for a workaround, that it simply is the kernel, or boot image. That and I want root
You can try Chainfire's CF-AutoRoot, It modifies Boot.img so root is granted in boot time, I already had a custom kernel when I rooted, but you can try to root first and see if it stops auto-writing the stock recovery.
Here's the download link: http://download.chainfire.eu/347/CF-Root/CF-Auto-Root/CF-Auto-Root-flo-razor-nexus7.zip
Extract it, and run root-windows.bat (or the one suitable to your OS) while in fastboot.
Not sure what has happened. Rooted with Odin3.7/CF. Everything running great. Titanium Pro installed. Knox frozen.
Wanted to install CM ROM. Ran TWRP app to set custom recovery. Said nothing found. Ran install of latest image. Install unsuccessful. Only option after that was to reboot into download mode and reflash from the xda forum files linked above. Now it seems to be stuck as unrooted and I can't get SU/root back.
Is this thing trying to flash itself now? Anyone have a custom recovery image and settings to use with Odin? Or is this something else? Sorry for the n00b problems/questions. :'( Any help is greatly appreciated. I'm trying to get this set up for a friend, and obviously, Android/Linux is not my specialty.
Also:
Tried flashing to this and then tried running the CF-Root again. No root. No glory.
Not sure what else to do at this point. I had root before and then CM instructed to run a custom recovery before installing the ROM. So I tried that with TWRP and failed. Now it seems like it is unable to flash the CF-Root. It goes through the process then says restoring stock recovery before rebooting.
If anyone has any advice, that would be great. I'm sure it is something stupid, simple, and outside the scope of my knowledge. Thanks.
Also:
I booted into recovery mode after the TWRP failed. No custom recoveries were listed.
Originally, I tried this and rooting failed. I still ran the custom recovery with that package. Then I ran the files linked in the first paragraph above and got root. Those instructions never mentioned running a recovery after flashing to root. Is this where things got messed-up? Should I have run a recovery after that? Or was the recovery from the first attempt at getting root still on the partition? I'm so confused.
Did you manage to root it? What device is it?
Flash back to stock and start fresh
Sent from my SCH-R530U using Tapatalk