Related
Hi everyone,
everything is in the title, yesterday I bricked my Mix when I tried to install a new version via recovery (Mi Pc suite chinese version).
It updated, started working (I entered the rom) then restarted because it asked for a reset, had to say yes, when it restarted I was in a bootloop of Xiaomi logo and couldn't go into recovery mode anymore.
Only fastboot works, but still can't install rom via because I didn't unlocked the bootloader yet and didn't check for usb debugging.
Any ideas would be really appreciated.
Regards
zakenz said:
Hi everyone,
everything is in the title, yesterday I bricked my Mix when I tried to install a new version via recovery (Mi Pc suite chinese version).
It updated, started working (I entered the rom) then restarted because it asked for a reset, had to say yes, when it restarted I was in a bootloop of Xiaomi logo and couldn't go into recovery mode anymore.
Only fastboot works, but still can't install rom via because I didn't unlocked the bootloader yet and didn't check for usb debugging.
Any ideas would be really appreciated.
Regards
Click to expand...
Click to collapse
So you still be able to flash official with miflash?
When I try to flash via Mi flash it says critical partition error thing (probably because I still don't have unlock the bootloader)
zakenz said:
When I try to flash via Mi flash it says critical partition error thing (probably because I still don't have unlock the bootloader)
Click to expand...
Click to collapse
Shouldn't need unlock to install genuine ROM from xiaomi with miflash, you are using the fastboot ROM right?
Likewise USB debugging shouldn't be necessary, as far as I know. Like if you have no ROM it wouldn't know anything about USB debugging.
Yes I'm using fastboot rom
On this page: http://en.miui.com/a-234.html You can see Mi Mix is listed as it needs to unlock before any flash with fastboot.
When I try flash with MiFlash, it says Flash xbl error : https://i.imgur.com/ct0xAQY.png
zakenz said:
Yes I'm using fastboot rom
On this page: http://en.miui.com/a-234.html You can see Mi Mix is listed as it needs to unlock before any flash with fastboot.
When I try flash with MiFlash, it says Flash xbl error : https://i.imgur.com/ct0xAQY.png
Click to expand...
Click to collapse
You have unpacked the file correctly?
Think they mean if you're not using miflash.
http://xiaomitips.com/guide/how-to-flash-miui-fastboot-rom-on-mi-max-with-locked-bootloader/
Don't know if it would work on mix
Yes I did, with all the bat files the images folder.
I'll try one more time when I get home.
Or wait some days to get the unlock permissions by xiaomi
zakenz said:
Yes I did, with all the bat files the images folder.
I'll try one more time when I get home.
Or wait some days to get the unlock permissions by xiaomi
Click to expand...
Click to collapse
Might be safer to just wait. If you do it now you will have to do it again in a day.
I tried to unlock again with no success, it says error because I didn't enable the "OEM Unlock" option..
Any suggestions?
zakenz said:
I tried to unlock again with no success, it says error because I didn't enable the "OEM Unlock" option..
Any suggestions?
Click to expand...
Click to collapse
https://m.youtube.com/watch?v=4Q4MopLMprE
EDL not working on Mix models.. I already tried and it bootloops again
zakenz said:
EDL not working on Mix models.. I already tried and it bootloops again
Click to expand...
Click to collapse
Yea no edl mode but thought maybe that might work
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
james1089 said:
Yea no edl mode but thought maybe that might work
Click to expand...
Click to collapse
Just never heard of anyone been bricked when fastboot is available. Didn't read it just something to check
https://www.technobuzz.net/use-mi-pc-suite-to-flash-fastboot-rom-on-bricked-xiaomi-phones/
I'm kinda ****ed.. gotta replace it
james1089 said:
Just never heard of anyone been bricked when fastboot is available.
Click to expand...
Click to collapse
Because of bootloader not unlocked and usb debugging disabled. Thanks for help though
james1089 said:
Just never heard of anyone been bricked when fastboot is available. Didn't read it just something to check
https://www.technobuzz.net/use-mi-pc-suite-to-flash-fastboot-rom-on-bricked-xiaomi-phones/
Click to expand...
Click to collapse
I tried without success
Do you know why can't I get in recovery mode anymore ?
zakenz said:
Do you know why can't I get in recovery mode anymore ?
Click to expand...
Click to collapse
Have you tried reinstalling the recovery,
From command prompt or from the same command prompt , reboot recovery. Any of these useful?
https://www.google.co.uk/amp/s/www....0-basic-terminal-commands-you-should-know?amp
I'm sure you have disabled driver signature on Windows but just checking.
james1089 said:
Have you tried reinstalling the recovery,
From command prompt or from the same command prompt , reboot recovery. Any of these useful?
https://www.google.co.uk/amp/s/www....0-basic-terminal-commands-you-should-know?amp
Click to expand...
Click to collapse
These are all adb commands and since I don't have usb debugging enabled :/
And yes signature disabled
zakenz said:
These are all adb commands and since I don't have usb debugging enabled :/
And yes signature disabled
Click to expand...
Click to collapse
Last option is "deep flash cable" to go into edl mode, buy 1 or make 1
I have a note 5 of tmobile that the problem is that it has patron and payjoy lock
I already tried to make a hard reset but it throws me the following message:
MDM does not allow factoryReset
phone will reboot automatically
Friends remember my phone is locked with patron
and I try to start it in download mode but it does not start just turn on and already
I have z3x and usb jig and in no way boot into download mode
There will be some way to remove the pattern without debugging?
Alex1zz said:
I have a note 5 of tmobile that the problem is that it has patron and payjoy lock
I already tried to make a hard reset but it throws me the following message:
MDM does not allow factoryReset
phone will reboot automatically
Friends remember my phone is locked with patron
and I try to start it in download mode but it does not start just turn on and already
I have z3x and usb jig and in no way boot into download mode
There will be some way to remove the pattern without debugging?
Click to expand...
Click to collapse
You can remove it by first flashing a factory combination firmware then erase the persdata and persistent dev/block (mmcblk0p<x>)
Google the details.
Good luck.
U do it i can remove payjoy lock.
---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------
I can remove this pay joy app, I have do it with note5, s6 s7 and s7edge
How flash factory combination firmware if not download mode?
Can you help me!
billa said:
You can remove it by first flashing a factory combination firmware then erase the persdata and persistent dev/block (mmcblk0p<x>)
Google the details.
Good luck.
Click to expand...
Click to collapse
I just bought a Samsung Galaxy A32 form some guy and it has payjoy, I can't make calls, use thr internet and uninstall the app, please help
My phone is about to be blocked soon, I need help please
Hi I have a problem with my honor 5c so I deleted everything from the phone because I wanted to install custom rom but that didnt worked out and now I dont have system on it and twrp recovery was also deleted I unlocked bootloader but every command i type in fastboot is not working even one for oem status but if I type fastboot devices it shows my device and if I go to huawei erecovery and try to recover it it says getting package info failed and when battery discharge and I put it on charger it says
error mode
attention!
Please update system again.
Error!
Func NO: 10(boot image
Error NO: 2(load image)
I am really pissed off and I dont know what to do someone HELP ME PLEASE.:crying:
Simply u can fix
Preview:
Today I faced this issue,and successfully solved,
Shutdown mobile ,then connect to PC and quickly press volume down button automatically goes to bootloader mode , manually flash system,cust,recovery and boot img
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
Then use Dload method u can fix this issue,
Today I post some posts according to this issue on Facebook,
Honor 5c group india
But as I wrote if I go to fastboot/bootloader I cant type any command on every command it says "command not allowed" even the one for oem status and I cant turn on usb debbuging or oem unlock because I dont have os.
Hey @leoleo333, I did exactly the same thing that you did and had exactly the same problem as a result. I considered myself fairly knowledgeable about Android and Huawei/honor mobiles... I tried everything you can think of and spent months trawling the internet for a solution and was unable to fix it. I posted here on XDA and even the most knowledgeable members were unable to help. You should do a search of my XDA posts relating to this.
That said,I am using my honor 5C right now!:laugh: I didn't realise that my warranty was 24 months,I thought it was 12 months. Hence why I spent so many months trying to fix the problem myself. By chance I found out I still had warranty and sent it to the repair centre. It was so easy and straight forward and in a matter of days they had fixed and returned my beloved mobile. I even had a slight defect on the screen as a result of falling over and they even repaired that free of charge!
All I can say is that I hope and pray you have warranty :fingers-crossed: or you can kiss your mobile goodbye. Sorry. Please do let me know if you fix it yourself though, I'd be really interested to know where I went wrong. Thx.
leoleo333 said:
But as I wrote if I go to fastboot/bootloader I cant type any command on every command it says "command not allowed" even the one for oem status and I cant turn on usb debbuging or oem unlock because I dont have os.
Click to expand...
Click to collapse
Is opend erecovery mode
I used Huawei multi tool,
For installing stock recovery,
If you success to flashing stock recovery
Then use dload method
shankarjdhv125 said:
Is opend erecovery mode
I used Huawei multi tool,
For installing stock recovery,
If you success to flashing stock recovery
Then use dload method
Click to expand...
Click to collapse
He has already explained that....!
It doesnt matter if you use multi tool or manual commands...You cant flash stock recovery because every fastboot command comes back 'remote command not allowed' and this is because the os will not boot so you cant enable oem unlock and usb debugging in order to unlock bootloader and have full use of adb/fastboot.
The dload method will install the update.app, it will even go to 100% and say success but it will NOT boot the OS. It will stay stuck on boot animation until the battery dies. Search my posts here on XDA (stuck on boot logo).
I think it has to do with the partitions or the filesystem...I'm afraid i cant help you with that @leoleo333
@leoleo333 , you mention that your bootloader is unlocked...I think you should double check that. if it was unlocked you would be able to use fastboot commands and flash whatever you want. I have read many posts on XDA where members report that their bootloader is unlocked and the device says as much but in fact that is not the case! Let me know how things go. Good Luck.
I managed to fix it couple of days ago with dload method, it actually worked for me i would try it before but i did not had micro sd card
Nice, Im really glad that the dload method was all it took to fix it. Take it easy now.
Bro try this ,added screenshots ,I fixed same issue
iantechie1979 said:
He has already explained that....!
It doesnt matter if you use multi tool or manual commands...You cant flash stock recovery because every fastboot command comes back 'remote command not allowed' and this is because the os will not boot so you cant enable oem unlock and usb debugging in order to unlock bootloader and have full use of adb/fastboot.
The dload method will install the update.app, it will even go to 100% and say success but it will NOT boot the OS. It will stay stuck on boot animation until the battery dies. Search my posts here on XDA (stuck on boot logo).
I think it has to do with the partitions or the filesystem...I'm afraid i cant help you with that @leoleo333
Click to expand...
Click to collapse
Same issue fixed by me
Software install failed but successfully booted
Hello All,
Device always flashed with stock DT Germany firmware. A couple of months back I toggled OEM Unlocking (off-on-off) by mistake and next morning device reboots stating "Custom binary blocked by FRP Lock", single red line on top of screen, no other information.
I have tried to flash stock DT Germany firmware several times.Process through ODIN goes fine and completes successfully but phone reboots again in "Custom Binary blocked by FRP Lock".I can only access download mode, no other modes are available (not even recovery)
Below I have attached some screen shots of download mode and ODIN process.
https://drive.google.com/open?id=10aWMWozVCweBe3UTch9PBvvw6fboYjEQ
I have tried several combination files and all have failed.
I hope anyone has faced and sorted this out
Regards
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Munawar Mehmood said:
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Click to expand...
Click to collapse
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
besmirgogu said:
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
Click to expand...
Click to collapse
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
bober10113 said:
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
Click to expand...
Click to collapse
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
besmirgogu said:
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
Click to expand...
Click to collapse
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
bober10113 said:
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
Click to expand...
Click to collapse
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
besmirgogu said:
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
Click to expand...
Click to collapse
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
bober10113 said:
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
Click to expand...
Click to collapse
ok, thank you for your help...
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Munawar Mehmood said:
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Click to expand...
Click to collapse
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
besmirgogu said:
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
Click to expand...
Click to collapse
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Munawar Mehmood said:
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Click to expand...
Click to collapse
I am trying to understand which of the steps I am doing wrong. I managed to successfully flash a Galaxy Note 8 today so I know that laptop, cable and steps followed are fine.
What seems strange to me is that on this Galaxy Note 9 ODIN completes successfully in 2 min and 14 seconds but every time phone states CURRENT BINARY: Custom making me think that device is not being flashed at all. Any ideas how to confirm this?
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
last1youlove said:
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
Click to expand...
Click to collapse
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
besmirgogu said:
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
Click to expand...
Click to collapse
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Munawar Mehmood said:
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Click to expand...
Click to collapse
I managed to flash COMBINATION_FAC_FA81_N960FXXU3ASF1_BoxWares.tar.md5. Phone tries to reboot showing corrent model but on top of screen it says "Boot image signature check fail!!!" and "Reboot to avoid Warranty bit set!!!"
In download mode CURRENT BINARY:Custom and SYSTEM STATUS:Custom
I have added below a couple of screen shots of the situation now:
https://drive.google.com/open?id=1lwbblCDLKnvDkyBMtlsOOhH_F1c4HpeJ
i have once again gone through the entire thread and i see that you mention odin version 3.13.3, while the latest version of odin is 3.13.1. and i am using odin version 3.13.1. try this specific version of odin. and flash combination firmware. it seems from latest screen shot that your phone is not flashing any firmware. it just shows progress on pc but on phone it is not happening at all. try the odin version i mentioned.
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
last1youlove said:
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
Click to expand...
Click to collapse
you sir are making alot of sense.
Hi guys,
I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it.
As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
I'm interested too. Bump!
interested too. This is somewhat confusing, so much things changed in the past 10 years. I remember using a single app and it was done...
I was reading through magisk documentation and it was saying that devices coming with android 9 are NON-A/B and requires magisk to be installed on recovery.... However, inputting the command getprop ro.treble.enabled returns true therefore confirming the device is A/B on the command line sooooooo I'm not sure what to do or where to start reading lol
Can anyone help please
collmomo said:
interested too. This is somewhat confusing, so much things changed in the past 10 years. I remember using a single app and it was done...
I was reading through magisk documentation and it was saying that devices coming with android 9 are NON-A/B and requires magisk to be installed on recovery.... However, inputting the command getprop ro.treble.enabled returns true therefore confirming the device is A/B on the command line sooooooo I'm not sure what to do or where to start reading lol
Can anyone help please
Click to expand...
Click to collapse
getprop ro.treble.enabled does not confirm the device is A/B.
All devices released with Oreo> should return that value irrespective of their file system layout.
Samsung devices released with Pie are SYSTEM AS ROOT and A only.
Is there a root that works for the T290?
treahuggs said:
Is there a root that works for the T290?
Click to expand...
Click to collapse
With MagiskManager processed the AP file from T295 firmware.
Files boot.img;recovery.img;vbmeta.img changed.
Unlocked the bootloader, which is done in 2 stages, however the file magisk_patched.tar does not flash through ODIN
Can a line in Downloading mode KG Status: Checking interfere?
I answer my own question ... I installed a pure stock firmware for the BTU region, blocked the bootloader, made the initial configuration after a reset, went into Downloading mode, there is no KG Status line! The bootloader unlocked again, there is no KG Status line, but the problem has not disappeared - the files patched by Magisk are still not flashing ...
P.S. I came to the conclusion that the problem is in Magisk, it does not know how to work with our model ...
You need to contact the Magisk developer, but is he interested in our device?
bump --- looking to root the sm-t290
Bump
Yeah i hope a dev will be also be able to have a custom rom for it
Talich52 said:
With MagiskManager processed the AP file from T295 firmware.
Files boot.img;recovery.img;vbmeta.img changed.
Unlocked the bootloader, which is done in 2 stages, however the file magisk_patched.tar does not flash through ODIN
Can a line in Downloading mode KG Status: Checking interfere?
I answer my own question ... I installed a pure stock firmware for the BTU region, blocked the bootloader, made the initial configuration after a reset, went into Downloading mode, there is no KG Status line! The bootloader unlocked again, there is no KG Status line, but the problem has not disappeared - the files patched by Magisk are still not flashing ...
P.S. I came to the conclusion that the problem is in Magisk, it does not know how to work with our model ...
You need to contact the Magisk developer, but is he interested in our device?
Click to expand...
Click to collapse
Can you post a step-by-step explaining how you unlocked the bootloader?
Also, I found a website that has a .tar file named "T290_U1_9.0_ ROOT_ Kernel_Magisk" specifically for the SM-T290 but I can't post the link here because I am a new user. I'm not sure if it will be of any help.
I tried flashing the file on that website with Odin 3.13.1 on my tab A with download mode on but it failed with the error "RQT_CLOSE". Maybe it's because I don't have the bootloader unlocked yet? Idk. I just got the device and I'm trying to figure out how to root it, but if it's unable to be rooted it is completely fine. I also tried flashing it with two other versions of Odin; however, those versions just got stuck on "boot.img" until I manually restarted the device. Any help will be appreciated
Here is the full log when I tried flashing it on Odin 3.13.1:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 10 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Koerst said:
Can you post a step-by-step explaining how you unlocked the bootloader?
Also, I found a website that has a .tar file named "T290_U1_9.0_ ROOT_ Kernel_Magisk" specifically for the SM-T290 but I can't post the link here because I am a new user. I'm not sure if it will be of any help.
I tried flashing the file on that website with Odin 3.13.1 on my tab A with download mode on but it failed with the error "RQT_CLOSE". Maybe it's because I don't have the bootloader unlocked yet? Idk. I just got the device and I'm trying to figure out how to root it, but if it's unable to be rooted it is completely fine. I also tried flashing it with two other versions of Odin; however, those versions just got stuck on "boot.img" until I manually restarted the device. Any help will be appreciated
Click to expand...
Click to collapse
B. Unlocking Bootloader :
https://forum.xda-developers.com/showpost.php?p=80116925&postcount=1
I found a similar file for my T295 for U1 & U2, but they also do not flash
Although the bootloader is unlocked ...
Talich52 said:
B. Unlocking Bootloader :
https://forum.xda-developers.com/showpost.php?p=80116925&postcount=1
I found a similar file for my T295 for U1 & U2, but they also do not flash
Although the bootloader is unlocked ...
Click to expand...
Click to collapse
This works for the T290? What rom did you install? I would love to get away from the Samsung version.
Talich52 said:
B. Unlocking Bootloader :
https://forum.xda-developers.com/showpost.php?p=80116925&postcount=1
I found a similar file for my T295 for U1 & U2, but they also do not flash
Although the bootloader is unlocked ...
Click to expand...
Click to collapse
I appreciate the help, but the instructions on the post are unclear to me. I enabled the OEM unlocking option in developer settings, but when I tried the instructions on the post it just does not work. I am able to get into download, bootloader, and recovery modes but I'm not sure what else to do.
Koerst said:
...I enabled the OEM unlocking option in developer settings, but when I tried the instructions on the post it just does not work. I am able to get into download, bootloader, and recovery modes but I'm not sure what else to do.
Click to expand...
Click to collapse
Before entering the firmware mode, the device first enters the warning screen and here you need to press and hold the Volume Up button for more than 10 seconds, after which the device will go into reboot with data reset... After booting, the item unlock OEM will become gray and inactive, in firmware mode there will be a line OEM LOCK: OFF (U), and at each reboot there will be a warning screen that the bootloader is unlocked.
xsnipuhx said:
This works for the T290? What rom did you install? I would love to get away from the Samsung version.
Click to expand...
Click to collapse
I can't check for T290, since I have T295 ,but both models are Tab A 8.0 2019
Unfortunately, unlocking the bootloader did not give anything,I could not root the device and even install at least one custom file
Talich52 said:
Before entering the firmware mode, the device first enters the warning screen and here you need to press and hold the Volume Up button for more than 10 seconds, after which the device will go into reboot with data reset... After booting, the item unlock OEM will become gray and inactive, in firmware mode there will be a line OEM LOCK: OFF (U), and at each reboot there will be a warning screen that the bootloader is unlocked.
Click to expand...
Click to collapse
I was able to successfully unlock the bootloader after trying a number of button combinations. Thanks a lot for the help!
I will try flashing that file again soon.
Koerst said:
I was able to successfully unlock the bootloader after trying a number of button combinations. Thanks a lot for the help!
I will try flashing that file again soon.
Click to expand...
Click to collapse
What did you do to unlock your SM-T290? And for treble support, what do I choose? Arm or arm64, a only or A/B? And how would I install the GSI without a TWRP recovery?
secretwolf98 said:
What did you do to unlock your SM-T290? And for treble support, what do I choose? Arm or arm64, a only or A/B? And how would I install the GSI without a TWRP recovery?
Click to expand...
Click to collapse
These are the steps I took to unlock the bootloader that worked for me:
1. Power off the tablet (And make sure OEM unlocking is enabled in developer settings)
2. This is the part that was a little tough for me to figure out, but this is generally how I think I did it. I pressed the power button once, then instantly after I pressed one of the volume buttons (Not sure which one I pressed) and then held both volume buttons and the power button. You'll get to this screen with a bunch of text and a few options. If this way doesn't work then you should try out some other combinations.
3. One of the options on the screen is to unlock the bootloader, which tells you to hold volume up in order to unlock it.
4. The tablet will factory reset and the bootloader will be unlocked. To prove it is unlocked, the OEM unlock option in dev settings will be grayed out and will say "The bootloader is already unlocked"
I don't know about treble support or GSI, I've never actually heard of those things before and I'm sure you're much more of an expert at them than I am.
Koerst said:
These are the steps I took to unlock the bootloader that worked for me:
1. Power off the tablet (And make sure OEM unlocking is enabled in developer settings)
2. This is the part that was a little tough for me to figure out, but this is generally how I think I did it. I pressed the power button once, then instantly after I pressed one of the volume buttons (Not sure which one I pressed) and then held both volume buttons and the power button. You'll get to this screen with a bunch of text and a few options. If this way doesn't work then you should try out some other combinations.
3. One of the options on the screen is to unlock the bootloader, which tells you to hold volume up in order to unlock it.
4. The tablet will factory reset and the bootloader will be unlocked. To prove it is unlocked, the OEM unlock option in dev settings will be grayed out and will say "The bootloader is already unlocked"
I don't know about treble support or GSI, I've never actually heard of those things before and I'm sure you're much more of an expert at them than I am.
Click to expand...
Click to collapse
GitHub explanation: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
XDA explanation: https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
secretwolf98 said:
GitHub explanation: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
XDA explanation: https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
Click to expand...
Click to collapse
Thanks for the explanations.
I would like to add that to anyone who wants to attempt to unlock the bootloader, you should do so carefully and with precautions, because your device will do a factory reset and the process can even brick your device. Backup your device before you do it.
I bricked my tablet earlier today, not right after unlocking the bootloader but after a couple of times that I rebooted it and tried flashing the file that I found on that site. I was able to somehow unbrick it by wiping the cache partition and doing a factory reset. That didn't instantly unbrick it, but after one reboot I held the volume up button and somehow my tablet started up again. Whew. Anyway, I'm most likely going to stop searching for ways to root this thing. I think I have concluded that it is unrootable until further support is given by the developers of TWRP/Magisk/whoever and someone else who has more knowledge than me is able to figure something out.
Some tips for people who may need them:
- To get into recovery mode, I discovered that all you have to do is power off the tablet, then power it on again while holding both the volume up and power buttons. Then you can let go once the screen pops up.
- From recovery mode, you can wipe the cache partition, perform a factory reset, reboot the device normally, and do a bunch of other stuff. This is what I used to unbrick my tablet.
- To get into download mode (If you're trying to flash something using Odin) I could not figure out the hardware combination for it; however, I was able to get into download mode by installing the proper drivers on my computer, downloading Minimal ADB and Fastboot, connecting my tablet to my computer, and using the command "adb reboot download" on the ADB and Fastboot command prompt.
- If your tablet does get bricked (stuck on the Samsung logo) after unlocking the bootloader, try holding down the power button and see if that reboots it. If it does, do it again but this time hold the volume up button with the power button to get to recovery mode. You can try wiping the cache or resetting the device as that is what I believe worked for me.
Koerst said:
- To get into download mode (If you're trying to flash something using Odin) I could not figure out the hardware combination for it; however, I was able to get into download mode by installing the proper drivers on my computer, downloading Minimal ADB and Fastboot, connecting my tablet to my computer, and using the command "adb reboot download" on the ADB and Fastboot command prompt.
Click to expand...
Click to collapse
With the bootloader unlocked, this is simple:
Send the device to reboot, first the warning screen for the unlocked bootloader appears ... Press any volume button and see a menu where we select Recovery with the same volume buttons and press power ... the device enters ODIN mode firmware mode