Related
AT&T version of this thread: http://forum.xda-developers.com/showthread.php?p=47413669
Started with N900AUCUBMI9, rooted via RDLV (N900AUCUBMI9_OneClickBin)
accepted OTA update (i know) to N900AUCUBMJ5, lost root
Wanted root back, attempted RDLV again, got SECURE CHECK FAIL : cache, stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Found this thread: http://forum.xda-developers.com/showthread.php?p=47411605
Flashed PIT ONLY, successfully booted up into MJ5, unrooted. Should have left it alone there. KNOX flag 0x0
Wanted root back, thought I could downgrade BL, AP/PDA, Phone, CPC to MI9 as suggested in above thread.
BL fails with SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1. AP/PDA, fails with SECURE CHECK FAIL : system. Phone successfully flashed to MI9. CPC fails with SECURE CHECK FAIL : cache
Stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Flashed PIT again, phone tries to boot but "Process system isn't responding" after AT&T globe boot animation, then reboots
Attempted RDLV again, get SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1, presumably because the MI9 BL can't be flashed over the MJ5 BL.
I'm stuck folks. Any suggestions welcome. Am I just going to have to wait for a stock MJ5 package/files similar to the MI9 files in the thread above?
For those reading who were dummies like me and accepted the OTA update, lost their root, tried to re-root with RDLV: flash the PIT file ONLY from the above link and you should be back into MJ5, un-rooted.
Help please?
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
LuckyColdJohnson said:
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
Click to expand...
Click to collapse
yes, that's the way i should have done it (SU persist, un-root, OTA, SU root) but I didn't and now here i am.
I followed the info to flash PIT only and my phone rebooted. Now fc's allot of stuff. Can't get past it. Build number mi9, baseband mj5. Do you think someone will make an mj5 odin? Or any advice would be greatly appreciated.
Same here
Same situation here ;_; can you post just the Pit? the zip is taking forever for the fact that I just need an XML file.
ditto
+1 I was updated and rooted and decided to jack around with a data toggle in notification (/data/data/com.android.providers.settings/databases/settings.db) and here i am
So I flashed the .pit
which let me reboot.
However now I'm in a horrible limbo state where pen imput crashes in an infanite loop making anything on the phone painful to do.
I think it's because my PDA and CSC are MI9 but my phone updated to MJ5.
I tried recovery mode wipe and "reset Phone" in settings and the issues persist.
This lovely mismatch has also rendered my ability to install firmware via Kies imposible. Nulling my plan to just roll back to stock.
Anybody have an odin one click for MJ5? I'd rather be stock than inoperable.
I'm afraid to try the method listed above for Knox flag reasons. If rolling back to MI9 is unreliable and might throw flags.
Hope someone else gets further than I have soon.
LuckyColdJohnson said:
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
Click to expand...
Click to collapse
Where is this kingo?
Sent from the phone with the best specs on the market, "NoTe III"
mnorris0678 said:
+1 I was updated and rooted and decided to jack around with a data toggle in notification (/data/data/com.android.providers.settings/databases/settings.db) and here i am
Click to expand...
Click to collapse
I soft bricked my phone probably 5 or 6 times before getting it to work!
Sent from my SAMSUNG-SM-N900A using Tapatalk
tyiphius said:
I soft bricked my phone probably 5 or 6 times before getting it to work!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Would you do us a solid, and elaborate on how you fixed it?
bloodyRevolver said:
I'm afraid to try the method listed above for Knox flag reasons. If rolling back to MI9 is unreliable and might throw flags.
Hope someone else gets further than I have soon.
Click to expand...
Click to collapse
FYI, nothing that I have domes so far has tripped KONX. Still at 0x0
bloodyRevolver said:
Would you do us a solid, and elaborate on how you fixed it?
Click to expand...
Click to collapse
+1
Sweet. Your OP lead me to believe that you tripped it somewhere. Honestly I'm beginning to care less and less about it. I honestly think that with a full ODIN of the current OTA WE'd be back in the clear. The inability to roll back after The thing updated without my permission is frustrating to say the least. Coming from iOS I'm also a bit surprised by the lack of OEM firmware existing in the wild.
settings.db
Might anybody have a stock unmodified /data/data/com.android.providers.settings/databases/settings.db file that i can try loading with adb?
Resolved issue with at&t.
Couldn't handle waiting for SM-N900A stock firmware so I took my phone to AT&T retail store (I didn't have warranty with them). They referred me to At&t Device support center and told me that I have a manufacture warranty with samsung for 1 year and since i didn't have any water damage or such, just a boot loop, i can just exchange it for a "like-new" product and might ship between 6 business days.
nikeflight19 said:
Couldn't handle waiting for SM-N900A stock firmware so I took my phone to AT&T retail store (I didn't have warranty with them). They referred me to At&t Device support center and told me that I have a manufacture warranty with samsung for 1 year and since i didn't have any water damage or such, just a boot loop, i can just exchange it for a "like-new" product and might ship between 6 business days.
Click to expand...
Click to collapse
I was offered the same deal. Preferred to hold out hope that we'd get an MJ5 firmware ripped and running before that.
Where can I find this pit file?
WHERE CAN i FIND THE PIT FILE
hunterdg said:
AT&T version of this thread: http://forum.xda-developers.com/showthread.php?p=47413669
Started with N900AUCUBMI9, rooted via RDLV (N900AUCUBMI9_OneClickBin)
accepted OTA update (i know) to N900AUCUBMJ5, lost root
Wanted root back, attempted RDLV again, got SECURE CHECK FAIL : cache, stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Found this thread: http://forum.xda-developers.com/showthread.php?p=47411605
Flashed PIT ONLY, successfully booted up into MJ5, unrooted. Should have left it alone there. KNOX flag 0x0
Wanted root back, thought I could downgrade BL, AP/PDA, Phone, CPC to MI9 as suggested in above thread.
BL fails with SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1. AP/PDA, fails with SECURE CHECK FAIL : system. Phone successfully flashed to MI9. CPC fails with SECURE CHECK FAIL : cache
Stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Flashed PIT again, phone tries to boot but "Process system isn't responding" after AT&T globe boot animation, then reboots
Attempted RDLV again, get SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1, presumably because the MI9 BL can't be flashed over the MJ5 BL.
I'm stuck folks. Any suggestions welcome. Am I just going to have to wait for a stock MJ5 package/files similar to the MI9 files in the thread above?
For those reading who were dummies like me and accepted the OTA update, lost their root, tried to re-root with RDLV: flash the PIT file ONLY from the above link and you should be back into MJ5, un-rooted.
Help please?
Click to expand...
Click to collapse
nabooki said:
WHERE CAN i FIND THE PIT FILE
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2502049
First page of the second link you posted. It's in the zip with all the other MI9 files. If you look further down the thread he also posted another version of the PIT. Read read read read.
Hello all.. Been gone for a bit. Catching up now and hoping for a solution but if anyone has figured this out, please let me know how or provide a link! (Mj5 Odin stock recovery)
Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further
Hi!
Last week I got a S2 TM-810X Retail-Tablet (9.7, Wifi, 16GB).
This tablet is for shops or so and the Retail Mode starts the Tablet after a time between 3 minutes and 3 hours (you can select it) automaticly and reset all preferences, delete all files, pictures, installed apps and any kind of user changes.
So I want to remove this firmware and first step was to try to root with Odin.
I tried rooting with all of this files.
t810_5.1.1_boot.tar
t810_cf-autoroot_5.1.1.tar
t810_twrp_LL_5.0.2.tar
twrp_2.8.7.1_LL_5.1.1_t810.tar
I had success with "t810_cf-autoroot_5.1.1.tar". I see "SuperSU"-App on my tablet now.
But if I start this app I got an error -> "SuperSU stopped".
What do you mean: Is the tablet really rooted? And what is the best way to remove the "Samsung Retail Mode"-Firmware?
BTW: I had no success with the other tree files. I got an "PASS!" in Odin indeed, but after the tablet autostarted it goes directly to the main screen and not in a screen like I got after cf-autoroot ( see at imgur.com/a/hwzMS )
Sincerly Andy
A few ideas:
http://www.naldotech.com/how-to-disable-exit-galaxy-s5-demo-live-unit-retail-mode/
This suggests changing the retail mode settings to enable factory resets and allow for odin-flashing a standard rom
http://forum.xda-developers.com/tab-s2/general/stock-collection-sm-t810-stock-odin-t3204373
That + factory reset should eliminate retail mode and have a rom that is supported by autoroot. Do you really have a 16gb model or is it 32gb?
schrimmschramm said:
Hi!
Last week I got a S2 TM-810X Retail-Tablet (9.7, Wifi, 16GB).
This tablet is for shops or so and the Retail Mode starts the Tablet after a time between 3 minutes and 3 hours (you can select it) automaticly and reset all preferences, delete all files, pictures, installed apps and any kind of user changes.
So I want to remove this firmware and first step was to try to root with Odin.
I tried rooting with all of this files.
t810_5.1.1_boot.tar
t810_cf-autoroot_5.1.1.tar
t810_twrp_LL_5.0.2.tar
twrp_2.8.7.1_LL_5.1.1_t810.tar
I had success with "t810_cf-autoroot_5.1.1.tar". I see "SuperSU"-App on my tablet now.
But if I start this app I got an error -> "SuperSU stopped".
What do you mean: Is the tablet really rooted? And what is the best way to remove the "Samsung Retail Mode"-Firmware?
BTW: I had no success with the other tree files. I got an "PASS!" in Odin indeed, but after the tablet autostarted it goes directly to the main screen and not in a screen like I got after cf-autoroot ( see at imgur.com/a/hwzMS )
Sincerly Andy
Click to expand...
Click to collapse
All you need do is ensure reactivation lock is disabled. Factory reset then flash the stock firmware.
rp3 said:
A few ideas:
http://www.naldotech.com/how-to-disable-exit-galaxy-s5-demo-live-unit-retail-mode/
This suggests changing the retail mode settings to enable factory resets and allow for odin-flashing a standard rom
Click to expand...
Click to collapse
I tried this. All the codes are working but after rebooting the retail mode is enabled again.
http://forum.xda-developers.com/tab-s2/general/stock-collection-sm-t810-stock-odin-t3204373
That + factory reset should eliminate retail mode and have a rom that is supported by autoroot. Do you really have a 16gb model or is it 32gb?
Click to expand...
Click to collapse
Tablet has 16gb.
After a lot of attempts I can boot in TWRP
But SuperSU is stopping furthermore, when I start it.
Thanks for stock-firmware-URL. I will try it.
Does anyone knows the difference between a XAR and DBT?
Sincerly
Andy
ashyx said:
All you need do is ensure reactivation lock is disabled. Factory reset then flash the stock firmware.
Click to expand...
Click to collapse
I will try it again!
Thank you very much!
Yeah! New Firmware installed!
Thank you so much you both
some more questions
Android 5.1.1 runs now on my S2 One little issue: if I install now "t810_cf-autoroot_5.1.1.tar" with Odin I run in a bootloop. Maybe there is another way to install SuperSU?
After installing "Phone Info Samsung" I can see the tablet has no IMEI. Is this normal because the tablet has no LTE or is the reason for the missing IMEI that the tablet is a retail model?
I can't open the sd card slot. When I tried to stick a needle in this small hole on the right side of the tablet nothing happens.
Maybe someone with a "normal" S2 can tell me if there is a little trick to open this slot? If not I think the reason too is that I have a retail model.
Did you install firmware for the t815 and the custom kernel?
I installed the firmware for 5.1.1.
After that I installed cf_autoroot 5.1.1
Oh, now i read that i have to install your kernel too. sorry, i will try it now.
All is fine now!
Thank you again!
schrimmschramm said:
Android 5.1.1 runs now on my S2 One little issue: if I install now "t810_cf-autoroot_5.1.1.tar" with Odin I run in a bootloop. Maybe there is another way to install SuperSU?
After installing "Phone Info Samsung" I can see the tablet has no IMEI. Is this normal because the tablet has no LTE or is the reason for the missing IMEI that the tablet is a retail model?
I can't open the sd card slot. When I tried to stick a needle in this small hole on the right side of the tablet nothing happens.
Maybe someone with a "normal" S2 can tell me if there is a little trick to open this slot? If not I think the reason too is that I have a retail model.
Click to expand...
Click to collapse
I have the same model (SM-T810X) and i can open the sd-card slot. press down fairly hard to open the slot.
i have a question for you. Did evreything went well with the software ? I am thinking of rooting myself but i am a bit afraid of causing more dammage then good.
sikkie81 said:
I have the same model (SM-T810X) and i can open the sd-card slot. press down fairly hard to open the slot.
i have a question for you. Did evreything went well with the software ? I am thinking of rooting myself but i am a bit afraid of causing more dammage then good.
Click to expand...
Click to collapse
Flashing anything is always a risk even Stock firmware however considering literally thousands have already done this success is more likely than failure.
My note 4 was bought used, no warranty. When I bought it, it was rooted, but no custom rom, worked great. Once lollipop came out, I wiped and returned to non-root and was able to get the update through tmobile. Didn't bother rerooting as things were ok. Marshmallow udpate came, and I noticed a lot of screen lag. Less than a week ago, tmobile did some sort of update and now, the phone shuts off and restarts on it's own, has very slow screen response (nothing, and then tries to do the same function 10 times in a row, messaging is very slow, types the same words several times over). I did a factory re-set twice. Once, I reloaded all my favorite apps, etc. still bad, so then I did factory reset but did not add anything or bring in my contacts, etc. I am planning on buying the note 7 in a 3-4 months, but in the meantime, would like to continue to use my note 4. I tried doing the rooting method using odin, it appeared to work ok (got the successful notice), triggered the knox thing, but..when I use a root checker, it says phone is not rooted. I am hoping that by rooting and putting a new rom on there I can fix this thing in the interim. So..suggestions on what to do next? Let me know what additional information you need. Could it be the phone itself and not the software? Suggestions on a cheap interim phone? links to relevant threads also appreciated. Is there a better way to wipe everything and start new that I am did not do? I did a factory reset. I have two batteries, which I changed out intermittently to see if it as a bad battery. Android version 6.0.1, security patch level july 1, 2016 Kernel 3.10.40-7804088
Knox version 2.6
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
more info
goosa23 said:
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
Click to expand...
Click to collapse
No to supersu? it's sm N910t, I think what finally worked what odin 3.9 version and flashed the stock that is meant to go with this particular phone to downgrade it down to lollipop. The first few times, I got fail with Odin, but realized that I had marked the option on the phone to keep it from being wiped/flashed if someone found it, once I got that off, I got a successful message. I used the following link and did all of the things mentioned on a link that I am too newbie to be allowed to post, apparently.
but it goes with 3.7 odin, flash the stock firmware from the phone model, and get to the reset button, if successul and then supersu appears.
I got as far as step 8, with odin showing the green 'reset'. But when I went back to the phone, I did not have supersu.
I've tried to do it again, but I get 'fail'
Try out the toolkit that is in the forum. https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
The link takes me to a 404 page not found, is part of it missing?
send me the link by private message so i can see what you are doing?
This weekend, I rooted my Note 8, and I learned I had no use for it since I really cannot do much with it and mobile data will not work at all. I've tried numerous times to flash everything back to the way things were via Odin 3.14.1, but all has failed. I fear if I continue, I may cause a heard brick. Is there something I am doing wrong?
IV_Flower said:
This weekend, I rooted my Note 8, and I learned I had no use for it since I really cannot do much with it and mobile data will not work at all. I've tried numerous times to flash everything back to the way things were via Odin 3.14.1, but all has failed. I fear if I continue, I may cause a heard brick. Is there something I am doing wrong?
Click to expand...
Click to collapse
Maybe. You can check with Frija for latest stock Samsung firmware files and flash it with Odin to your device.
If this does not unroot completely, you may do a factory reset. Keep in mind that this will wipe your data. So backup everything important before.
Or use another method for unfortunately your device, such as described here:
How to Root and Unroot Samsung Galaxy Note 8
In this page we are providing information on root and unroot Samsung Galaxy Note 8 smartphone with or without PC.
rootunroot.com
I was rooted and have tried to go back to stock. Mine passes but will not boot. Get a constant bootloop. I have flashed combination files then stock. Keep getting dm-verity fail in stock recovery. Recognized Contributor Jrkruse even tried to help but nothing. Have flashed stock so many times I lost count. Any ideas?