Related
hello everyone ,
my Iconia A500 , just broke down or i don't know exactly what's wrong with it ,
it's rooted stock -ICS-4.0.3 , 6 months ago
and the last thing happened in the past 3-4 days :
1- "Air Playit" was downloaded 2 days ago
2- reading news /Facebook/messenger , occasional games
3- opera browsing
that's it , no physical impacts , nothing abnormal else
now for no reasons , the tablet shut down ..
and stuck on "Android" logo ...and never past that for an hour , then it shut down
any help please with "preserving data"?
I would connect Micro USB cable to PC and device...
and see if PC recognizes device...then if you can see it in ADB or APX mode..
at least you can modify stuff with PC recognizing it..
Maybe take out External SDCARD and click it back in.
try to boot into recovery mode
mess with it when power cord is plugged into it and NOT plugged in
*** IF you are ever are able to enter into a RECOVERY mode, I'd wipe Cache + Dalvik (so it can refresh files and apps) (it doesn't erase anything, settings, apps, etc)
hope you have your CPUID #
Dought this is very helpful, APX mode saved me after my tablet was bricked for 2 months
ktmdave7 said:
1- connect Micro USB cable to PC and device...
DONE
2- see if PC recognizes device...then if you can see it in ADB or APX mode..
at least you can modify stuff with PC recognizing it..
the computer sounds like something plugged over USB however , nothing appear in my computer or device manger
3- Maybe take out External SDCARD and click it back in.
Done
4- try to boot into recovery mode
a dead robot appear with red triangular mark over his chest
5- mess with it when power cord is plugged into it and NOT plugged in
tried both ...nothing
6- *** IF you are ever are able to enter into a RECOVERY mode, I'd wipe Cache + Dalvik (so it can refresh files and apps) (it doesn't erase anything, settings, apps, etc)
how ?
7- hope you have your CPUID #
sorry , but i didn't think i'd need it , since my ONLY thing i'm doing with the tablet is reading news and browsing internet
anyway , how to get it now ?
Dought this is very helpful, APX mode saved me after my tablet was bricked for 2 months
Click to expand...
Click to collapse
help
things been done till now :
1- CPUID extraction
(1) From a PC using Blackthund3rs A500 manager
not readable
(2) From your device using Terminal Emulator App
not accessible
(3) From USBDeview must have previously used the Tab under HC with the PC you're using
only 11 digits were founds under the exact given criteria
(4) From a uid.txt in any Honeycomb-cwm backup in external_sd/clockworkmod/backup/"your_HC_backup" folder
not available
(5) From adb devices if you're running honeycomb
not available
(6) From cwm 1.7.2 via on screen display and a text file - great if you are on ICS already
not accessible
(7) From a working system in /sys/firmware/fuse/acer_cpuid
?!!?
** USB doesn't recognize the device , tried multiple ports , USB 2 , 2.1 and 3 (USB driver installed)
any more ideas ??
---------
2- tried flashing updates stock ICS
((http://forum.xda-developers.com/showthread.php?t=1874345&page=2))
41-203-01-update.zip = failed
41-206-01-update.zip = failed
41-124-01-update.zip
41-125-03-update.zip
both are not downloadable ,,, so please if anyone can upload them somewhere else ??
((http://forum.xda-developers.com/showthread.php?t=1816560))
Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy = failed
---------
3- tried access through these apps
A500 APX Flash Tool = failed (require CPUID)
A500 Manager - Utility Suite for A500 = Failed (can't recognize any sort of communications with the tablet through micro-USB)
===================
Ideas , anybody , help !!!
Acer_A500_1.031.00_WW_GEN1
Acer_A500_1.031.00_PA_CUS1
Acer_A500_1.041.00_WW_CUS1
Acer_AV041_1.054.00_WW_GEN1
all failed !!
come on guys !!
Well I wish that I could help in a way that would let you preserve your data. Hate saying it. It is probably lost. The 'save my data' prerequisite is probably why there are no answers to this point. I won't say that it is impossible, just highly unlikely. Sorry.
So if you get tired of waiting for an answer for that and just want to get your tab up and running I would humbly suggest that you consider these...
http://forum.xda-developers.com/showthread.php?t=1624645
Tons of great information and the support from the OP is legendary.
I think that you will end up at this page...
http://forum.xda-developers.com/showthread.php?t=1751978
This one is not an easy read or an easy process for those who lack Linux experience. But with a little patience you should be fine. Just be sure to read through the first few pages. There's a decent amount of information in that single thread, and not all of it is in the first post.
Once you get through those two threads you will, without a doubt, be able to continue with restoring your tablets software to something useable.
Good Luck.
Dr.GM said:
hello everyone ,
my Iconia A500 , just broke down or i don't know exactly what's wrong with it ,
it's rooted stock -ICS-4.0.3 , 6 months ago
and the last thing happened in the past 3-4 days :
1- "Air Playit" was downloaded 2 days ago
2- reading news /Facebook/messenger , occasional games
3- opera browsing
that's it , no physical impacts , nothing abnormal else
now for no reasons , the tablet shut down ..
and stuck on "Android" logo ...and never past that for an hour , then it shut down
any help please with "preserving data"?
Click to expand...
Click to collapse
I'm in the same boat. The same thing happened to me two days ago. Stock ICS + root are the only mods I've done.
I'm going to finish reading through to see if anything worked. :/
---------- Post added at 03:53 PM ---------- Previous post was at 03:42 PM ----------
In my case, I'm not so interested in preserving any data as I had already relocated everything important to GDrive and my external SD card.
First attempt, I tried booting into recovery which, I'm guessing, tried to grab an update.zip from the SD card that wasn't there. When nothing was found it proceeded to a green android boot screen and then quickly changed to a dead android with a hazard symbol on it. The boot bar below the logo crept slowly for several minutes and then stopped and hung for about an hour until I gave up.
Any quick ways to get me back to a stock blank rom?
ok , i think i'll let go for the data ... although it's VERY annoying -_- considering i did never lose any data since 1990 with dos / windows / symbian , i'm very disappointed with my first experience with Android and Acer ..
anyway here is my thoughts ,
1- first i tried All possible ways for extracting the CPUID in many forums .... except the "Ubentu" one ...which i'll give it a try soon after my surgery exam
2- another VERY annoying point honestly , it's the "inconsistency" ....
i mean , when i pressed the reset , it stopped showing me the "android-logo" , then after couple of resets , it started to show it AGAIN !!
then , doing hard reset (+vol + pwr + the or.lock) and confirmed erasing data and cache , the "android-logo" disappeared , and only ACER !!!
another , one normal reset , and it appeared again !!
ok ok ... let's forget this
i tried all 7 Stock ROMs ...
each SINGLE ROM , gave me at least 2-3 different responses !!
- the loading bar alone
- the robot with rotating thing , no loading bars
- the dead robot , no loading bar
- the robot with rotating crystal , with loading bar which get stuck at 25%-30%
- the dead robot , with loading bar which get stuck at around 20%
- Nothingness !! ( yes , it boot up from update.zip , then nothing happen)
*each trial , i gave it at least 20 min to progress up ... but with no use
anyway ,
3- i'll try again last time extracting CPUID , so i can install EUU ROMs .... but anyway ...
guys , does anyone know any relation between the S/N of the machine and the CPUID ?
just trying to think alittle bit differently , maybe , the S/N is 22 units long , so maybe there is a relation between them ?
4- if all failed , i think i'll have to wait till i get to dubai soon , because no service center in my country -_- !!
5- last resort , i'll use it as cutting table in my kitchen -_-
please guys ... help
IDEAS !!
i know you said the drivers are installed but I'm not sure they are....but try this
put your tab in manual apx mode and hook up to your pc - if theres an apx device listed then run afterOTA Lite version to get your cpuid that way...there is no relationship between the serial no and the cpuid...if nothing else works the only answer is Linux, as all the others have said
ok here what i have done ...
installed Ubuntu 12.10 ... done
installed all developer packages ...done
extracting the UID ... 0x3806148417f4317 ... done
double check ...the same result ...done
trying to convert to SBK ... FAIL
adding extra -as advised- "0" so the UID become ... 0x03806148417f4317 ...done
converting to SBK ... done
back to windows 7 ...done
trying to make "A 500 manger" or "A500 APX" detect the tablet ...fail
windows detection to APX .. done
retry "A500 manger or APX" ...fail
downgrading from "acer USB drive" 1.06 to 1.00 ....done
trying "A500 manger or APX" ...done
on "A500 APX" ... chose package 13 , put the SBK , APX detected , the tablet show "Acer" in green color with "Acer Iconia APX Mode" ... (finally something different)
"A500 APX" asks me if i saw the new "APX mode" ... yes
and then
it continued in all steps with success
till reaching " Exiting the bootloader..."
and it hangs for 30 min on that stage with no respond not what so ever !!! -_-
any ideas , guys ?? :fingers-crossed:
Dr.GM said:
ok here what i have done ...
installed Ubuntu 12.10 ... done
installed all developer packages ...done
extracting the UID ... 0x3806148417f4317 ... done
double check ...the same result ...done
trying to convert to SBK ... FAIL
adding extra -as advised- "0" so the UID become ... 0x03806148417f4317 ...done
converting to SBK ... done
Click to expand...
Click to collapse
Cpuid - take off 0x
Sent from my GT-I9300 using Tapatalk 2
3806148417f4317
and
03806148417f4317
gives me the same SBK ...
how long time should the flashing tool take till it complete its job ?
ok ...
now that's where i reached ....
and nothing happens after that
i flashed this bundle :
Bundle 13: A500 ICS BL v7 / Thor Recovery 1.7
ICS Unlocked / Skrilax Bootloader v7 and Thor Touch Recovery 1.7 (Legacy version for those with issues with 1.7.3) for the A500
using the "APX a500 flash utility" ...
then i ended up with this screen (see the attached image)
and can't pass it at all
trying SD card update.zip ...failed
trying secondary kernel ...failed
trying hard reset ...failed
so ??
ok ... back on track .... UP and RUNNING
Dr.GM said:
ok ... back on track .... UP and RUNNING
Click to expand...
Click to collapse
Hello! What did you do in the end? I have something not exactly the same, but a similar situation to yours. Your final solution could be my salvation too...... :crying:
Thanks in advance for any help.
Regards.
The tool he used flashes a custom recovery as well as the unlocked boot loader..for some reason the recover.img got corrupted...u must use the ones that come with the tool and use the tool to install it. Once u have the unlocked boot loader you're able to use a flash able zip to change it if u want.
So to answer yr question just reflash again. Choosing the bundle market option select bundle 17 its the latest version and seems most stable.
The window in the s/shot is fast boot menu, power volume up. Wiping cache helps if you are stuck on Acer boot logo
Sent from my GT-I9300 using Tapatalk 2
Hi all,
So my J7 2017 (SM-J730FZKDLUX) basically soft-bricked itself after an official update. Everything on this phone is stock and I never installed anything suspicious on it either.
The current situation is as follows:
Booting the phone normally doesn't work as it gets stuck on the first Android/Samsung screen.
Recovery and safe modes don't work at all: nothing happens.
Download/Odin mode works.
Samsung Smart Switch says my device is not supported while it's supposed to be...
Samsung Kies does not want to start on my PC and says "Update in progress. Unable to run Kies".
Even though it is still under the standard warranty, I've been told I would have to pay for the screen to be changed since the current screen has a scratch on it...
Since Download mode works, I've tried flashing the phone by following this guide from SAMmobile (https :// www(d0t)sammobile(d0t)com/firmwares/galaxy-j7/SM-J730F/LUX/download/J730FXXU3BRL3/247119/) as well as this guide from updato (https :// updato(d0t)com/firmware-archive-select-model?record=0E6D53429C5B11E89F15FA163EE8F90B).
Both result in Odin getting stuck on the "Initialzation" phase. I've searched on the Internet and people said to remove the SD card (I don't have one in that phone), remove the battery (impossible), use a different USB port (tried all of them), be quick (I click on the "Start" button as soon as the phone is "Added" in Odin), enable Debugging mode (well... I can't boot the phone...), make sure to install the Samsung drivers (done from https :// developer(d0t)samsung(d0t)com/galaxy/others/android-usb-driver-for-windows (official Samsung site), but that didn't change anything), using an older version of Odin (but which am I supposed to use? There are tens of them), make sure that Kies is not running at the same time as Odin (Kies was not even installed at the time), running Odin as admin (this is actually required otherwise it doesn't get passed the "SetupConnection" step unless I'm quick enough), use the original USB cable the phone came with (impossible, it was destroyed by my dog however the cable I'm using fits well in the USB port of phone)...
So what am I doing wrong? What can I do? Please help me!
PS: You'll note that my links are a bit weird, it's because I'm new to xda, sorry about that.
Blagatt said:
Hi all,
So my J7 2017 (SM-J730FZKDLUX) basically soft-bricked itself after an official update. Everything on this phone is stock and I never installed anything suspicious on it either.
The current situation is as follows:
Booting the phone normally doesn't work as it gets stuck on the first Android/Samsung screen.
Recovery and safe modes don't work at all: nothing happens.
Download/Odin mode works.
Samsung Smart Switch says my device is not supported while it's supposed to be...
Samsung Kies does not want to start on my PC and says "Update in progress. Unable to run Kies".
Even though it is still under the standard warranty, I've been told I would have to pay for the screen to be changed since the current screen has a scratch on it...
Since Download mode works, I've tried flashing the phone by following this guide from SAMmobile (https :// www(d0t)sammobile(d0t)com/firmwares/galaxy-j7/SM-J730F/LUX/download/J730FXXU3BRL3/247119/) as well as this guide from updato (https :// updato(d0t)com/firmware-archive-select-model?record=0E6D53429C5B11E89F15FA163EE8F90B).
Both result in Odin getting stuck on the "Initialzation" phase. I've searched on the Internet and people said to remove the SD card (I don't have one in that phone), remove the battery (impossible), use a different USB port (tried all of them), be quick (I click on the "Start" button as soon as the phone is "Added" in Odin), enable Debugging mode (well... I can't boot the phone...), make sure to install the Samsung drivers (done from https :// developer(d0t)samsung(d0t)com/galaxy/others/android-usb-driver-for-windows (official Samsung site), but that didn't change anything), using an older version of Odin (but which am I supposed to use? There are tens of them), make sure that Kies is not running at the same time as Odin (Kies was not even installed at the time), running Odin as admin (this is actually required otherwise it doesn't get passed the "SetupConnection" step unless I'm quick enough), use the original USB cable the phone came with (impossible, it was destroyed by my dog however the cable I'm using fits well in the USB port of phone)...
So what am I doing wrong? What can I do? Please help me!
PS: You'll note that my links are a bit weird, it's because I'm new to xda, sorry about that.
Click to expand...
Click to collapse
You should use the latest odin (3.13.1) and use an official samsung USB cable if possible. Not all cables (although it fits) are wired the same.
If the problem is hardware related at least you have warranty.
Blagatt said:
Hi all,
So my J7 2017 (SM-J730FZKDLUX) basically soft-bricked itself after an official update. Everything on this phone is stock and I never installed anything suspicious on it either.
The current situation is as follows:
Booting the phone normally doesn't work as it gets stuck on the first Android/Samsung screen.
Recovery and safe modes don't work at all: nothing happens.
Download/Odin mode works.
Samsung Smart Switch says my device is not supported while it's supposed to be...
Samsung Kies does not want to start on my PC and says "Update in progress. Unable to run Kies".
Even though it is still under the standard warranty, I've been told I would have to pay for the screen to be changed since the current screen has a scratch on it...
Since Download mode works, I've tried flashing the phone by following this guide from SAMmobile (https :// www(d0t)sammobile(d0t)com/firmwares/galaxy-j7/SM-J730F/LUX/download/J730FXXU3BRL3/247119/) as well as this guide from updato (https :// updato(d0t)com/firmware-archive-select-model?record=0E6D53429C5B11E89F15FA163EE8F90B).
Both result in Odin getting stuck on the "Initialzation" phase. I've searched on the Internet and people said to remove the SD card (I don't have one in that phone), remove the battery (impossible), use a different USB port (tried all of them), be quick (I click on the "Start" button as soon as the phone is "Added" in Odin), enable Debugging mode (well... I can't boot the phone...), make sure to install the Samsung drivers (done from https :// developer(d0t)samsung(d0t)com/galaxy/others/android-usb-driver-for-windows (official Samsung site), but that didn't change anything), using an older version of Odin (but which am I supposed to use? There are tens of them), make sure that Kies is not running at the same time as Odin (Kies was not even installed at the time), running Odin as admin (this is actually required otherwise it doesn't get passed the "SetupConnection" step unless I'm quick enough), use the original USB cable the phone came with (impossible, it was destroyed by my dog however the cable I'm using fits well in the USB port of phone)...
So what am I doing wrong? What can I do? Please help me!
PS: You'll note that my links are a bit weird, it's because I'm new to xda, sorry about that.
Click to expand...
Click to collapse
Tru using portronics cable it will right fit into your jack . Try it
I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!
Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.
no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
will this root onn 8 inch tablet running android 9
soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.
installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes
when you mean patch boot img do mean to unzip file on onn 8
Hi - I was after a bit of help. A friend of mine has child who has severe special needs , he has a Tab A (SM-T555) no pin set - which has suddenly stopped working. I have had a look at the device and it does not start up or enter the boot menu (despite trying every key combo).
I found that by plugging it into my computer it causes the computer to make a sound , so after a quick check in device manager i could see that it was being detected as a Qualcomm device.
I then downloaded the Qualcomm drivers and it now shows up as a com port in device manager. I grabbed QPST to see if i could get a connection to the device and nothing.
I am right at the limit of my knowledge so I am reaching out for anybody who can help.
This kids Minecraft worlds are on the tablet and are not backed up to the samsung cloud - so being able to recover these if possible would be goal 1 , getting the tablet working again would be even better but i suspect we are beyond that.
Any help is much appreciated
Mark
Update/Flash/Unbrick your device via Odin
Hello everyone! I made a tutorial regarding flashing the latest update when not available in your region: Video tutorial: Steps: 1. Download and extract both Frija and Odin. 2. Launch Frija. 3. Check the "Auto" button. Write your device's...
forum.xda-developers.com
Thanks however this wont work - the device will not go into download mode. I have already downloaded the firmware but ODIN does not see it. As far as i can understand the Qualcomm recovery mode driver is a level lower than Odin can access. I think you can use the Qualcomm tools to restore the boot loader but you need a file specific to the device to do this which Samsung do not publish - i could be horribly wrong so that is why i am asking the question here ! Let me know if i am wrong though ...
Mark
mah123 said:
Thanks however this wont work - the device will not go into download mode. I have already downloaded the firmware but ODIN does not see it. As far as i can understand the Qualcomm recovery mode driver is a level lower than Odin can access. I think you can use the Qualcomm tools to restore the boot loader but you need a file specific to the device to do this which Samsung do not publish - i could be horribly wrong so that is why i am asking the question here ! Let me know if i am wrong though ...
Mark
Click to expand...
Click to collapse
Have you tried this method to enter download mode? With tablet off, plug USB cable into the PC only. Then while pressing both vol up and down, plug the cable into the tablet.
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!
I can fix it remotely the last hope
Same Issue here,
Any one had any luck with MDM T307U. Please assist.
rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.
How to Remove MDM Control from Android?For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.
Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3