1. Are you ready for the Galaxy S20? Here is everything we know so far!

Looking for a suggestion on a new device

Discussion in 'Android Lounge' started by knoober, Dec 30, 2019.

  1. knoober

    knoober Android Enthusiast
    Thread Starter

    I recently lost my trusty old ZTE Force (which I absolutely loved for its sturdy design and a couple of really stable custom roms). It had a good run, but was showing its age. I had retired it to the position of Mp3 player/knockaround device (no data/phone service). But since it is gone I need another cheap but usable device to fill the void.

    Not to sound like a choosing beggar but here is what Im looking for:

    :Easy on the pocketbook as possible, $30USD is extreme high end of my budget

    :Nothing special in the hardware dept. (dual core is good enough)

    :rootable at a minimum, but would like some sort of decent rom, mostly just to get rid of bloat, but I can manually debloat if I need to

    :would like to have as modern an OS as possible (Force had JB, but some of the apps I wanted to install didnt go as far back as JB)

    I think that is everything I need out of a device. Please let me know what you think of and TIA.
     

    Advertisement

    MrJavi likes this.
  2. MrJavi

    MrJavi Android Expert

    As far as rooting, much of it depends on device, model and carrier so before you purchase anything I would suggest searching XDA. Could you please clarify your budget? If you mean $30 U.S dollars then you might be able to go as high as a Galaxy S3 but its small , the battery drains very quickly, the OS is low (kk), and overall I dont think you be happy with it.
    A working Note 3 starts a about $50, larg screen, and 3gb rom, external sd . There are are many custom roms available for both. I've owned both and the Note 3 is way better than the S3, big time. Neither S3 or Note 3 are able to run 64bit software and Google PS has set a timeline in which it only accept 64bit apps to be submitted from developers.
    If you are able to find a rootable 64bit phone at a good price that would be better.
     
    ocnbrze and knoober like this.
  3. knoober

    knoober Android Enthusiast
    Thread Starter

    this is the kind of info I was looking for. thank you

    I've looked over the S3 a little and even with the low battery life, the small fork factor is a plus. it's got an unofficial build of Lineage 14.1 and an AOSP kernel that look like they might work as well. the kernel specifically lists undercoating and underclocking in the options, so maybe I can squeeze the battery. this one goes to the top of the maybe pile until I take a closer look at the Note or unless something else has better options or lower price tag. thanks again

    edit: yeah I meant 30 Unites States Dollars as the top range for my budget.
     
    MrJavi likes this.
  4. MrJavi

    MrJavi Android Expert

    Good luck with you search, You might find somthing you like on "Swappa".
     
  5. knoober

    knoober Android Enthusiast
    Thread Starter

    Okay so after some digging here is where I am at:

    Samsung Galaxy S3 16GB SCH-L710T for $26-ish (could be cheaper but livable)
    new sdcard (havent looked yet but planning 64gb at a reasonable price)
    one of the roms from here: https://forum.xda-developers.com/galaxy-s3-sprint/orig-development#tools

    What Im worried about is that there seems to be a load of different versions of the S3 (which btw is just a better version of my beloved Force. Same Proc/Gpu with a slightly bigger screen and more internal memory with better rom support). I would like a second opinion that I have matched the phone model with a rom that should work before I seal the deal.
     
    MrJavi likes this.
  6. MrJavi

    MrJavi Android Expert

    If your carrier is on Sprint and your from the U.S. then I had the same model. If it is the same then I'm pretty sure the latest firmware is on a higher aboot which will prevent your from downgrading. I suggest you confirm that as its been many years since I had my Sprint Galaxy S3. For example, I now have a rooted Sorint Note 4 n910p. The latest update prevents me from firmware downgrading as the aboot is a fused 5, bianary 4. Sort story, I am only able to flash MM roms. Most Samsung custom roms are developed gor specific firmwares. With my device, the roms on MM were built for earlier firmwares, flashing the all of the MM toms work fine except they data connection was no higher 3g. Having a beautiful rom with bad data spead is unacceptable. Call me stubborn but I want my cake and eat it to. LoL. I flashed a newer kernel on an older custom rom. Lets just say, Im still on the same rom and a newer kernel. I wouldn't recommend doing this on an AOSP rom. The sceen shoot Android security patch 2016 kernel hybrid N7 2017.
    The last rom I used with my S3 was CyanogenMod rom (I think 12.1).

    PS: The best way to root is with a custom recovery and always have a back-up. I keep on external sd.
     

    Attached Files:

    #6 MrJavi, Jan 1, 2020
    Last edited: Jan 1, 2020
    knoober likes this.
  7. knoober

    knoober Android Enthusiast
    Thread Starter

    quick story about this with MotoG, Moto E, Moto E4.
    Moto G was a great little phone with nice roms. I had a little issue with the official TWRP but someone reworked it and that one was fully functional. Moto E was on sale from my carrier so I upgraded. Same story, beautiful roms and smooth sailing. Then I got greedy with the Moto E4. I wanted the bigger screen and ended up with possibly the worst phone I have ever had. Don't get me wrong it isnt a bad phone, its just the most prone to breakages and the absolute most finicky for roms/recovery. The bigger screen and thinner design made it too flexible and it became curved from sitting in my back pocket. I had to dig through 3 or 4 TWRP versions to find one that worked on every boot and never found a rom (even stock based) that had working LTE. There are threads with fixes but I could never get them working, so now I live on a debloated stock rom. Cake is good, so is eating it :D
    As a side to this short story, I lost my stock nandroid for all of these devices through various problems (sd card failure then misplaced files on a desktop and for the last I somehow corrupted all the data on a different sdcard and lost everything on it). For the Moto G and Moto E, the carrier just sent a link to the stock rom on their servers, but the Moto E4 was different. Apparently Motorola was bought out or something and they were no longer allowed to give out the stock rom. Couldn't get it from Motorola either, because they just didn't post it and wouldn't respond to me about it. I eventually found one that would work from many hours of googling (all the links to stock roms on xda were 404), but there were so many variants that I was never sure I got the right one. While I did get the device working I could never take the OTAs that were pushed out for the entire life of the device. I was building real brand loyalty with Motorola up until the E4. I have no idea if the later models have corrected the problems or not. I will probably never find out either.

    Thanks for this. After the problems I described above I keep triple backups of my nandroids :D
     
    Fox Mulder and MrJavi like this.
  8. MrJavi

    MrJavi Android Expert

    "Cake is good, so is eating it :D" yes it sure is LOL

    And XDA error 404 is common issue with older threads. Same thing with my old Note 4. I hate it when that happens.
    Your wise to triple back up, I keep two one on sd and one on my laptop. As for wjat you described about lossing your back ups, you not alone, same here. The N4 is prone to bending.
    If you do instal TWRP, you might be interested in an app called Tipatch available from the Google PS and on XDA. Works fantastic with my device. If your not familiar with it heres the link

    https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217/amp/

    PS: Sorry to hear that about your Moto E4
     
    knoober likes this.
  9. knoober

    knoober Android Enthusiast
    Thread Starter

    The big issue with the bend is that over time it destroyed the phone. Either a solder joint or trace was flexed too often and now the device is nearly dead. I can still get it to power on if I flex it in the right way and perform the proper voodoo ritual before hitting the power button.

    Just to be clear though, its not a bad device. Its just the weakest I have ever had, and build quality is noticeably less than previous versions. It is definitely a budget device (which is what I gravitate towards). If I had taken care of it with the kid gloves I used for my first smart phone it would have been fine for years. But many generations of Android that were built tough had spoiled me into thinking that they could all take a beating and keep on ticking.
     
    MrJavi likes this.
  10. knoober

    knoober Android Enthusiast
    Thread Starter

    oh lord I may have played myself. I've gotten the S3 (l710t. 03) and now I find that I didn't dig far enough into xda. I haven't been at it long because my laptop keeps dying but I can't find any live links for Ron's or recoveries. I've grabbed the newest TWRP from the official repository, but haven't tested yet.

    If you (looking at you MrJavi :D) have any live links that you would like to share please let me know. In the meantime I will keep searching through all the threads on xda and here on AF.
     
    MrJavi likes this.
  11. MrJavi

    MrJavi Android Expert

    Good luck with
    Im keeping my fingers crossed and hopping for the best.

    PS: drop it and send it back as brocken on arrival ;) Just Kidding :)
     
    knoober likes this.
  12. knoober

    knoober Android Enthusiast
    Thread Starter

    Yeet. Sink or swim time I guess. Gonna have to learn to compile from source... if that doesnt 404 as well. Im sure fun will be had by all. If youve got any good tips or tricks form that I will be glad to hear them. Likewise if you still own the device and are looking at a rom that you want built... let me know because it looks like Im about to learn how :D
     
    MrJavi likes this.
  13. MrJavi

    MrJavi Android Expert

    Compiling from source is something I have very basic familiarity with and couldn't offer any useful assistance. I can, however, suggest a virtual root that can be downloaded from Google PS. Its call VMOS.
    It the T version as Im sure you already know. I check into it. Is the bootloader unlocked? Can you also provide the Software version. Look for it in the settings.
     
    #13 MrJavi, Jan 8, 2020
    Last edited: Jan 8, 2020
    knoober likes this.
  14. MrJavi

    MrJavi Android Expert

    I was not having any l much luck searching "XDA L710t" so I decided to search " Galaxy S3 L710t specs". The results I got said its T version is a Boost Mobile Galaxy S3 but it could also be a Virgin Mobile Galaxy S3 tri-band. As Im sure your already aware that lashing the wrong software will result in a hard or soft bricked device. I will say, if I were in your shoes, I would use the software version provided in the settings as a means of distinguished one from the other. Good idea to read threw everthing.


    This is for Tru-band

    https://www.google.com/amp/s/forum..../triband-modem-virgin-sph-l710t-t3364789/amp/

    https://www.google.com/amp/s/forum....st-roms-compatible-boost-mobile-t3223294/amp/

    The link below is for custom recovery (TWRP) for the both the Boost and Virgin Galaxy S3 models.

    https://forum.xda-developers.com/devdb/project/?id=9577#downloads
     
    knoober likes this.
  15. knoober

    knoober Android Enthusiast
    Thread Starter

    Thanks for the links I will give them a readthrough. BUilding a rom isnt quite as tough as I feared. There are hiccups and it isnt as easy as say, installing an OS, but it still isnt anything to break into a cold sweat over.

    I am using these guides and so far so good: (https://wiki.lineageos.org/devices/d2spr/build)
    (https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763)

    There has been issues of course, but that is what a search engine is for I guess :D

    While I learn the ins and outs of getting Lineage built (I think Ive learned enough from the process to try Ressurection Remix next) I have flashed TWRP from the official page (https://twrp.me/samsung/samsunggalaxys3sprint.html) and an Unofficial build of Lineage (https://forum.xda-developers.com/ga...om-lineage-14-1-d2spr-weekly-4-10-18-t3776142). Pretty sure my build of Lineage will be either the exact same as this one or inferior, as this gentleman likely has some experience and has added some polish to the rom that I have no clue how to do. Guessing so anyway.

    All that said: I wish I had paid better attension to the 'T' as you did. The TWRP and Rom have flashed fine (kernel as well) but something is wrong. I cant get bluetooth, or any other sound. I really dont think it is because of the L710/l710T difference, but more careful reading on my part would have made this a non issue :D I do know that the device had sound before I flashed so it is definately no the hardware. And you know, of course I got excited and didnt take a nandroid before I flashed the rom because why would I do something sensible like make a damned backup before I go poking around in a brand new device especially when I have caused myself similar troubles before?

    Anyway, my version of Lineage just finished compiling, so I am gonna flash it and see if I get any different results. Thanks again for all the help :D

    Edit: Bootloop. Shit :( Well Ive still got TWRP and the previous nandroid. And Plenty of reading to do. Ill update when there is something worth talking about :)

    Edit2: Found a stock image and it works(https://forum.xda-developers.com/showthread.php?p=53219958#post53219958). Sounds and bluetooth are back. 1 step forward and 2 steps back.
     
    #15 knoober, Jan 11, 2020
    Last edited: Jan 11, 2020
    MrJavi likes this.
  16. MrJavi

    MrJavi Android Expert

    Sorry, I hadn't noticed your reply. The first thing I noticed was NO BACKUP OMG!! LoL :) Say it isnt so. Other than that excellent and well done
    Bluetooth issues are quite common on AOSP roms. In fact a fellow member on XDA sent me a PM about Bluetooth issues and AOSP roms. Screenshot_2020-01-10.png
     
    knoober likes this.
  17. MrJavi

    MrJavi Android Expert

    knoober likes this.
  18. MrJavi

    MrJavi Android Expert

    Do yourself a big favor and check all partitions (boxs) in TWRP select external storage and press backup. Backing up data doesn't include user data. Tipach app available for download from Google PS patches TWRP to include user data when make a backing up. I highly recommend it.
     
    knoober likes this.
  19. knoober

    knoober Android Enthusiast
    Thread Starter

    ooh that one is juicy. give me a place to start digging. Ty. Here is a tidbit for you: (the link from the official lineage website directs to this, i dont think it is some shifty third party link) https://www.getdroidtips.com/lineage-os-17/#Lineage_OS_17_Supported_Devices
    TLDR: Samsung S3 is on the list to get the newest Lineage. Just in case you still have one sitting in a junk drawer somewhere. :D
    In the meantime I have put posted in the xda thread to see if the guy who built 14.1 can give me any clues as to what tweaks he has done to get his rom booting. Mine is ~5mb fatter than his so obviously somthing is different. Hopefully he doesnt get annoyed. I also found out that my phone is probably *not* the T version because TWRP says it is d2spr (L710) as opposed to d2resreshspr (L710T). Could be wrong still but its something.

    You know.... Ive wanted something that does that for so long..... its just beautiful to see that it exists. *weeps* :p

    Well for now I think I am finally going to let this thread die a bit. I will be referencing it later for links , and if I end up making a post in the device forum this will be linked for a proper history of my adventures. Thank you again for your help :)
     
    MrJavi likes this.
Loading...

Share This Page

Loading...