So I've been having this strange issue for a year now, where I want to upgrade my SM-T530 (Tab4 10.1 wifi) to the stock Lolipop (5.0.whatever) ROM in order to get the damn kernel updated so I can access all these wonderful custom ROMs (Stuck on CM 12 atm...).
But whenever I flash a stock ROM for my model, it seems to freeze the screen after the boatloader. As in, everything seems to be working, sound and touchscreen, it just doesn't update/refresh the screen. Basically, the same behaviour as described in this post.
So here's the steps I took, in the hope that anyone can point me in the right direction:
Boot tablet in recovery (TWRP 3.0.1, in this case) and wipe Dalvik, /data, /cache, /system, basically everything)
Reboot tablet into bootloader/download mode
Using Odin 3.11.1, flash T530XXU1BOL2_T530PHN1BOE1_HOME.tar.md5 (Found here, which should be the correct ROM for my model (Bought in the Netherlands, but I have no idea where you folks are pulling this T530XX stuff from, it's nowhere to be found on the back))
Reboot tablet
After the 4th step, the tablet will be unresponsive for ~10 minutes (I think it's doing the whole "upgrading apps" thing that follows a new installation). After that, when I hit a certain area of the screen, I can hear the regular Android touchresponse, raising the volume also give the normal beeps and pushing the power button plays the "turning off screen" sound, but the screen stays active, showing the Samsung Galaxy Tab4 boot logo.
Soooo... Anyone care to take a guess what I'm doing wrong?
Personally, I think it might have to do with flashing the incorrect stock ROM, but for the life of me, I can't find out which T530-code I have. I've been flashing different ROMs, but no luck so far...
As for troubleshooting I've already tried:
The above procedure, afterwards flashed TWRP via Odin and flashed a custom ROM via TWRP. Same effect.
Variations of the above procedure, where I keep wiping the tablet after each step
Different custom ROMs
Ugh, nevermind.
Turns out I have an UK tablet (BTU-T530XXU1BOG2). After flashing a dozen or so ROMs, this one did the trick.
Oh well, problem solved :good:
Related
Here is the story. I've got my Vibrant as a replacement for my older one two weeks ago. The old one had a problem with Home button responsiveness and at the end I decided to go with replacement. After some testing with identical firmware (freshly flashed) on both phones I found that the the new one boots much faster - around 12 sec difference (the time my audio widget is fully loaded) and overall I was very happy, until today when my phone screen turn of during some work on the browser. The buttons light was on and the screen became black.
1. I did battery pool. First boot was very slow. Force close for some koush process ( probably clockworkmod) came out .
2. I did 'wipe cache' - multiple force close after that
3. Factory reset - it was somewhat booting very slow and I decided to go with Odin.
I was able to put the phone in downloading mode and flash JFD with repartitioning. Everything looked ok during the process, but after reboot it plays Tmobile animation, startup sound, shows the letter S and stucks there.
I am able to get in stock 2e recovery. If I choose reinstall packages it goes to clockworkmod recovery (I thought clockworkrecovery should disappear after flashing with odin, but it is there) I tried flashing different usb ports - no difference.
The phone was with stock JI6 firmware, rooted with OCLF, ROM Manager with clockworkmod installed. Was working fine till today. I didn't experience any lag issues and neither of the lag fixes were installed or tested.
I played with clockworkmod recovery options format: system, data, sdcard.
I was not able to format boot - some error.
I am not a very good writer... sorry if somebody gets upset.
I will appreciate any help or idea.
Thanks
Fix for your problem
Sounds like some of the rom is either corrupted or the factory reset did not have J i-6 in it.......not enough info. Personal message me and i ll help you fix this problem.
What I want to do is install a stock non rooted rom, kernel, and recovery. I am not sure how to change recovery to stock either is it like flashing a rom? Please give me some links for these I can't seem to find them, besides the stock kernel I found that.
----------------------------------------------------------------------------------The reason I want the above is bellow, if it matters.-----------------------------------------------------
My phone is about 95% broken.
Before, every rom/kernel combination would randomly restart, it was my phone it self I believe.
I went to a stock rooted rom, but then it restarted, and my lock screen worked, yet my home screen was black all i could do was slide my status bar down.
After that i restarted my self and then it got stock forever on the screen where it says Samsung galaxy s4.
The 5% working part is my recovery, for the most part.
I keep having to do a full wipe, not just system wipe otherwise it says error unable to mount preload or i/o or a few other things, I have to system wipe before every rom attempt.
I tried several popular roms such as sacs and triforce and a few other roms and all the kernels also.
The phone will turn on, work for a little normally, then crash again and go into the infinite loading screen where is simply says galaxy s4.
This phone is only 3 months old, so I want to take it back to sprint being completely stock so they give me a new phone.
I need links to files I need, and if i am forgetting to change anything back to stock please let me know. Thank you.
I replied to you in the newbie thread, but to return to complete stock download the latest firmware from here: http://www.sammobile.com/firmwares/ and install it with odin. Do a factory reset before and after install to make sure you have cleared out what ever is causing your problems. After this process you will be completely stock and unrooted. If you are still having problems after this it is probably hardware related.
Hello to all. First, thank to the devs for all the fantastic work done, and to all the people willing to check and answer these threads. So down to my problem.
When I first got my S5 (SM-G900F) I immediately rooted with cf-autoroot. Tripped knox but worked well. From there I went on to install Twrp and then CM 11. The bugs drove me off, so I wanted a tw based rom. At the time I chose XtrStoLite (spelling?) And that worked a treat.
So after a while I found alliance rom and thought wow, this is great. So I installed it as per the instructions in the OP. Now we get to problem one: I got stuck at the Samsung boot screen. No boot logo, nothing, no matter what I did, even formatted /system, still nothing. I tried a few suggestions from the extremely helpful dev, @Goldie, none of which worked, such as flashing another rom first, so I tried with cm and slimkat. Didn't work. Tried updating supersu, didn't work. Tried different TWRP version, nothing. Tried Philz. Tried different Kernel with and without SELinux set to permissive and still it would need a battery pull at the Samsung "powered by android" screen.
Okay, last resort, flashed stock for my country (south africa), flashed TWRP, installed towelroot, rooted, flashed newest supersu, installed busybox and retried. This time something changed. Instead of freezing at the first Samsung screen, it now showed "Set Warranty Bit: kernel" in yellow at the top. Then the screen would go black, phone would vibrate twice and then reboot. So now I had a boot loop.
It was suggested to try omega, to see what happens. Well, it works fine. To date I've tried 5 different working roms. Was told to flash via omega, so I did, but same issue. At some point when I was on stock I even did a factory data reset, effectively wiping sdcard. Just in case. Formatted the external sdcard too. Formatted everything from /system to dalvik to /cache and /data, and eventually /data/media, and still that didn't work.
I'm really at a loss here. I'm the only one of all the other users with this issue. The devs have gone way over and beyond to help me, and that makes me happy. I donated because they've done more than others would. But basically I just need ideas of what the problem could be and why this is happening, if anyone has any ideas.
Find a screen shot of my "About" page here.
I have a Samsung Galaxy Tab 4 8” SM-T330NU running 5.1.1. The box tells me the ‘real’ model is SM-T330NYKAXAR. I decided to root the phone, because I want to get to Marshmallow and to get rid of this extra bloat where. (I will mention I have a good amount of experience rooting, including just rooting my Droid Turbo).
Anyway, after a lot of looking around the forums, I decided to use the CF-AutoRoot method (CF-Auto-Root-milletwifiue-milletwifiue-smt330nu) to root. I got Odin and installed it (along with the Samsung drivers) onto my Windows 10 PC; set debugging, on; and ran Odin. I followed the directions and it appeared to root properly; and I got to CWM recovery. Woo hoo! (Or so I thought)
So then after making sure I can get into recovery, I rebooted back into my stock ROM. Unfortunately, I got stuck at the Samsung logo; tried rebooting multiple times; even did a factory reset/wipe (as per instructions I saw on the forum) but to no avail. (Even let it set for over an hour but it never got past the Samsung logo).
After some more reading, I figured I might as well go ahead and flash a new ROM; so I think (if I remember correctly) I tried the JazzROM. It got up to about 69% and then it just quit - screen went black, and then it rebooted back to Odin mode. Obviously it didn’t work; then when I tried to get back into recovery to wipe and try the flash again, I got the message ‘Cannot mount \system - invalid argument’.
Again, after much reading and trying, I was able to get TWRP recovery installed and then wiped/formatted the system partition, which I had read would help get rid of that error. And it did seem to fix it.
So I can re-root with Odin without any issues; I can get to Recovery (either CWM or TWRP depending on which I flash), but no matter what I do, it either gets about 2/3 the way thru the flash process and then reboots back to Odin mode; or (using TWRP) I can get it certain ROMS to flash successfully, but after rebooting it goes right to Odin mode (saying it could not do normal boot). I even tried loading a stock, with the same result.
Which leads me to my first question: Exactly which ‘stock’ file should I be loading? I am having a hard time finding one - either it leads me to a dead end, or the download doesn’t work.
- When in CWM recovery, it shows the following:
At the top:
LMY47X.T330NUUEU1BOI1
Bottom:
#Manual Mode#
— Applying Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
Are these correct?
- When TWRP is installed (3.0.0-3) it starts by asking me about the ‘Unmodified System Partition’ and whether it should be kept read-only or allow modifications. I assume allow mods? Otherwise I don’t see how you could apply a new ROM? (I haven’t seen this in a while, not in my install of TWRP to the Droid Turbo). So just want to make sure I am selecting the right option.
- I am also concerned about whether I am using the right packages for this tablet. Based upon what I see on the box and sticker (which I still have) this should use the stock ROM LMY47K.T330NUUEU1BOI1 model; but I’ve also seen things referring to a BOG1 model? Mine is the T330NU English and (I assume) US model since I am in the US.
Any ideas as to what is going on? If I can at least get back to stock I could then start from scratch with the appropriate info; or just install one of the new ROMS (I’ve tried Jazz, Dirty Unicorns, UltraStock). I don’t think I am ‘bricked’ because if so I wouldn’t be able to get to Odin or recovery. Any help appreciated here. Thanks!
-Tom (Chimp)
NM, finally got it working, running DU and running fantastically, if I may say so. Getting TWRP to install finally fixed everything.
Sent from my SM-T530 using XDA-Developers mobile app
Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.