I get failed with v3 patched
Will somebody plz chime in with some knowledge here for me? I'm on 4CTD1 firmware. I rerooted. I'd like to install TWRP. The ones I've flashed won't allow me to boot into the system after flashing. It just keeps booting into TWRP. And once it booted up with SAMSUNG on the screen and got stuck. Thanks
Currently from what I have seen and experienced there is no fully functioning TWRP for latest One UI 2.1 yet that successfully boots custom GSI/ROMs without tampering with the TWRP. The latest TWRP on xda is not updated for latest firmware yet so if you was to flash and use it you will run into many problems when booting custom firmware e.g broken camera. Your best bet is to wait until further news has been updated on xda for a newer TWRP.
Related
Hi,
I've rooted and unlocked my t989D. To do that I pushed recovery-clockwork-5.0.2.7-hercules.tar via odin and then flashed SGH-T989_UVLH1_Stock_Deodex_Rooted_signed and Tmo_SGH-T989_UVLE1_radio to be at at 4.0.4 ROM and radio.
Now I want to upgrade to cm 10.2. I tried flashing it, and it required a newer radio, so i flashed Tmo_SGH-T989-UVMC6_radio. Then I reflashed cm 10.2 and the installation completed, but I only get a boot loop with the CM sign. I figured it was because I was using an old recovery. So I tried to flash a newer CWM (recovery-clockwork-touch-6.0.3.1-hercules), and that failed, so instead I pushed the latest TWRP (openrecovery-twrp-2.6.3.0-hercules.tar) via Odin. I'm in the same position as with the older version of CWM: I can boot recovery, I can successfully flash 10.2, but I get stuck in a boot loop with the CM sign. Can someone correct me? Id appreciate it if you could correct my logic as well plz.
Update:
I pushed the old CWM back (5.0.2.7), then flashed an older version of CM (9.1) and it got stuck in boot loops as well. I then flashed the stock 4.0.4 ROM back and it gets stuck in boot loops (during samsung logo). I then pushed TWRP 2.6.3 back and reflashed the stock 4.0.4 rom ROM and it boots
Basically, the only combination that well allow a full normal boot is TWRP 2.6.3 + stock 4.0.4 rom (SGH-T989_UVLH1_Stock_Deodex_Rooted_signed)
Update 2:
Solution seems to be a dark side super wipe http://forum.xda-developers.com/showthread.php?t=1477955
So far, this allows me to get 9.2 working. Haven't figured out how to get 10.2 going yet.
Install latest twrp recovery then use superwipe zip file (that is mention in your archive post) than install your rom.
As far as about your boot loop issue wipe your internal and external card than just put rom installation files in it.
Sent from my SGH-T989 using XDA Premium 4 mobile app
Hi people, quick bit of help if possible. Received my X9006 a couple of days ago. I initially flashed TWRP on it and then rooted, all went perfectly. I then found that I couldn't flash OS 2.0 with this, so reverted back to stock recovery and the stock recovery root. This fixed the issue and OS 2.0 installed flawlessly. I have since tried to re-flash TWRP but it just doesn't want to work. Is there some compatibility issue? Would I have to revert back to OS 1.2 and then flash TWRP and SU to be able to install any other ROMs in future? Apologies for what seems like a stupid question as I'm sure it's something obvious but my brain is fried. Thanks.
Hi, I flashed twrp after installing 2.0. No issues. Did you erase cache?
Edit: or you could try flash tool from play.
With our unlocked bootloaders there is nothing stopping you from flashing a different recovery at any time.
Show us the output from your fastboot commands to help.
BTW, you can flash official Oppo updates in TWRP by removing the (usually first two) assert lines looking for Find7 in the updater-script.
Hi all,
I am new here and I am having trouble with my Galaxy 3 SGH-I747 from at&t
I rooted the phone using KingoRoot and everything was fine.
I used the phone for about a week and decided to update from kitkat 4.4.2 to lolipop 5.0.
I have a micromax phone that is rooted and I didnt have any trouble updating it while it was rooted, so i figured it wouldnt be a problem but when I updated the s3 it said update failed at 94% and started rebooting and got stuck in an update loop.
I searched and searched and tried finding recovery options using odin but I cant find a 4.4.2 stock firmware, and cant find much information on recovering my device.
I am unable to boot in to recovery. I cant find a link for the SGH-I747 to philz recovery, the links all seem to be dead.
I can boot in to download mode.
I want to install a custom recovery via ODIN but i cant find one for my phone.
After I install the custom recovery, how will i know which stock OS my phone is currently at
I appreciate any advice you can give me, thanks.
Use TWRP for custom recovery. CWM and Philz haven't been updated in quite a while. You can get odin flashable tars from here.
Flashing TWRP should get you to working recovery, and you can find the rom zips you need to get back up and running in the development section here.
Unrooted stock will overwrite TWRP with stock recovery upon boot. Depending on how far your phone is getting into the booting process that might happen if you let odin auto-reboot. Your best bet is to uncheck auto-reboot in odin, so it won't restart on you automatically. Upon success remove the USB cable and pull battery. Replace battery and boot straight to recovery by holding home+vol up+power until you see tiny blue text in the upper left corner then releasing.
Thankyou! i was able to install the recovery by TWRP.
I just need to figure out what firmware to install and where I can get it... I was on kitkat, I tried to update to lollipop but it didnt work. My phone is bricked so I dont know how i would see the firmware version on it.
I really just want any kind of stable firmware that is rooted. Any ideas where I could find one? I'm trying to sift through the forums
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
audit13 said:
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
Click to expand...
Click to collapse
I appreciate all the help - It seemed really hard because I was finding roms and flashing with ODIN but it always failed TWRP is giving me results. I flashed slimkat and got my phone working again! the only problem is my sound is a bit junky, idk why.
I plan on trying out Octos - M, because I heard marshmallow OS has a lot better battery life among other things
If i upgrade to a custom marshmallow OS, is there any coming back to a former custom OS like 4.4.2? or is it a permanent upgrade?
Do you guys recommend any custom OS? I need something stable, that uses the resources efficiently.
Before flashing additional ROMs, make sure the phone is running the latest bootloader and modem.
To verify the installed bootloader and modem, install the Samsung Phone Info app from the Play store.
With a custom ROM, you can flash from one to another, usually without any issues as long as you perform a complete wipe (system, data, cache) before flashing a new ROM. If you are upgrading an existing custom ROM with a newer custom ROM (e.g. CM12.1 2016-01-01 nightly to CM12.1 2016-01-02 nightly), you can just flash the updated ROM over the existing ROM.
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
After several failed attempts to root my Galaxy S6 Edge+ (SM-G928T) with the latest firmware update to 6.0.1, G928TUVU4DPK6, this is what I had to do to get a working root solution. At no time did I ever have a problem installing TWRP with Odin. Ive been using Odin 3.12.3 but I had the same issues with Odin 3.10.7.
I started with a clean slate and performed a fresh install of the stock firmware which I downloaded from here:
http://forum.xda-developers.com/tmo...al/sm-g928t-stock-odin-g928tuvu4dpk6-t3516310
After flashing the stock firmware with Odin 3.12.3 I did the basic setup on my device to make sure I could boot and everything was working. Next, I shut down my device and booted to Download Mode by using the key combination of Volume Down + Home + Power. Once booted into Download Mode I used Odin again to flash TWRP 3.0.2-0, which is available here:
https://dl.twrp.me/zenltetmo/
After the flash was complete I booted to recovery using Volume Up + Home + Power. When TWRP starts it will ask you if you want to swipe to allow system modification. If you swipe to allow system modifications you will trigger DM-Verity and you will not be able to boot normally unless you flash a custom kernel that has DM-Verity disabled in the fstab or you can flash the no-verity-opt-encrypt.zip that I dowloaded from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
The newest version available is 5.0
So, I swiped to allow system modifications. Next, I transferred the no-verity-opt-encrypt.zip from my PC to my device and installed the zip in TWRP. Once this was completed, I transferred my root zip from my PC to my device. I used the PHH Superuser to root my device which is available here:
https://superuser.phh.me/superuser.zip
I installed the root zip in TWRP, wiped cache/dalvik cache and then selected Reboot System. I didnt know if I would be able to boot or not. I could never get past the T-Mobile boot animation each time I attempted to root this damn thing but low and behold everything went as planned and I was fully booted up and running. I went through the setup wizard and everything was working as it should.
I am using PHH Superuser instead of Chainfires SuperSU. Its a personal choice for me as I have been using PHH Superuser since the hand off of SuperSU to a new company, CCMT, LLC.
Once I was finally able to boot normally I downloaded PHH's app in the Play Store from here:
https://play.google.com/store/apps/details?id=me.phh.superuser
This is just my experience of what I had to do to get root working on my S6 Edge+. All of my root apps are working as designed. I cant remember the last time I didnt have a rooted device and it was starting to bother me. I was having root withdrawals. If anyone decides to upgrade to the latest firmware from T-Mobile and wants a working root solution, here is what worked for me. I have not tried to use Chainfires SuperSU again. If you dont want to use PHH Superuser and wanted to use SuperSU instead, try to insert SuperSU in place of PHH Superuser and see what happens. Do this at your own risk because I have not tested it with this solution that I found. Good luck. Happy Rooting!!
fast69mopar said:
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
Sent from my SM-G928T using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the one I used. works great
Venal_System said:
Here is the one I used. works great
Click to expand...
Click to collapse
I tried that version too and I ended up with the same problem each time. I figured it out last night though. Im going to update my OP with the steps I had to take to get it working and that way if anyone upgrades to the latest PK6 firmware for their G928T and has this problem my thread is available with a solution.
[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?