FYI I'm definitely a newbie to android and had 0 knowledge of any of this when starting so this very well could be something stupid and easy I'm missing..
Device: Samsung galaxy tab S4 wifi version SM-T830 (Now on android 10)
Cliff notes:
I was on android 8.1.0 (oreo), tried rooting via a patched root(?) i think it's called, without twrp using magisk. magisk showed it was not rooted
Tried flashing TWRP still on oreo, odin showed a failure to flash with no other information, just the standard (<OSM> All threads completed. (succeed 0 / failed 1))
I tried different odin and twrp version combinations with the steps above, i couldn't find which version of odin to use on oreo as their docs seem to list every android version but oreo and had other people suggest maybe not using the latest TWRP since I wasn't on the latest version of android. None of the combos worked
Finally got updated to android 10 today, using one of the latest odin versions (3.14.1) and a couple different TWRP files found either on twrp.me or on here (twrp-3.5.0_9-0-gts4lwifi.img.tar / TWRP_T83x_3.4.0-6.tar) but still nothing, same message in odin.
One last thing that might be helpful is that I only just updated today to android 10 because by some magic my device finally showed updates in the settings of the tablet itself. Previously I had tried samsung's smart switch which found updates but got stuck on 0% for the install the 50 times i tried it. I'm also still unclear as to how I'd flash a custom recovery(?) to get myself to a good version of android. I know how to in odin but I don't know where I can find trustworthy files that will work for my device. I've downloaded some with Frija but have been nervous about trying it as I'm just too new to this to know if that's always safe to do or if I'd cause more issues..
So yeah sorry that was still long, shortest version: Can't flash TWRP no matter what I do. Does anyone have ideas on what else I can try or does anything stick out as blatantly wrong? I'm at such a loss with all of this.
I find it hilarious that after like a week and a half 5+ hour days trying to figure this out, i finally give in and post my question. Within 30 min I find the answer and flashing works lol... I saw user Mentalmuso mention in one post, if Odin errors to restart the device and PC. Go figure, that worked. How stupid that you have to completely shutdown your workspace on error lol! Anyway hope someone facing the same issue sees this. Good luck!
Related
Phone Stats
Sprint Galaxy S3 (SPH-L710)
Cyanogenmod 10.2 (Stable)
Last ROM update flash was months ago, no issues
TWRP latest
Can not get into recovery
Can get into download mode (using HOME+VOL-DOWN+POWER)
Using Odin 3 (1.85)
Phone was sitting on table, just started boot looping.
Tried to flash (everything) - stock Sprint image, CM ROM, etc.
Odin fails when it gets to reading the PIT information.
I looked everywhere for a Sprint GS3 PIT file, only found one, but it was labeled "i710" (probably by accident) and did not work.
If anyone has or can dump an image of their partition information (PIT) I would be extremely grateful, and willing to compensate you, because I'm an Android developer and kinda need my phone =)
More information:
Yes drivers are all installed and working. Phone is recognized as usual on three different laptops.
Yes phone was charged at least over 80% when trying anything.
Yes, tried multiple cables and USB ports (esp. powered ones) - phone connects fine.
Brought it to Sprint - they actually tried to flash it for me (nice guys!) but the software denied b/c of the custom binary.
Yes, I read every post here/elsewhere containing the keywords "PIT", "S3", and "brick" - many solutions would work, except for the fact that Odin won't get past reading the PIT.
No, I didn't do anything dumb like flashing GSM, international, custom crap, or by checking "repartition" or anything like that.
Not using any custom kernel or anything else - only the recovery (TWRP) and ROM (CM10) are custom.
Even more information (yes, I'm desperate!):
I tried all methods I could find - literally days worth of searching - including reinstalling the drivers, installing drivers while in download mode, connecting from Windows 7, Windows 8, Windows 8.1, and Linux (Ubuntu - Mint).
Tried flashing stock recovery.
Tried flashing stock Sprint/Samsung image.
Tried flashing various PIT files claiming to be Sprint SGS3.
I basically gave in and was going to buy a new phone, but the dude at Sprint even said "this is fixable - you just need that PIT file", so I'd like to give it one last try before calling it. The phone really has been good to me, otherwise.
Any help is greatly appreciated! If you read all of this, you're a saint =)
Adding Odin output
CorporalMaxSterling said:
Adding Odin output
Click to expand...
Click to collapse
Relevant thread for anyone following:
http://forum.xda-developers.com/showthread.php?p=48376031#post48376031
DELETE: I see you have another thread about this already
sent from my GS3
joeyhdownsouth said:
DELETE: I see you have another thread about this already
sent from my GS3
Click to expand...
Click to collapse
Thanks. That's real helpful. It's not my thread, it's a related one I found after I posted, and this info is still relevant.
Hi,
This is my first post here on the XDA forum so if I make any mistakes, please do tell.
So, I got a Galaxy Ace 2 (I8160) which was running unrooted and stock at Android 2.3.6 (if I recall correctly).
I decided I wanted the phone to run at a newer Android version (KitKat preferred), so I decided to look into Cyanogenmod 11.0.
I succesfully installed the Clockworkmod Recovery after soms attempts and after that I was able to install Cyanogenmod 11.0 running on Android 4.4.4.
My first impression was positive, until I noticed I regularly got some error messages about com.android.phone which stopped working.
On top of this, the phone had no service and I was unable to make any calls (also selecting a service provider made com.android.phone crash).
After a lot of looking around on the internet, I found out this could be caused because I flashed Cyanogenmod 11.0 directly from Android 2.3.6.
On another tutorial I read I should've flashed Cyanogenmod 11.0 from any Jellybean version but as I stated earlier, I flashed it from a Gingerbread version.
On another forum I found someone who used to have the same issue and stated that he made the same mistake as I did (flashing from a non-Jellybean version).
He said he flashed a stock Jellybean ROM to his phone, installed Clockworkmod Recovery and at last flashed Cyanogenmod again and everything seemed to be working just fine.
I decided to do the same and flashed a stock Jellybean ROM for the I8160 using Odin v3.07.
After Odin told me the flash process passed, the phone rebooted but was stuck at the Samsung Galaxy Ace 2 logo.
When trying to get into the recovery, I got the same problem and the only thing I saw was the startup logo.
If I'd turn off the phone and plug in to my computer (which normally shows the battery percentage) it'd be stuck at the loading icon (normally this loading icon is visible for about 5 seconds and after that the battery percentage is visible).
I'm still able to get into download mode, so I tried reflashing the same ROM but unfortunately without success.
I used the following stock ROM: samsung-updates.com/details/28857/Galaxy_Ace_2/GT-I8160/XEN/I8160XXNB1.html.
I've been using the Cyanogenmod 11.0 and GApps files from: maclaw.pl/downloads/.
Does anybody have any idea about how I coud fix this?
Thanks in advance.
EDIT: Just tried flashing a stock ROM with Android 2.3.6, problem is still there: samsung-updates.com/details/18868/Galaxy_Ace_2/GT-I8160/H3G/I8160NELG2.html
In my opinion, You should flash 3-parted Firmware
http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8
PS. Sorry for my bad English.
ChuckMichael said:
In my opinion, You should flash 3-parted Firmware
http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8
PS. Sorry for my bad English.
Click to expand...
Click to collapse
Thanks for you reply.
I came across this 3-parted firmware flash a few hours ago.
I'm trying it right now. I'll let you know what the results are.
Alright, another update. (My problem seems to be fixed!)
At first I tried downloading the 3 files neccessary for the new flash method, but for some reason it'd take me hours to download them.
I started looking on the internet for the same files and found a torrent link on another forum leading to a torrent file uploaded here, on the XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=1757643&d=1361735404.
I downloaded the files in the torrent and used them properly in Odin.
The flashing process started and at about 80% Odin gave me a nasty error message saying the flash failed...
At that moment I was seriously hopeless and pretty sure I've just succesfully hard-bricked my phone.
I tried to start it and I got a weird message saying a firmware update went wrong and that I should fix it using Samsung Kies.
As it stated, I tried using Samsung Kies but was unable to get my phone to work.
I was out of options so I decided to give the 3-way flashing method a second chance.
Oding started flashing and for some reason finished succesfully this time.
The phone reboots, and shows the 'Samsung Galaxy Ace 2 GT-I8160' message for a few minutes.
After that the Samsung logo pops up and I've waited for another few minutes until a new screen pops up.
I see the Android guy and a blue progress bar underneath and patiently waits untill it's done.
After this I see the Samsung logo again and the phone finally boots to Android! Great Success!
Conclusion in my case: The 3-parted firmware seemed to do the trick for me.
As I stated above, the first flash failed but the second one was totally succesfully and revived my phone.
kolsthoorn said:
Alright, another update. (My problem seems to be fixed!)
At first I tried downloading the 3 files neccessary for the new flash method, but for some reason it'd take me hours to download them.
I started looking on the internet for the same files and found a torrent link on another forum leading to a torrent file uploaded here, on the XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=1757643&d=1361735404.
Click to expand...
Click to collapse
Yeb - you can use also the 3-parted MB4 (which was an very early JB FW).
But as the MB4 is not 100% complete - I still recommend only to use the 3-parted FWs linked by me (which ChuckMichael shows you)
But anyway - If your Phone booted you are done - You do not need to to it again. Just flash afterwards the newst original FW available.
Ive been trying to install android 7.1 on my sm-t800 now for 5 hours. I've trudged through countless posts on this forum, downloaded I dont know how many different versions of odin and the beanstown auto root and I still cant get any further.
The beans town auto root says it worked the SU icon is there but when you open it it says its not rooted. I dont know what else to do. Theres just too much different information and files floating around its overwhelming and confusing. I'm currently stuck in download mode with no apparent way to exit. Can someone please help me before this ends up as an expensive paperweight.
seanyc4 said:
Ive been trying to install android 7.1 on my sm-t800 now for 5 hours. I've trudged through countless posts on this forum, downloaded I dont know how many different versions of odin and the beanstown auto root and I still cant get any further.
The beans town auto root says it worked the SU icon is there but when you open it it says its not rooted. I dont know what else to do. Theres just too much different information and files floating around its overwhelming and confusing. I'm currently stuck in download mode with no apparent way to exit. Can someone please help me before this ends up as an expensive paperweight.
Click to expand...
Click to collapse
Have you installed TWRP? I think that's the best approach to install a custom ROM. You install TWRP with Odin, then boot into TWRP recovery and flash the ROM and Gapps with TWRP.
You've tried to use a root method that is seriously outdated by about 3 years, doesn't work any more and has been superceded.
Hey guys,
With the whole stay at home situation I stumbled upon my old Note 4 (sprint variant SM-N910p). I haven't touched it in several years, and have no clue what rom/firmware was on it, but it won'T boot. I can get into recovery but it fails to wipe anything, I was able to flash twrp (twrp-3.0.2-0-trltespr.img) through Odin, and i have tried various firmwares, but odin always fails. I have tried different cables, and even another computer. Not sure where to go from here. I only want the phone restored to factory, i do not need root. I have tried stock firmwares from sammobile aslo to no avail.
Any suggestions and help would be great!!
Thanks
Purell and be well!!!!!
If your on the latest update 5DQ15 then your locked on a fused 5, binary 4 and will be prevented from downgrading. Odin will show "sw rev check fail" when attempting to flashing a lower aboot. The firmware is at the top of the link
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Mr. JAVI said:
If your on the latest update 5DQ15 then your locked on a fused 5, binary 4 and will be prevented from downgrading. Odin will show "sw rev check fail" when attempting to flashing a lower aboot. The firmware is at the top of the link
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Click to expand...
Click to collapse
The main file download is not available from androidfilehost anymore.
if you do get it to pop through, it just doesn't download.
Do you know of an alternate source for this file??
I'm messing around with one of my old note 4's to check out the new roms without flashing my daily driver note 4. I done borked this one up long time ago, so it's wipe wiped.
Might have been a bad battery long time ago when this thing started messing up on me. doh!
sarinhighwind said:
The main file download is not available from androidfilehost anymore.
if you do get it to pop through, it just doesn't download.
Do you know of an alternate source for this file??
I'm messing around with one of my old note 4's to check out the new roms without flashing my daily driver note 4. I done borked this one up long time ago, so it's wipe wiped.
Might have been a bad battery long time ago when this thing started messing up on me. doh!
Click to expand...
Click to collapse
Looks like it works randomly. Decided to try again.
Hi all!
Got me a N975f (d2s), Note 10+ that is. Used, but in really good condition. 512GB. Not cheap, but reasonably priced. It seems unlocked also, but i have to admit that i couldn't really say even if it was not. But the CSC is NEE, nordic carriers, and that usually means unlocked.
The phone has not been used for a while and was stuck at Android 10 or so. From what i know it was untouched flashing-wise. So i started with updating firmware and got it up to the latest A12 version, NEE. I thought i would then start with flashing TWRP first. Tried the method via Odin. TWRP version 3.7.0_9-0 from the TWRP site that the dev linked to. Odin version 3.14.4. Bootloader unlocked according to the first part of the instructions. I put the twrp-tar and the vbmeta-tar in their places (AP and CP in Odin respectively). The computer has been used for similar operations with Odin, altho perhaps not in a while. Odin recognizes the device and the proper 'added' message shows.
What happens when I press 'Start' is... pretty much nothing.. Odin shows message 'analyzing file' without anything else happening regardless of how long i wait. Eventually i have to press volume down and power button to restart. I tried different cables, USB-ports, Odin versions and even different computers, both previously used for flashing. I remember also fiddling with Heimdal but i am not so familiar with it so i was afraid i would break something.
I am not a developer but i have flashed quite a few devices through the years, and I don't remember getting this kind of result ever. I contacted the developer of the TWRP and he scratched his head too.
Recently i bumped into this thread, diferent device, but basically saying that updates after certain date around late januari could render that device (T290) practically unflashable.
[ROM][OFFICIAL][13] LineageOS 20.0 for the SM-T290 (gtowifi)
WARNING: Samsung rolled out a new firmware update starting roughly at the end of January 2023. This contains bootloader version 4. From what we understand with SM-T295 bootloaders, this may or may not permanently lock you out from ever flashing...
forum.xda-developers.com
I did my updating of the Note 10+ around that time also, perhaps even february.
So now i am wondering if anything of that kind might have happened with this phone also. I am considering buying another, but they're not so cheap and I don't want to risk ending up in the same situation with another one.
Has anyone heard or experienced something similar with this phone? Is there anything else that could be done?
I would be very grateful for any answer that would point me in the right direction.
Regards
@prkfsz Your post does not qualify as Development. Please read the stickies before posting.
Questions belong in the Questions and Answers section. As a courtesy I have moved your post. Please ensure your posts remain pertinent to the sections and threads you post in.
Appologies. Thank you for moving it to the right place.
I would leave it on Android 10, good as it gets.
I prefer Pie but 10 is better than 11 or 12.
I have 2 N10+'s, one running on 9, the other 10. Neither will be upgraded! They run very well as is and security is no issue at all unless you do stupid things.
blackhawk said:
I would leave it on Android 10, good as it gets.
I prefer Pie but 10 is better than 11 or 12.
I have 2 N10+'s, one running on 9, the other 10. Neither will be upgraded! They run very well as is and security is no issue at all unless you do stupid things.
Click to expand...
Click to collapse
I am sorry but I fail at seeing exactly how your post is helping me...
Update:
Still nothing. I did manage to, using Odin, flash a bit older firmware. Same Android version (A12) but from previous year, in hope that it would change something. It didn't, the phone is still not cooperative when it comes to flashing any custom binary. I flashed back to the latest firmware, nada.
In the process of trial and error I did notice that the phone refuses to switch over controll over USB-port in the USB pulldown menu, while connected to computer. Found a thread on the forum with seemingly one person in the whole world that had the same problem. Nothing there helped.
So, long story short, the phone is flashable with stock rom, but using the same gear gets nothing. Bought a new 20€ USB-cable anyway, no difference.
I consider myself not being stubborn. So i bought another Note 10+, but cheaper and with broken screen, just to see what happens. The phone is almost identical firmware-wise, and when i got it it had been updated to the second most recent firmware, and it's from this year. Same friggin' result!
WHAT THE FRICK IS GOING ON??!!
SOLUTION:
Finally... Posting this in case other people run into the same problem.
I had tried several newest versions of TWRP with the same result. But everything else seemed to work. Even if I flashed only vbmeta, it went. So I figured that it must be something with the TWRP itself that the phone is not excepting. Kept trying and eventually found that the TWRP version 3.6.2_9-1 works. Didn't try more.