I've tried several times to flash shrp on my phone with twrp, but it never actually overwrites twrp? Not sure what I could be doing wrong.
malaikaj said:
t's possible that there might be an issue with the flashing process or the compatibility between the recovery and the firmware you're trying to install. Make sure you're using the correct version of TWRP that is compatible with your phone model and firmware version. Check if the firmware you're trying to flash is compatible with the version of TWRP you're using. Incompatibility issues can cause the installation process to fail. Try wiping the cache and data partitions in TWRP before flashing the firmware. This can help to ensure that any conflicting files are removed before the new firmware is installed. Check if there are any error messages displayed during the flashing process. This can give you a clue as to what might be causing the problem. You can also try using a different custom recovery such as OrangeFox Recovery or PitchBlack Recovery to see if the issue persists.
Click to expand...
Click to collapse
SHRP and TWRP are the only recoveries that have been compiled for this phone so far, so I cant try anything else. You say firmware as if SHRP is a rom, but it is a custom recovery?
Related
I was trying to switch my phone over to CWM from TWRP. I tried flashing using ROM manager but it was always rewritten. I decided to grab the .img file from the CWM site and flash it in terminal emulator like I had done with TWRP before. It seemed to flash but when i rebooted I got the message that the system software was not authorized. I thought the file I downloaded was loki but I guess not. Do I have to odin back to stock now or is there another method?
So I just realized it was being stupid and was stuck trying to boot recovery. I booted to download mode and selected cancel to force it out of this loop. Once it did this I was able to boot the system and restore a proper recovery.
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
thecaptain0220 said:
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
Click to expand...
Click to collapse
ROM manager does work...try flashing then reboot at least once before booting recovery...and if you are running a stock tw rom some will attemt to overwrite custom recovery...in newer cwm it will ask you if you want to disable recovery install...clicking yes will stop the process keeping custom cwm
Hi all, I'm looking forward to your help. Current state of my phone is a bootloop straight into TWRP with failed installs of Kitkat/gapps and failed restore of my backup. Here's a step by step of what I've done.
1. Opened Goomanager, updated TWRP using the button (current version 2.6.3.0)
2. Downloaded AOKP kitkat nightly and pa gapps - download completes and MD5 hashes check out
3. Used goomanager "flash zips" interface to attempt flash, with factory reset option and backup option selected
4. Came back to find my phone stuck at TWRP with failed flash
5. Tried to flash again manually, using the standard TWRP flashing page
6. Failed again.
7. Decided to cut my losses and restore the backup created when I first attempted to flash via Goomanager
8. Restore fails.
9. Phone fails to load system, reverts into TWRP when it fails.
10. So now I can't restore my old android system and I can't flash a fresh one.
Where do I go from here? Is my version of TWRP dodgy and giving bad flashes? Should I downgrade it via adb? My phone was fine until an hour ago, so I don't think it's a hardware issue. Many thanks for your help. Tom
Did you try to flash a stock rom via Odin (in case you can get to dl mode) or via recovery (you need to get a flashable stock rom for that). I have not experience with twrp though, maybe you could also try philz recovery (I think I read somewhere that kitkat had problems with twrp).
Sent from my GT-I9300 using xda app-developers app
Twrp let me recover my backup after I pulled the battery rather than just use twrps reboot option. So at least I have a functioning phone now. Odin was always my last resort, but I have a mac so finding someone's pc to use is a bit annoying/embarrassing. I'm going to try re-downloading the kitkat rom and see if that fixes it, but it seems unlikely considering it passed an MD5 check after download. Thanks for taking the time to reply.
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Tom-Tom07 said:
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Click to expand...
Click to collapse
thats what I read as well. the Slim team for instance recommends Philz and not TWRP if I am not wrong
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing. I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery. I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature". Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Bklynrx7 said:
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing.
Click to expand...
Click to collapse
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery.
Click to expand...
Click to collapse
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature".
Click to expand...
Click to collapse
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Click to expand...
Click to collapse
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
creepyncrawly said:
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
Click to expand...
Click to collapse
Sorry if I want clear. The phones are currently on 2.3.6. I tried using framaroot but it was not successful. The app said it was successful, but there was no supersu after I rebooted. I successfully got the phone rooted using one of the one-click odin flashers posted on these forums that are said to return it to factory + root. I then tried to use rom manager which said it was successful, but wasn't. That makes sense now that you're telling me its not compatible. Ill try upgrading to the JB firmware first, then ill try framaroot. Thanks for the suggestion
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Bklynrx7 said:
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Click to expand...
Click to collapse
Maybe I could help. What error does it give when you flash gapps?
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!