I bought a used Samsung tab S2 with a working Lineage 17 already installed.
I tried to install stock ROM using ODIN.
The ODIN process seems to work fine; I get a "PASSED" in green in ODIN, but the tablet will not boot. Immediately after the "PASSED" in ODIN, the tablet displays "updating system", then "erasing" for about 20 seconds, tries to reboot, but hangs at "SAMSUNG" screen and will not boot.
I've tried several stock ROMs from from different sources.
I'm not sure about the Android terminology, but I think I can get into "boot" mode, but not "recovery" mode on the tablet.
I'm not familiar with a lot of the terms with tablets/phones, so learning by doing. However, I've successfully flashed many computers(Windows >Linux), Enigma 2 receivers, (much easier process), stick a USB stick in and go. I'm surprised the process of flashing a new ROM on Android devices is not more simplified, or less involved.
Thanks for any help.
I had this issue once, it was after I enabled 'Update Recovery' in Developer Options on LOS 17.1, it's "update the built in recovery with system updates" thinking it was a good idea but after it updated the first time it would boot-loop or hang, cant remember but it wouldn't get to the OS anymore so I had to re-flash it, but I was getting this problem. I remember it all being a mini nightmare at the time, I believe I had to find a PIT file to repartition it. I don't understand how it got so severely busted but I stayed right away from that option since then and the LOS 17.1 has been really great.
I had a similar type thing years back going from 1 type of OS to another, I didn't realise they used different file systems and I had similar issues when trying to fix my mess. Learning then about how different ROMs can depend on completely different file systems taught me that if things are really bad and you can't even flash a stock rom with Odin, then finding and flashing the PIT file is basically guaranteed to fix the issue. It's super rare that this type of thing happens though, so I tend to forget about crazy experiences like watching my new OS delete itself immediately after installing it, I forget about the techniques and tricks, I tend to swear and panic and chase my tail for a while before eventually working it out.
Related
I have a Galaxy Note 3 and a Galaxy Note 4. I encrypted them and it seemed to go smoothly on both phones.
However after boot, the Note 4 started giving me headaches.
Turning it on I see the usual CyanogenMod's animation for a few seconds then it jumps and disappears. then I see a white box saying Android is finishing booting, and then I'm presented with a pattern screen different than the one I used to see. This one lets me change the amount of dots. It also lets me make emergency calls. So I slide my pattern, I see "Checking" then it's just the same initial CyanogenMod animation. For ever.
With the Note 3 I saw the exact same thing but the second animation lasted just a few seconds. Now it is working fine. The Note 3's storage had around 100MB in data. The Note 4 has several gigabytes of data in it. I presumed it was still doing some work, so I left it in the animation screen for a few hours. When I touched it was burning hot.
It won't enter Recovery Mode. I tried flashing recoveries with both Odin and Heimdall. With Odin it seems to work but it won't boot into Recovery Mode. Heimdall always gives me an error. I tried flashing cm-12.1-20160316-NIGHTLY-trltexx-recovery.img, twrp-2.8.7.0-trltexx.img and twrp-3.0.0-0-trltexx.img with Heimdall and twrp-2.8.7.0-treltexx.img.tar and twrp-3.0.0-0-treltexx-treltexx.img.tar with Odin.
Update: I've managed to install TWRP 3.0. The problem still persists though. TWRP doesn't ask for password or pattern, which doesn't allow me to do pretty much anything. The only MicroSD card I have is only 256MB - usable 240MB - latest CM 12.1 nightly is 255MB - so I can't even flash a new ROM! I'm surprised TWRP doesn't have a way to decrypt the storage. I very much hope I'm missing something.
Update 2: I've managed to flash a few different ROMs via ADB Sideload. I still can't get access to the data partition at all. I can't even format it! I'm getting quite desperate at this point.
Please, help!
I guess you could try a complete repartition using a pit file.
http://forum.xda-developers.com/showthread.php?t=3282641
I flashed a stock ROM. I genuinely thought it would completely erase the entire phone memory, but it didn't. as soon as it finished booting I saw the pattern decryption screen, but it just wouldn't accept my pattern.
I flashed another TWRP 3 again, went to that scary screen and wiped, and formatted, and erased, and did everything it allowed me to do, as I was sick and tired of that drama. flashed some CM to it and was done with it.
never trying to encrypt that thing again. Android's openness is too chaotic: too many OS variants, too many vendors, too many minor model variations, too many non-standard stuff going on. the result is it's unlikely someone else will have the exact same problem, with the same model, the same OS. I'm done.
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
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:
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
G'day all,
Hoping someone can help. (firstly I've searched on here over and over and some things have really helped, but can't find this issues on here)
Samsung Galaxy S4 GT-i9505 (originally with Vodafone rom)
Back story, I managed to put google rom via WINTEAM at some point in time (I don't recall how I did this now) this file - crdroid-6.0.0-20151208-jfltexx.zip (I still have this but not a md5 file)
Anyway, I wiped it under settings and basically stuffed it right up. Loops on WINTEAM (this part I had found in search and downloaded Odin3 v3.13) and Samsung Rom and a couple of others.
I9505XXUHOJ3_I9505VAUHOJ1_I9505XXUHOJ3_HOME.tar.md5
I9505XXUHQK1_I9505MAXHQK1_I9505XXUHQK1_HOME.tar.md5
I9505XXUHOL3_I9505TELHOL2_I9505XXUHOL3_HOME.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
The last one actually fixed up the google install but was hoping to place the original Samsung ROM back on and now it doesn't help at all when I run again.
The top 3 are Vodafone, Telstra and Max a forum had suggested (from a page on here somewhere). All of these say pass in Odin3 when installing onto phone. But once it gets to the Samsung with what looks like dots shooting out from the word it never gets past this at all.
When I power up the S4 phone, to get to download screen. I have volume up to download or volume down to restart phone. Some places I've read say to select wipe, I don' t have this option at all.
I saw an option to install s8 rom to s4 which I would like to do, but the how to do that requires working software first and install TWRN or something like that.
I'm not sure if this will run fast or ok on this phone, but it isn't a MD5 file either.
I would like Samsung ROM back on as it (for me cleaner than google or maybe just what I've been used to). I'd like to give to my youngest child as their first phone.
I also had tried to place zip files and also unzipped files on the SD card on the phone, nothing worked for me as it looks like it is expected ODIN3 to work.
At this stage of the day, I would just like to have it functioning again with anything that works.
Any advice on what to do now would be greatly appreciated, also I'm truly sorry if this problem has been documented, I really did try to do my research first before putting this up here. I've been on this for weeks now
So quick update. through more research, I have managed to install TWRP and now have access to additional utilities through WINTEAM. I've now tried to install ROM through the Micro SD card.
I think it comes up with a mount error, but has rebooted and still stuck so can confirm just yet.
I've managed to go through the entire process of installing the PurifieD+ROM+v3.5.zip through the micro SD card in the phone. Asked me about all the options etc during the install. There didn't appear to be any errors at all. Asked to reboot. etc....
I even had sound on the bootup, Now I have the Samsung word on the main screen with a blue backlight just flashing. Been like that for nearly 10 minutes. Not looking good.
Have I got bad memory or am I doing something wrong?
I managed to do a wipe after I did an install and it booted up find. I had no WiFi but than installed the vodafone install that should be the original and all works now.
The amount of time I had been working on this, I really didn't think I was going to get it going. I honestly thought I had some hardware error going on.
In the end it runs now, I can setup and had to my child
so I've managed to now use several different ROMs but now I can't root the phone (it should be able to, has been before)
When I run Motochopper I get this error
error: only position independent executables (PIE) are supported.
Seems to happen no matter what rom I've installed. I can't seem to find an older rom running android version 5.01 now
Any help on how to root this. Would be great
Now says it has been rooted, but I do not get the teamwin boot menu option at all. more like just a text style menu for wiping and loading other roms.