Related
OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?
OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.
Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
saywhhaa33 said:
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
Click to expand...
Click to collapse
First of all you have entered wrong model no here note 5 model no should be SM-N920xx
1)Have you enabled Oem unlocking from developers option before flashing twrp and cf-autoroot using odin? If not then you done a mistake!!
2) Have you tried to flash latest stock firmware using odin with latest usb drivers installed on you pc and proper odin flashing guide?(Flash latest 6.0.1 for your device with latest usb drivers installed on pc and connect phone to main usb port using original usb cable) After flashing stock rom if your facing bootloop then you can try reset through stock recovery (Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
3)If you can boot into twrp recovery normally then flash any custom rom suitable for your device i.e. for sm-n920p..Custom roms are pre-rooted so no need to flash cf-autoroot..Flash custom rom, if you successfully boot up the rom( It's difficult to boot custom rom though if you haven't enabled oem unlocking you will face custom binary is blocked by frp protection),then enable oem unlocking from developers option and try flashing stock rom again
4) Next option for you is download Samsung smart switch for pc, install latest usb drivers on your pc, connect your phone to pc in download mode(Press volume down+power+home button simultaneously),in smartswitch select emergency software recovery, it will ask you imei,model no and serial no which you can find either on box or back panel of your phone,smartswitch will detect latest stock firmware for your device, hit update now,give some time until update complete..Your device will be automatically reboot..If even you face bootlopp, then goto stock recovery(Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
**IF SUGGESTION IN SECOND POST HELPS YOU THEN ITS DONE, AVOID NEXT SUGGESTIONS**
Are you sure you can't install cf auto root again to solve it? IF not...
I did a search and got hits for twrp for N910P. Get it loaded, get it wiped and have another shot at success. Next way to get rid of the persistent rooter gone rogue, load up a factory BL + AP. If that doesn't work download another version and try again.
I've enabled OEM unlocking, flashed latest stock AP...BL.. And so on, factory reset in both factory and TWRP. I have also tried flashing CF Auto root again to see if that would fix it also custom ROMs bootloop except for CM13 and Lineage OS- Which is weird because the ROMs are for the SM N920C model and I'm and Sprint model, So I don't understand that. Weird!! Everything recognizes me as SM N920C except when I am in download mode. Also, having no imei or any back ups make its even harder since my computer completely crashed on me because I am unable to use Samsung smart switch due to the wrong model and null imei. So I'm completely stumped with this issue. Not sure if its a corrupted partition or folders not being in the correct folder locations along with wrong permissions, I've literally stressed everything to my knowledge about this and I'm all out of what issues this could be related to
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Sdejager2 said:
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Click to expand...
Click to collapse
1. Install official stock rom from sammobile from this link (doesn't matter which you download):
https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F
2. Load up Odin, put corresponding files to their slots, AP to AP, BL to BL, etc..
3. Boot into download mode (phone powered off, press and hol volume down + bixby button and insert cable to computer)
4. Flash it, wait for it to boot up.
Ok, I'll try that today and hopefully my next reply will be me posting from the Note. Let's hold thumbs.
Thanx
How did you solve the problem.. Same here.. Stuck at bootloop
Am unable enter in to download mode.. Tried hundreds of times
Minzlife said:
Am unable enter in to download mode.. Tried hundreds of times
Click to expand...
Click to collapse
try this
Plug your phone to pc
Hold power button + volume down for a few seconds
Then right before the phone logo shows, bixby + volume down
Now download mode shows. Flash stock rom
Hello guys, decide to mount this tutorial because I still see a lot of people with doubts, yes we already have how to root our device
I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
A tutorials too complex for some users, teaching you how to create your own Magisk modified Img boot, but I like simplicity, so if you don't want to break your head too much, here's a tip, use a successfully modified img boot , what you need is to install the rom stock that was used to create the modified boot first.
let's go to the tutorial, warning that the files posted here are not my own, and if it doesn't work, check if you're not commenting on any flaws, don't try to memorize the tutorial, follow it step by step. come on!:dedos cruzados:
1 - first follow these steps to unlock the bootloader:
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.
Now let's go to the next step, reinstall an outdated system, I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
2 - installing the stock ROM that we will use:
download this rom: https://samfrew.com/ru/download/Gal..._Wi-Fi-__/rue3/KOO/T290KSU3BUE1/T290KOO3BUE2/
OBS: a little detail about this firmware, it is made in arm32, which apparently makes it "lighter", but also has a more acidic use of RAM memory. This was the last software I installed on tab A, and I can say that the use has become better with it, but if you want to stay in the stock rom, even custom gsi didn't get such a good performance. It's worth testing, but be aware of the risks, I'm not responsible for errors.
Updating: use a modified version of Odin, to do the installations, be careful with downgrades, I managed, I was in the most current version of March, and I managed anyway using this modified Odin, but do it at your own risk, download the most current version here:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
And install via Odin, if you need more details just a Google, there are already millions of tutorials for that lol
when you get here you should already be aware that you have lost all your data, but it is necessary that the OEM option is enabled in the options, so in the CSC session use Home CSC, so that you leave the data saved, and do not lose the initial settings : )
once with successful installation, we will now install the file modified by magisk
3 - magisk Installation:
Intall TWRP: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
just follow our friend's tutorial, with a little observation, after starting the process in odin, be sure to hold the volume up button + turn on, to be redirected to the TWRP.
follow the standard steps to install magisk, if it doesn't work, you will have to manually modify the system boot.img along with magisk maneger.
if case of problem:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
I haven't had the tablet in my hands for a few months, so unfortunately I can't help more than that, as I said this was the last system I used, just because GSI are not very functional and are not always light, sometimes they crash more and it has more annoying bugs to fix that discourage daily use. my tip is, stay in stock Koo, excuses for those who can't, the most I can do now is guide them.
As a gift for you, I will teach you how to use Xposed :3
remembering, I did several tests that several times I faced bootlooops but in the end it worked for me, so notice, do it at your own risk.
5 - How to install end use EDexposed with Magisk
these versions were the ones that worked without problems in this rom
Install Riru - (Riru core) V21.0
Install Riru - Edxposed v 0.4.6.1(4510) YAHFA
Reboot, after reboot, install Edxposed Manager
and you can be happy
I thank you all for your help, and remembering that this was just a compilation of tips, to facilitate everyone, take due care to avoid problems, and don't forget to thank: 3 ?
Has anyone attempted this yet?
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
EngineeNerd said:
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
Click to expand...
Click to collapse
is the topic dead
EngineeNerd said:
is the topic dead
Click to expand...
Click to collapse
Hi friend, sorry but there are more current ways of routing, even already working on a TWRP, but now you can do the following, try using the same Firmware in the same version of the bootloader, otherwise there will always be an error, the file compressed this modified to work with Odin, I tested it myself on my T290, but I cannot guarantee its effectiveness if I try to use it in another version, I do not recommend doing this even.
I had trouble unlocking the bootloader until I did this:
After enabling OEM unlocking and turning the device off, plug in the USB cable. Hold both Vol + and Vol - at the same time, then unplug and replug the USB cable. The bootloader unlock screen should come up.
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
does this work if you're on a11?
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking o
Click to expand...
Click to collapse
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
Click to expand...
Click to collapse
what are you specifically asking? the TWRP here is very functional, but custom roms are not very stable for this tablet, some GSI behave well, but it's still better to stock debloated
WillisD said:
isso funciona se você estiver em a11?
Click to expand...
Click to collapse
I do not think so
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
MythoAegis said:
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
Click to expand...
Click to collapse
yes, you can go back to previous versions, but it gets harder when you upgrade bootloader version.
In order not to crash the downgrade, you need to look for the latest Android version you want, from your region you are in now.
An example:
I'm on the latest version ZTO - Brazil - Android 11
to get back to Android 10 I need to download the latest ZTO version with Android 9, of course you can try between different regions, but it will be a little more complicated.
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
themace51 said:
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
Click to expand...
Click to collapse
You mentioned it's on Android 11, didn't you?!
well, I don't have Tab A with me anymore, but the suggestion I give you is to try to go back to Android 10, then install TWRP, and then try to install magisk, I can give you the last firmware I installed,
currently he is with my brother.
The firmware is Koreano, as I said, it is 32bits, and super functional.
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки - 4PDA
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки
4pda.to
take a look here, search for the firmware I told you about, very good by the way
Hey
I am on T290XXU3BUC1 and i do not understand the language on the link you post
I tried your tutorial , but i am getting
sw rev check fail [aboot] Fused 3 > binary 3
hello, about that, but lately I don't have much time, but I'll update it today if I can, you probably got this error because this firmware is old.on 4pda there is a newer version with root, remembering that currently you can root through twrp, I'm going to port my last attempts here, but I notice that I don't have the tablet in my hands. use translation tools, the site is in Russian
I updated the guide as I could, any doubts I'm still here, but I can only guide, it's no longer possible to test.
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
themace51 said:
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
Click to expand...
Click to collapse
have you tried to put the firmware I mentioned? this tutorial probably won't work on android 11 one ui 3.1, i say this because the TWRP is a bit old, so as long as it's on the updated firmware it's really hard to do anything.
if you don't want the specific KOO Firmware, you can get the latest firmware version for your region which is on android 10.