Am I the only one? - Galaxy Tab S2 Q&A, Help & Troubleshooting

About 3 weeks ago I posted a question seeking help when I couldn't get TWRP recovery to boot after updating to 3.3.1. I tried numerous things but the end result was I wound up having to restore the latest stock ROM and rooting with CF-Root. (see thread "Can't access Recovery after updating TWRP").
My question is this - Am I the only T813 owner who has experienced this issue?

Related

[Q] Flashing the proper clockworkmod

Greetings Everyone,
I am really stuck with this phone that I am working on right now. I wanted to simply flash a new rom to this phone and I started by rooting the phone which was successful. Once I had done that I downloaded Rom Manager and flashed the recovery mod to the phone. However, It seems that the recovery mod that I had chosen for the P990 was incorrect. As a result when I try to flash any rom or even revert back to my back ups from CWM I simply get the Boot Loop. I am almost convinced that the problem lays with the CWM version that is installed. Therefore, My question is how do I flash a different CWM and I need a step by step help with this since I dont know very much about this process.
All your help is greatly appreciated.

[HELP] Soft-brick my phone (I think)

Hello, I have been trying to flash for 2 days now but still couldn't get it working.
Initially, my I9305 is running on stock without root. I wanted to root it and then install recovery and ROM.
And so I prepare the necessary files, and start to flash.
I used CF-Auto-Root to root my device first, then got Resurrection ROM and Gapps to flash.
Then I started to get some issue, as it always fail. Error message like no file context and so on. So I read online resources, and found out that I had a older version of TWRP installed which may cause the install.
I then tried to upgrade TWRP but it doesn't allow me to. No choice, I had to flash philz touch, and I did.
I then tried to flash Resurrection again, boot up, and it keep giving me bootloop. After which I downloaded nameless ROM, and CM11 but same issue.
Yesterday night, I downloaded the stock firmware to try. I flashed it, and it is successful based on ODIN, but it still won't boot up.
I just tried it again and it stuck on the Samsung logo screen.
Can anyone tell me what else to do? What I have to do?
This is the stock firmware that I have downloaded and flash - I9305XXUENH1_I9305EVRENH1_EVR.
Let me know what other information I have to provide.
Thanks!
Here's the Download mode information.
Custom binary count: 9 counts
Current binary: samsung offical
System status: custom
Knox void: 1
RP SWREV: A2
Update: 16/1
I just tried to go into my recovery mode and apparently, it has been changed back to stock recovery which I assume is because I have flashed the stock firmware.
I am trying it yet again after wiping in stock recovery, to flash the stock firmware again now.
P.S: I have posted it in http://forum.xda-developers.com/galaxy-s3/help-i9305/qa-samsung-galaxy-s3-lte-roms-kernels-t2999494 but no reply. So trying my luck here.
Ok, this is funny. I waited for 2-3 days before posting here for help. And it doesn't work for all those days.
Now that I just posted, it finally worked. I am getting into the setup screen.
Anyway, for those people who may have the same issue as me in the future, try to wipe everything after flash to stock firmware. then flash stock firmware again.
After flash
It's a good call,as per your last post,to wipe data and factory reset after a flash and even a second install.Need to give time for changes to occur.Don' go too fast.HTH.

i9305 stuck on boot logo

Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then

Flashing and twrp

Hi all I've been many year lurker since my galaxy s2.. I've had other phones but have been able to find what I need and stay quiet..
According to this thread page 3
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601/page3
Someone said they flashed twrp with flashify and it worked fine...
I was wondering if I were to do this do I still go through the bootloop stuff? I already have root via KingRoot and swapped for supersu..
I'm hoping to
Download twrp
Flash with flashify
And be done with it
Is it that easy???
Thanks all

What is the latest, proven way to install custom recovery on a I9305?

I see many threads involving problems with installing TWRP or CWM on a I9305. All have "Try this", "Try that", "Use (some older version) TWRP", "Install CWM, then flash TWRP", etc. I just bought a refurbished I9305. I want to root and install a recovery, preferably TWRP. I don't want to end up on some endless help thread after bootlooping in the attempt. So, what is the current, best recognized way to do this? Solutions to problems in the past should help prevent the same problems in the present. My hope is to flash Resurrection Remix, Android 7.1 or, frankly, any Android 7.1. Any help would be greatly appreciated.

Categories

Resources