I recently bought a T560NU, in really nice shape except it's been upgraded to Nougat.
I don't know these Galaxy tablets, mostly Moto phones (have unlocked/rooted/ROM'd several) plus have rooted an Asus tablet and a couple of Samsung phones . . . I know those can't be downgraded, but I'm in the dark about Samsung tablets. Just hoping.
1. Second title-question first, as I would prefer this if it's possible: Can I downgrade Nougat on this Tab E 9.6 to Marshmallow? I have the 6.0.1 BQF1 firmware downloaded from sammobile. The phone is now running CQK2.
2. If it can't be downgraded, is it safe to install TWRP 3.1.1-1 gtelwifiue on stock Nougat? And then root with SuperSU or Magisk?
Thanks very much in advance for whatever help/advice might be offered.
I realize these questions might seem a little noobish-ignorant, but after reading that (for example) the LG G Pad 8.3 can apparently be downgraded (at least the bootloader) and it is (or used to be) necessary to downgrade the bootloader to KK before TWRP could be installed; thus I ask both questions here . . . and because after browsing (and searching) a large part of of the Tab E forum, I read a lot of general talk-around, and think, well, it would probably be okay to try installing TWRP, but I don't really get a clear and solid feeling about basic prerequisites or do's and don'ts. I just bought a nearly-brand-new SM-T560NU running Nougat 7.1.1, and you can understand I don't want to take any unnecessary chances.
So I took this specific question and answer as an endorsement for installing TWRP on a T560NU with 7.1.1 (despite reading of several problems getting TWRP on the T377x). The title of the above-referenced thread threw me, because the OP's question is not about root, it's about TWRP. I installed twrp-3.1.1-1-gtelwifiue successfully on my T560NU with Nougat, flashed via Odin clean as a whistle. Just mentioning this for posterity.
As for downgrading stock firmware, it seems like this post (xTujirox's part at the bottom) is telling me I can do that. But considering that downgrading firmware (bootloader etc) can be a much more risky proposition, I'm still waiting/hoping for a more specific response to the question before I even think about trying it.
After 10+ days of waiting I decided to bite the bullet and dive in. It was nerve-wracking, but I got 7.1.1 downgraded to 6.0.1. About 40 minutes after starting, I was thinking I'd gotten a bad download from sammobile. But I finally got it working.
It turns out all I needed to do was clear cache and wipe data (in the stock recovery, since TWRP was blown away by the firmware flash). But it was a slow walk through he11 getting there . . .
After the phone rebooted from Odin and I got the Andy screen "updating" screen, and then apps optimization for the Marshmallow "update". After optimizing 218 apps (or so I thought), the phone went into a loop where 3-4 processes kept crashing/not starting. Most critical I'm sure was "android.process.acore" and the System UI. With the System UI not starting up, it was a real trick to get a shutdown to take -- lots of quick double-thumb-taps because the error pop-ups kept obscuring power-off.
It finally did shut down, and I powered-up into recovery with no problem. Once there I wiped cache and then data/factory reset. After watching the "Samsung" screen for 10 minutes plus, Marshmallow started up clean as a whistle. Another power-down and -up to make sure it started up okay, and then back to download mode to reflash TWRP.
Again this is all for "posterity" in case anybody else comes along with the same question(s).
PS . . .
Files Used:
T560NUUEU1BQF1_T560NUXAR1BQF1_XAR.zip (downloaded from sammobile)
. . . the US or "Cellular South" version of MM 6.0.1
. . . this zip file extracts to one rar.md5 file, which is flashed in the AP slot.
twrp-3.1.1-1-gtelwifiue.img.tar
Odin 3.12.3
Related
I've rooted and replaced the ROM on 3 other Android devices. I've spent two or three nights on this. Googling and reading page after page to try to get this right. I know I'm seriously lacking in knowledge, but I just can't stand the bloatware and lack of control over an OEM ROM. I knew I was taking a risk, but I did my best to be diligent without spending an excessive amount of time. All that said, I appreciate, in advance any help anyone can offer me. Whether that's direct advice or directing me to proper resources that I can't seem to find.
Samsung S5 SM-G900P (kltespr)
I had rooted it. I replaced the Sprint stock ROM (5.0.1 I think) with CM12.1 (which just got an OTA). I had TWRP 2.8.7 on it.
Unfortunately, I needed my research suggested I needed a Touchwiz ROM in order to activate phone service on the cell provider I'd chosen (Ting).
So I selected MOAR v7 and started following the directions here:
at galaxys5root.com/sprint-galaxy-s5-custom-roms/moar-lollipop-rom-for-sprint-galaxy-s5-w-2-8ghz-oc
I made a backup. I wiped the system/cache/davlik/etc.
I installed the Android 5.0 Bootloader TAR (G900P NDK Lollipop) per the instructions via Odin and using the Bootloader option. The flash failed. I can repeat the failure (ran Odin as admin, tried multiple USB ports, restarted the computer etc). I've since tried to send several recovery ROMS or OS ROMS (pardon if I'm using the wrong terminology here) to the device, but all I can get is download mode or a screen that says Samsung Galaxy S5 powered by Android (with Kernel is not Seandroid enforcing at the top). Sending TWRP via Odin has worked with a PASS, but still can't startup the device.
I can provide more detailed logs or information about where I'm stuck and how, but on the off chance that this is an obvious thing I'm going to stop here unless more detail would be useful.
Again, I'm grateful in advance for any help.
Moshker
Follow up and how I fixed my brick
This post is intended as a follow up in case anyone runs into a similiar problem and stumbles onto my post.
After trying several different bootloaders, including the stock ones from Samsung (multiple download attempts, very slow speeds, some didn't pass md5 check), and full ROM efforts via Odin 3.10.7 I was finally able to get one ROM to take.
G900PVPU3BOG1_G900PSPT3BOG1_SPR from androidfilehost.com/?fid=24052804347794921
After getting the phone activated on Ting I used Odin to push Chainfire Auto Root (408). I verified root after restart. Used Nandroid to make a new backup. I used Flashify to install TWRP 2.8.7. I restarted to recovery and DID NOT use TWRP to wipe the system/data/etc and instead loaded the MOAR7.0.OA6 ROM. During the ROM install process it asked if I'd like to wipe system/cache/davlik/etc. I did. The ROM installed successfully. I ran a Nandroid restore to bring back my apps and data. Most restored properly.
I still don't really understand what went wrong, why my efforts to fix it failed, and why the last thing I tried worked.
Really loving MOAR. I'm using the Numix theme and it's just incredibly clean and fast. CM12.1 had intermittent micro-freezes/lags that were driving me a little nuts and MOAR is really smooth and quite fast. I was pretty disappointed in CM as I had it a long time ago on an original DInc (7.2!).
Anyway, if you're phone is bricked, keep on fighting the good fight.
Note - this is for the SM-G930A AKA AT&T model only. Unrooting and flashing firmware works the same way for other carriers, but with different files.
Hi everyone, I just thought I should share how I went about unrooting my S7. I initially rooted it while it was running Nougat already, and I liked the extra customization options. However, I found after several months of using it that the only real feature that I personally liked about having a rooted S7 was the ability to "try" paid apps for free using Lucky Patcher.
The downside of rooting, for me anyway, was severely slow laggy touch inputs and general phone performance. Sometimes - especially after a reboot - I experienced slightly better performance, but overall it just got too annoying. The app that gave me the most trouble was Google Maps. That's why I decided to cut my losses and unroot; I'd figured out which apps I actually wanted to buy since I'd already used them for a while (I will miss free in-app purchases though ).
So after some Googling and reading up, I decided to try for myself. I was already running baseband version G930AUCU4BQA4 before I rooted, so I thought maybe I could just flash stock Nougat and be done. However, all the guides I read say to flash a stock firmware, so that's what I did to be safe.
So first I downloaded the stock firmware for my phone from a website called rootmygalaxy, on the Download Stock ROM For AT&T Galaxy S7/S7 Edge (SM-G930A/SM-G935A) page (being a new user sucks).
After that, I used the stock, unpatched version of Odin v3.12.3, (from Odin's website) to flash the stock firmware onto my phone. It should be noted that the steps you take to flash a firmware to download mode should be 1. Open Odin, 2. Put phone in download mode, 3. plug the phone in. I had some failures in Odin because I was doing that wrong. Steps one and two are probably interchangeable, but just make sure plugging in the phone is the last thing you do. Also, make sure you have ticked USB Debugging and OEM Unlock under developer options before you do any flashing.
Once that was complete, I rebooted my phone and set up Android 6.0.1 on the phone. After a full 24 hours, I still couldn't get any OTA updates, so I decided to manually flash Nougat because it is so much better than Marshmallow.
This guide on the website droidviews called Install Android 7.0 Nougat on AT&T Galaxy S7/ S7 Edge (SM-G930A/ G935A) was very helpful.
Take note of the fact that the guide references baseband versions by the last 4 characters, i.e. G930AUCU4BQA4 becomes just BQA4. I checked my baseband version, which ended in APJ4. According to that guide, all I had to do was flash APK1 and then I'd be set to update to Nougat, so that's exactly what I did.
After again flashing via the 4-file method with Odin, I set up the phone again so I was back at the home screen. I downloaded both the APK1 and the .zip file containing Nougat while my phone was charging (from 90%, my phone was at ~50% by the time I had Nougat up and running), and I placed the .zip Nougat update onto an SD card that I usually keep in the phone. Once APK1 was set up, I put the SD card back in, rebooted into Recovery Mode, and waited until the manual screen came up. Then I simply chose update from SD card, chose the .zip file I'd placed in there, and waited. After a while, I was greeted by a new setup screen. I set up Nougat and now it's running just fine.
The only issue I'm seeing is that I'm still not getting any OTA updates. I hope that doesn't continue, but if it does I can just update via .zip or something.
Thanks for reading!
where did you get the nougat.zip?
Just flashed my XT1622 (UK Moto G4, NOT the plus version) using Nougat stock rom with September security patch(https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138). Thanks @tywinlannister7 who made the guide. It worked smoothly although it's in Moto G4 Plus forum.
Now, I got some questions regarding root. I did a forum search to find the post (https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918), which is quite good actually. However, I flashed my xt1622 for two reasons. The first is to upgrade to the latest system - Nougat (well, it not 'the latest' at the moment). The second is because I flashed TWRP on Marshmallow immediately after buying my Moto G4 to get root access, which stopped me to update the phone via OTA for a long time. I can still get the OTA notification, but it just won't let me update - failed after ~20 minutes. So what I did is just manually delay the update notification for 24 hours every day at 12.00pm. It bothered me a lot so I decided to go for a clean flash.
By flashing the new system, I lost some features I used quite a lot.
1. The root access for sure. I am not going to flash TWRP this time in case new patches would come over OTA again. If I flashed TWRP, I will face the same issue as I was on Marshmallow before this flashing. Is it possible to root without flashing TWRP that stops me to update over OTA?
2. I used to flash a specially made logo.bin to prevent the unlocked bootloader screen to appear. Now on Nougat, is there any similar logo.bin to do the same? A download link would be appreciated.
3. I used Llama with different profiles for some automated work such as change alarm volume at home or at workplace, make the phone ring loudly everywhere else, switch to flight mode at 12.00am at midnight and go back at 6.00am in the morning, automatically restart my phone at 1.00am while I am sleeping, and so on. This app won't work properly without root access. - well, looks like we go back to the first question of gaining root access.
Thanks for reading anyway.
Hello,
If there would be anybody who could help me in my problem I would be very grateful!
I was a happy nougat b.09 user when I tried to upgrade the phone to newest android, I installed Oreo B.04 and the phone got much slower, now tends to stutter on web browser and the battery life jumps like crazy. I went on for few weeks but now I can't take it anymore, I want to downgrade to Nougat, probably to B.12, but when I put either N-b.12 or N-FOTA-B10 to B12 from the download center thread into my sd card and rename it to update.zip, the phone still doesnt see it and I cant downgrade.
Is there a safe way to downgrade phone without root or risk of loosing data?
Btw. when I was upgrading the system few weeks ago i went form Nougat.b09 to nougat.b12 then oreo.b02, then unfortunately i downloaded nougatb.04 (mistaken it for oreo) and downgraded phone to it, repeated the process to get oreo.b04 - maybe this process made my phone slower? (but seems unlikely).
The accidental downgrade to N B04 is likely the big issue.
I would try flashing oreo B02, factory reset then flash the downgrade version of Nougat B12, not the regular one but this may actually be a case of needing an ADB connection or similar to reflash it with correct partitioning so I will defer to more experienced modders on this.
If you are on B04 Oreo right now, download the B12 package from a official ZTE source (ZTE Australia has the link for it). Same thing, rename to update.zip and put it in root for SD. If phone still doesn't detect, boot to recovery (power+volume up button), select the wipe/erase all data option first, select yes. After that, select Apply update from SD card then select the update.zip. package. Probably do another data and cache wipe just in case after its installed
Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?
Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!