Hello all togehter,
i tried to root my new Samsung A12 SM-A127F/DS with Magisk, but something went wrong.
Now i´m stuck at a but Logo with the info "This Phone is not running Samsungs´s offical Software..."
I tried to enter download mode again, but no idea how, the usual way doesn´´t work :-(
Do you have any ideas?
Thank you and best regards,
Wolfgang
BadPig-Ger said:
Hello all togehter,
i tried to root my new Samsung A12 SM-A127F/DS with Magisk, but something went wrong.
Now i´m stuck at a but Logo with the info "This Phone is not running Samsungs´s offical Software..."
I tried to enter download mode again, but no idea how, the usual way doesn´´t work :-(
Do you have any ideas?
Thank you and best regards,
Wolfgang
Click to expand...
Click to collapse
Welcome to the club of the unlucky users of the SM-A127F variant currently unknown to the XDA developers You can re-flash back your stock firmware, get it from https://samfw.com/firmware/SM-A127F. To enter the download mode you have to be quick: loosely insert the USB cable into the socket, hold the vol+ and vol- keys with one hand and once the phone reboots (screen goes blank) promptly insert the cable, still holding the keys. If the phone does not reboot by itself, then you have to be extra quick: prepare the USB cable in the socket, press vol- and power, then once the screen goes blank quickly switch the fingers to vol+ and vol- while inserting the cable with the other hand. But be reasonably careful with the socket, of course, don't break it.
By the way: did you use the patched Magisk, or the original v23? You have to use the patched version or wait until the version 24 comes out. Magisk v23 does not work on SM-A127F.
I have the same model.
Did anyone succeed in rooting it ?
hamidv2 said:
I have the same model.
Did anyone succeed in rooting it ?
Click to expand...
Click to collapse
I had successfully rooted my SM-A127F/DSN before. It shouldn't be much different from SM-A127F/DS. I've succeeded with both the patched Magisk and the self-compiled original git master. The latter method is preferred, although it is not easy to compile it. Magisk is a very powerful program, no different from the OS itself by the extent of its access, it gets very deep into the system, starts before the system and has the full access to everything, so using any patched binaries is a security risk.
Yes, getting in download mode is tricky. If you still stuck at the Samsung screen, maybe you have to clean flash your phone (i had to...)
Related
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Employee here and I had to pouch one up as well for the price of $80. Now to figure out root.
Sent from my SPH-L710 using xda app-developers app
Let us know if you get it.
I've tried Bin4ry, doomlord, tpsparky, played around with it myself a bit. Still not luck. Closest I got is normal on Bin4ry. Just when it reboots, it has no root privaledges. su is in /data/local/tmp but it fails to do anything...
I haven't messed around with it until this very moment. I will admit that the price is killer but initial impression with the device could be better. I was impressed and I mean really impressed with its quadrant score. I'll root this device later today. Black Friday sales and I am tired.
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
I found a link to root this device on both ICS and jellybean. I will personally look into it tomorrow but I will post it if you would like to go ahead. The guide itself was written for ICS but later down the thread you will find another link to a working root for jellybean.
http://androidforums.com/insignia-flex-all-things-root/661247-how-root-insignia-flex.html
Please root at your own discresion and I sure hope you purchased a protection plan (GSP) for your tablet.
also picked this up at my BB, was surprised when i walked in at 3pm and they still had about 10. i want to root too
We had a large quantity to sell as well and they all went. It is honestly not half bad. And I would really recommend getting the GSP for the tablet in case of anything. Will report back after rooting.
Let us know if you have any luck. I found the link you posted before which led me to try Bin4ry. The script seems to be updated for JB in general but still had no luck. I'm on a Mac and haven't tried any of the windows rooting apps, like posted at the bottom of that thread. I do have a windows partition and would be willing to try that method if needed. That chinese one at the bottom seems shady regardless though.. I hope there is an alternative to that
Is there a way to flash clockworkmod onto this tablet?
rekagear20 said:
Is there a way to flash clockworkmod onto this tablet?
Click to expand...
Click to collapse
I managed to get the CX-803 version of CWM for Rockchip 3066 from AndroTab.info to work by replacing its kernel with ours by unpacking and repacking with RK3xxx-Firmware-Tools by Sergio.
Note: This is for the Insignia NS-14T002 (aka iRiver NS-14T002) tablet that shipped with Android 4.2.2
Be EXTREMELY careful! Highly recommend you dump your current kernel and recovery partitions and save them somewhere before flashing anything.
If for some reason the recovery doesn't work, you can flash your stock recovery back as long as you can get back into root shell. But, if it fails to boot normally, I have no idea how to fix it. I have not been able to get any of the Rockchip flashing utilities to recognize the tablet so far, in bootloader mode (these devices have no fastboot) or otherwise. So don't blame me if you somehow brick your tablet.
You have been warned!!
CWM & Stock* Recovery image for NS-14T002
* if for some reason you can't back up your own, but again highly recommend backing up your existing recovery in case it's different from mine
You need root, and you need to do the install from root shell (don't forget to su) as described here.
I used /data/local instead of /dev - anywhere writable should be okay.
To boot into recovery:
adb reboot recovery
power off tablet, disconnect USB, press and hold Vol+ and Power until recovery comes up.
USB disconnect is not a strict requirement, but the battery status thing tends to get in the way.
In stock recovery, push Vol+ and Vol- simultaneously to bring up the menu. CWM menu should be visible at launch.
install petrus's Reboot App and use it to Reboot into recovery
Note: In CWM recovery you can swipe up for Vol+ (move up), swipe down for Vol- (move down), swipe left for Power (select), and swipe right for Back.
Re:Insignia Flex Tablet
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a problem thus far!
http://www.kingoapp.com/
cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers.
Click to expand...
Click to collapse
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
bhiga said:
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Yes my device came with 4.2.2 Jelly Bean! My first attempt using Kingo Root it did not see my device. Windows would not install the drivers needed. So I installed PDA net for windows and choose other in the program and once it was done installing it had configured the necessary drivers for Kingo Root to find my tablet and it rooted fine within a couple minutes after that! :good:
help!
klowdhaus said:
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Click to expand...
Click to collapse
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
arahmahndy said:
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
Click to expand...
Click to collapse
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Thank you!
bhiga said:
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Click to expand...
Click to collapse
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
If you can access ADB then try loading the CWM recovery I posted above. If you can at least get CWM up, at worst case I can give you a copy of my stock backup to restore.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
Did you get things sorted out?
If anyone is interested or needs it, Insignia sent me the GPL source.
You can also request it directly from them like it says on the website but it took a week or two (they might not have had a procedure in place yet, the agent had to forward my request to a different department) and I had completely forgotten until an unexpected package arrived.
Performance NS-15at10, ta120, ITQ701
Just thought someone might want to know, kingo root works, updated to 4.4.2, Booster plus battery saver pro is worth the money, better than 3c so far, still looking for more sources, any advice or help is appreciated especially for a recovery, dual bootloaders, ugh
cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a proble
Can I install drivers without PC?
Click to expand...
Click to collapse
Hey guys,
Longtime lurker but first time encountering a problem and needing to register.
I've previously ran a nethunter build on an old Nexus 6 which went fine. Now I've picked up the ZTE Axon7 as I needed a new phone.
I followed this thread: HERE
I successfully was able to follow along and get TWRP as my bootloader.
I then followed the instructions to go HERE to grab the Axon7 img file and tried the "TWRP Install" method (install the image to recovery and flash it)
Now upon reboot, I get the ZTE logo (the red dot shows up at the same time like a normal boot) then the log and dot disappear with the red dot then doing one quick flash afterwards. From there the device is just off. Even if I try doing a reboot to the bootloader via power + VolUp the same thing happens. Essentially I think this means the entire bootloader from twrp is now gone??? Plugging into my PC I still get the sound of a device connecting but it is not seen in Windows. HOWEVER while the device is connected to my PC I AM still able to see the Qualcomm port in my Device Manager.
Is there any way to go back to having an OS????? Even my backups I made??? It just seems like there isn't even the bootloader anymore and I just don't know what to do :crying:
If someone could PLEASE help it would mean the world to me!
Did you ever get this resolved?
xerxes_ said:
Hey guys,
Longtime lurker but first time encountering a problem and needing to register.
I've previously ran a nethunter build on an old Nexus 6 which went fine. Now I've picked up the ZTE Axon7 as I needed a new phone.
I followed this thread: HERE
I successfully was able to follow along and get TWRP as my bootloader.
I then followed the instructions to go HERE to grab the Axon7 img file and tried the "TWRP Install" method (install the image to recovery and flash it)
Now upon reboot, I get the ZTE logo (the red dot shows up at the same time like a normal boot) then the log and dot disappear with the red dot then doing one quick flash afterwards. From there the device is just off. Even if I try doing a reboot to the bootloader via power + VolUp the same thing happens. Essentially I think this means the entire bootloader from twrp is now gone??? Plugging into my PC I still get the sound of a device connecting but it is not seen in Windows. HOWEVER while the device is connected to my PC I AM still able to see the Qualcomm port in my Device Manager.
Is there any way to go back to having an OS????? Even my backups I made??? It just seems like there isn't even the bootloader anymore and I just don't know what to do :crying:
If someone could PLEASE help it would mean the world to me!
Click to expand...
Click to collapse
First, TWRP is a custom recovery, not a bootloader.
Second, it seems to me that your device has a locked bootloader, you have to have an UNLOCKED bootloader to flash TWRP, flashing TWRP without unlocking bootloader brocks devices. You need to restore your stock firmware.
What exactly does device manager label your device as when you connect to PC?
Sent from my SCH-I535 using Tapatalk
MelloZ said:
Did you ever get this resolved?
Click to expand...
Click to collapse
Yes, DrakenFX helped me out. Ended up being a long complicated process that I couldn't really rewrite here if I tried.
Hi folks, I’m not finding the CORRECT info on what I need to reset my phone. The following is what I have gleaned (& used) from the web sources etc.
Phone details: S6 SM-G920W8, was rooted and running Oreo quite happily (aside from telephony)
Was changing, using a TWRP BU to a Nougat TWRP BU ROM something went wrong!!!
Only have access to Odin: (Vol -/Home/Power buttons
Not able to use: Vol+/Home/Power buttons response
Used Odin to install the following file, G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5. It installs giving off the following: Pass in Odin. Phone then Reboots after install to “System Update” then “Erasing”, then Samsung Logo then "Android is starting up". After this it just loops between Logo & Android Starting.
The other file, G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5 (just checks the MD5,hit start then “Fails”
Using Odin 3.13.1 & Samsung Drivers are installed.
Anyone point me as to what I’m doing wrong please??
The 2 files used are:
G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5
G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5
C'mon guys! Someone must have some advice/help with all the expertise on this site. If the post doesn't make sense, please tell me & I'll try to re-phrase it. All I want to do is to get it up & running again in some shape or other. I have a pile of TWRP backups but no way to install them, so, I have to use Odin for something (as in the 2 .img files I referred to).
PLEASE help me!
gpreen said:
Hi folks, I’m not finding the CORRECT info on what I need to reset my phone. The following is what I have gleaned (& used) from the web sources etc.
Phone details: S6 SM-G920W8, was rooted and running Oreo quite happily (aside from telephony)
Was changing, using a TWRP BU to a Nougat TWRP BU ROM something went wrong!!!
Only have access to Odin: (Vol -/Home/Power buttons
Not able to use: Vol+/Home/Power buttons response
Used Odin to install the following file, G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5. It installs giving off the following: Pass in Odin. Phone then Reboots after install to “System Update” then “Erasing”, then Samsung Logo then "Android is starting up". After this it just loops between Logo & Android Starting.
The other file, G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5 (just checks the MD5,hit start then “Fails”
Using Odin 3.13.1 & Samsung Drivers are installed.
Anyone point me as to what I’m doing wrong please??
The 2 files used are:
G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5
G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5
Click to expand...
Click to collapse
The First File (G920W8VLS6DRC1) it flashes ok because the bootloader on your phone is "6" (Thats the fifth number in that file name) the second it fails because the Bootloader is version 6 so is only accepting version "6" and not "5" (G920W8VLU5DQD4).
To fix your problem turn off your phone pressing Vol- + Power. Keep pressing Vol+ + Home + Power (the three at the same time). its going to boot on recovery. its going to appear an Android with an X and under it "No Command (keep calm this is normal). let it there without touching anything until the recovery appears, then wipe Data+Cache and reboot it should be fixed by now.
Many, Many Thanks Razor001_. Worked like a charm once I let the Android "No Command" sit a few seconds. If only I had left it alone and been more patient with it! You truly saved me (Well my old phone anyway!).
Thanks again for your help and input.
As an aside, would I be correct that when it first went wrong and went into the Factory Reset mode, would it have installed the last version of my rooted ROM?? Please say "no" and don't make me cry with a "yes"!
[SOLVED, ANSWER BELOW]
Hi
Yesterday I tried to install TWRP Custom Recovery on my phone. I have done it before succesfully on different models.
The installation went smoothly, and I managed to boot into TWRP quickly. However the touch screen went all funky. Every little button I had to press was a difficult process, and I could barely swipe the unlock mechanism. Using the keyboard to type 'yes' for certain functions was impossible. I tried everything from aluminium foil to special gloves..
I looked up methods how to fix this and this site came up multiple times. Some solutions offered however were too complicated for me to use, because I have no knowledge on the core electronics of my device.
I decided to just leave it at this and turn off my phone. I tried going to the menu to power my phone off, however it decided pressing a lot of buttons was a better idea. I have no idea what buttons were pressed during that moment of craziness, and now I can only get my phone into the download mode. If I try to acces TWRP, it boots up to the first screen, then immediately turns off, and does it again. I can shut that process off, by pressing the power button + volume down, and then using volume up+down+power button to go into download mode.
I have the version of Odin that matches my android 9.0 Pie version, not the latest, as the latest version of Odin did not even install TWRP the first time I tried this, but the matching yet older version did.
I tried reinstalling TWRP. No luck.
I tried flashing stock firmware. I get a Complete(write) Operation failure.
I have up-to-date USB drivers
I tried Samsung Smart Switch but it does not recognize my device. I tried reinstalling my USB drivers to no avail. I used different USB ports, and a different USB cable.
I have tried to look up any and everything that may relate to this issue but I have not succeeded in finding anything that fixes my issue.
When I started the process, OEM unlock and USB Debugging was turned on. It may or may not have turned off in that crazy moment, I can't tell
All of my data is backed up or not valuable to me. A factory reset, or wipe, or whatever, is something I'm okay with. I just want my phone back.
Thank you for your help
Greetings, Jaxus
[SOLUTION]:
I decided to go ahead and use the latest Odin anyway. It worked. My touchscreen issue has been fixed, and I can go back to rooting as I expected I should be able to. I apologize if I broke any social convention in my post.
SM-A530W
I just recently ran into same'ish TWRP issues and locked up totally upon a reboot with a SM-A530W. Here's why,apparently. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 I got the "Only official released binaries are allowed to be flashed" message. Most certainly worth a read. Wow, 7 full days (168h) going unmolested, who would of guessed such.
Does Rooting work for Android 9?
I don't know what to do!!!
uwannabananababy said:
I just recently ran into same'ish TWRP issues and locked up totally upon a reboot with a SM-A530W. Here's why,apparently. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 I got the "Only official released binaries are allowed to be flashed" message. Most certainly worth a read. Wow, 7 full days (168h) going unmolested, who would of guessed such.
Click to expand...
Click to collapse
I have the same phone and I've got a similar problem I've used every odor known to man the newest one to the oldest one I can no longer load TWRP I can't root it I can't do anything please tell me what I can do thank you in advance
So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
mrjuniork said:
OEM unlock has been selected in the dev options.
Click to expand...
Click to collapse
I have the SM A326U but unfortunately I tried to see if I had the OEM Unlock options in the Developer Options Activity, and it's not there.
Do you know what the hidden activity might be when you click on the OEM Unlock? Maybe we can bring it up with an Activity Launcher?
mrjuniork said:
So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Did you try plugging into usb while holding down the buttons?
TimmyP said:
Did you try plugging into usb while holding down the buttons?
Click to expand...
Click to collapse
Yes, among other things. It just never enters that mode. It either restarts, goes into charging mode or reboots to recovery.
It's weird
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
TimmyP said:
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
Click to expand...
Click to collapse
Thx for this useful information. I could enter the download mode with this program but interestingly there is no way to use volume up button for proceeding to unlock the bootloader. Odin recognized the device properly but no way to unlock the bootloader. Isn't that strange? Also I did not see the warning screen, it went straight to the download mode screen.
I did not expect this to be such a pain...
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
TimmyP said:
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
Click to expand...
Click to collapse
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
mrjuniork said:
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
Click to expand...
Click to collapse
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
GauchoTche said:
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
Click to expand...
Click to collapse
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
mrjuniork said:
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
Click to expand...
Click to collapse
Hello, I need help with unlocking the bootloader as well. I can't find the Oem option and there is no unlock the bootloader option in download mode.