Related
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Try fastbooting a recovery like TWRP thati s updated then flash a rom.
disclaimer: I might be no help at all!
You have fastboot -- go learn all the fastboot commands... you need to know the tools and figure a solution!
erase... hmm? why? What about factory reset? I see you are not using LOS 13 but stock image... need root? Basically, I would factory reset/wipe sdcard, then install recovery (TWRP) [okay, so first you would need to use fastboot to install custom recovery)...THEN, push (fastboot an image.zip (LOS or stock) to sdcards, install, and reboot!
Good to have WUG... another tool in the chest (I have never seen it or used it)
Ok, so one clue is that if your computer cannot see it, that says to me RED FLAG... ADB drivers? but you say fastboot works, hmm... I think this is the problem... Koush's universal ADB drivers? official Google drivers? Could these help!
Erasing screen? Hmm...
I would say, for the hell of it, try flashing different ROMs, Recoveries, and Drivers.... you are basically trying to...
Factory Reset/wipe SDcard [system, cache, ... everything], Flash custom recovery (optional), then, some how (fastboot or mycomputer) get an image on to /sdcard, then, install, then, reboot!
Good luck!
luckyheel said:
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Click to expand...
Click to collapse
Why not try this
I have not had this problem with my Nexus 10 but I did once with my Nexus 7 and it may help you.
Instead of trying to flash TWRP and run it (which is not working for you) why not boot into a temporary copy of TWRP and then work from that? To flash TWRP normally (persuming you had renamed the img file to TWRP which makes it easier) you would enter 'fastboot flash recovery twrp.img'. Instead of doing that type 'fastboot boot twrp.img'. This boots into TRWP and from there you will be able run all the options and from there flash TWRP and other images as normal.
If you are having problems with drivers have you used 'USBDeview' ? Run this as Administrator and delete all references to any phone or tablet USB driver and particularly look for devices with Vendor ID '18d1' or '04e8'. Just select them, right click on them and select 'Uninstall Selected Devices'. When they are all cleared reboot your computer and plug your tablet in and it should install the correct driver.
Another option I used successfully with a Nexus 7 in a boot loop was to connect it while running Linux. I don't have a Linux on a computer so I installed one in 'Oracle VM VirtualBox' I don't know Linux but after Googling for help I installed Peppermint Linux and then ADB for Linux. I downloaded the 'TWP' image into a folder in Linux and any other images I wanted. Connect your tablet to the USB port and then on the top menu in VirtualBox select 'Devices' then 'USB' and tick the option which shows your tablet. I then went into what we call a command prompt in Windows but which they call 'Terminal'. Then type 'ADB devices' and if you see it on the list use ADB instead of fastboot. As I mentioned my Nexus 7 was in a boot loop so I typed 'ADB wait-for-device' and as soon as it looped to a point where ADB could see it then the looping stopped and I could flash the images and recover the tablet.
All the best. I hope you are successful.
As long as you can get into bootloader mode, your good.
NOW
If you can't get into boot loader mode? as far as I know...
You're ****ed.
Unless you want to set up usb boot (might not work on Exynos, idk, this is magic to me) and solder the connectors and flash it like they do in factories. That's next level **** too, and considering an N10 is 100$ on amazon you're better off just grabbing a new one.
Hello all. I have owned my shield for 2 years now and for the first time attempted to root it. I made it to the twrp image and instead of loading the needed option to root it stayed on the nvidia image. I am guessing the twrp is old and there for not 8.0 twrp. At anyrate now ehen I turn on my shield it says I need to relock the boot loader and that I am not protected. My question is how do I fix this or do I need to ? Does anyone know where to find the current twrp and do I need to relock the bootloader and start over or can I finish from here ? Will I screw anything up keeping it unlocked ?
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
mLgz0rn said:
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
Click to expand...
Click to collapse
Thank you for responding ....
I am on 8.0 oreo
elderbrain said:
Thank you for responding ....
I am on 8.0 oreo
Click to expand...
Click to collapse
For Oreo there is only an experimental twrp, but you don't really need twrp to root.
You can use this guide for Nvidia Experience 7.2.3, which is Android 8.0 Oreo.
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
So to be sure, you are on Android 8.0 Oreo (Nvidia Experience 7.2.3) Correct?
And not Android 9.0 Pie (Nvidia Experience 8.0)
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
elderbrain said:
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
Click to expand...
Click to collapse
I'm using minimal adb and fastboot https://forum.xda-developers.com/showthread.php?t=2317790
Use the shortcut it makes when installed to open a command prompt.
What version of the shield do you have?
And are you booted into the bootloader?
I have the 16 gb running 8.0 oreo. I have unlocked the bootloader yes. I did every step up to loading the twrp. I used a you tube video by TT Technology. Made it to the last and final step. As of now my shield keeps disconnecting and reconnecting when connected to through usb so it does not detect any devices. I get lucky for a moment but it then stops recognizing the shield. Whats odd is that the shield is listed and I can open it and access all the storage including the mounted through the computer even when the connection drops. Right now untill i fix this issue everything else is moot.
I didn't ask if you unlocked the bootloader.
I'm asking if you are able to get into it where you do the fastboot commands?
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
elderbrain said:
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
Click to expand...
Click to collapse
If you own a SHIELD Controller
Unplug SHIELD TV.
Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
While holding the A and B buttons at the same time, connect power to SHIELD TV.
If you do not own a SHIELD controller
Unplug SHIELD TV.
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Click to expand...
Click to collapse
This will get you into the bootloader, and you should be able to use fastboot commands
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
elderbrain said:
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
Click to expand...
Click to collapse
Oh my bad, I didn't think you were able to boot.
Have you enabled usb debugging on the shield in the developer options?
Anyways, that error is usually because of using an out of date adb.
try this minimal adb and fastboot
https://www.androidfilehost.com/?fid=745425885120698566
Yes. I have made sure all 3 possible options where enabled, from developer options to usb debugging. I even got the message to allow it always on this device. I have full access to the shield through usb and it appears in my DM.........I have tried all three versions I can find for minimal fastboot. v 14.1......1.4.3 and the one you said to try 1.4.2. All have the same message. It just either does not detect a device or it says its offline. I have pretty much thrown in the towel at this point as all options have been attempted and hours of googling where wasted. I really have no idea where to go now. I tried resetting the shield a few times.....then tried revoking usb and re enabling and nothing will get it to connect to the deamon. Thank you for all the help. I appreciate you trying
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Roamin64 said:
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Click to expand...
Click to collapse
I have all but gave uop at this point, but to answer your question. My shield works and runs it is just in the state where the bootloader is unlocked and I get the warning. I have attempted the instructions before, holding down the a and b keys on both the game controller and a wired keyboard and it does nothing. I agree that the twrp is not current and that I need the proper files. As of now my shield is just not recognized period. That is why holding down the aand b keys does not work ( IE it in the command prompt it says shield is offline or it sees it and when I enter fastboot it just says waiting for device and does nothing more. So half way through it looses connection to the shield ) Untill I can get the shield to be recognized none of these instructions matter. As of now I have decided to give up and maybe in a while try again. I would like to completely restore my shield to the state it was in so I can start from scratch. That is what I am focusing on now, but untill my shield is recognized I dont think even that is possible. Thanks for your post. I appreciate all the help all of you have offered.
Impossible d'accéder au recovery
Bonjour j'ai fait une erreur de flashing, le fimware de NVIDIA Shield TV n'était pas bon, donc le logo NVIDIA reste bloqué, j'ai essayé de faire a et b mais impossible d'accéder au booloader et au recovery comme faire ?
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
Hello,
I've got a Galaxy Tab S5e which I want to boot when I insert a usb cable for charging.
I've tried using the fastboot oem off-mode-charge 0 command but whatever I try fastboot keeps waiting for devices.
Tried updating the USB driver already.
When I have my tablet connected and it's normally booted adb devices shows the device. When I then reboot into bootloader using adb reboot bootloader, it's no longer showing devices when I try fastboot devices.
What am I missing here?
Is there another solution to this problem?
Hope someone can help me out.
Thnx!
Hi
Firstly I do not know if fastboot commands work with samsung, that is why we have to use Odin to flash roms
I am on stock ROM and have the exact opposite problem.
I rooted using magisk following the excellent guide in xda
I then installed a magisk patched version of twrp using the official twrp installer. (detailed in post 232 of the S5e root thread)
This left me with three issues.
1 The tablet would be rooted weather I booted into system or recovery.
2 The adb would not connect or said device was offline
3 The tablet would boot up when plugged in to the charger.
Wiping the cache in twrp corrected the first 2 but has left me with a tablet that boots when charging cable is plugged in
So if you want a rooted tablet that boots on charging this may be the way to go only I don't yet know how to reverse it!
And of course it may not work that way with older or newer firmware
Extall
Hi, thanks for the answer.
I followed this brilliant guide to root indeed.
After that I've changed this file : /system/bin/playlpm. The source for this is here.
I've changed it to:
#!/system/bin/sh
sleep 20
/system/bin/reboot
Works like a charm. Device is rooted but I don't care. I hope future firmware will still support this but I think I'm going to make a clone using the backup feature of TWRP. This way I can always go back to this point.
In my case, the device is only used with one app. It boots on power and starts the app with Surelock. It's used in a museum.
Thanks for the answer, I had the same solution
Kind regards,
Marcel
Hello there,
I am a very, very, very newbie in mobile and android, event the vocabulary is new, so please be indulgent. Moreover, I am old school and running Linux (opensuse Leap 15.2) and I hate GAFAM stuff.
I got an old Galaxy S6 SM-G920F. I don't have access to it, no SIM card, I'd guess no data. I want to learn how to change the OS (I think the good word is mod) to something like Lineage.
I have read a lot but there has been evolution in methods and I can't find the easy way to do it.
As it seems WINDOWS OS is needed to success, I installed WIN 10 in a laptop (what a chit!). BUT if you have a way to go with Linux, please I'd prefer.
First I wand to know the main part of the process. I think the first on is to unlock the bootloader.
I tried the following in the phone: Press and hold three physical keys of Home, Power and Volume Down. Release them when the screen is lightning, and then press the Volume Up key. I got on the screen:
Code:
ODIN MODE
PRODUCT NAME: SM-G620F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download : Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:5 K:2 S:2
I'd guess the bootloader is unlocked, could you confirm?
Now, what to do? Could you
- Explain the main steps without detail then
- Point me on a good recent HowTo or write it here.
Many thanks for your help
Edit: BTW what does mean debloat and deknox?
MrNice said:
Hello there,
I am a very, very, very newbie in mobile and android, event the vocabulary is new, so please be indulgent. Moreover, I am old school and running Linux (opensuse Leap 15.2) and I hate GAFAM stuff.
I got an old Galaxy S6 SM-G920F. I don't have access to it, no SIM card, I'd guess no data. I want to learn how to change the OS (I think the good word is mod) to something like Lineage.
I have read a lot but there has been evolution in methods and I can't find the easy way to do it.
As it seems WINDOWS OS is needed to success, I installed WIN 10 in a laptop (what a chit!). BUT if you have a way to go with Linux, please I'd prefer.
First I wand to know the main part of the process. I think the first on is to unlock the bootloader.
I tried the following in the phone: Press and hold three physical keys of Home, Power and Volume Down. Release them when the screen is lightning, and then press the Volume Up key. I got on the screen:
Code:
ODIN MODE
PRODUCT NAME: SM-G620F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download : Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:5 K:2 S:2
I'd guess the bootloader is unlocked, could you confirm?
Now, what to do? Could you
- Explain the main steps without detail then
- Point me on a good recent HowTo or write it here.
Many thanks for your help
Edit: BTW what does mean debloat and deknox?
Click to expand...
Click to collapse
Hello,
as I have installed a custom ROM myself on my S6 G920f only a few weeks ago, I can help you out as far as my knowledge goes and as far as I haven't forgotten it. Bear in mind though that I am not an expert and had to look up a lot of stuff myself.
First, after trying many different up-to-date ROMs and after becoming very frustrated, I kind of accepted that there is currently no up-to-date ROM for the S6 that does not have one or the other big flaw. Some didn't even Boot and instead did load for 5 minutes and rebooted into twrp. The critical flaws on the others were random shutdowns, microphone issues ranging from my voice not being transmitted at all to constant feedback where the other person was hearing her or his voice. The feedback issue I experienced on all the ROMs. Also, with the ROM that I thought I could arrange with I noticed that sometimes, randomly, the calls coming in were just blocked/didn't come through for whatever reason. Also, fast charging is an issue and the camera is bad since you won't have Samsung's camera app and the necessary framework that optimizes it. Google safety net was a big issue with the Android 10 ROMs too, but magiskhide props solved that for me.
I'm sure many people have different reasons to use ROMs but for me it was just not worth it at this time. Maybe this will change later. Just wanting to let you know since you asked for it. I found my current happy place with the Marduk Stock Rom which you can find in the S6 Development section. It is based on the stock ROM which is Android 7, I find it to be fast, it has a good battery life and for me it is very stable. Also no microphone or connectivity issues, fast charging works only with screen off, camera is good since it's the original camera app. No google safety net issue.
Now to your questions.
Debloat means the pre-installed apps that you cannot uninstall and that clutter your phone are removed. Deknoxed as far as I know refers to Samsungs knox which is a safety plus as long as you use your phone unrooted but (tries to) restrict rooting and installing custom ROMs etc. Don't know much more than that tho.
Yes, your bootloader seems to be unlocked.
Now install twrp first. Go to twrp website and download the version you need for your phone. To flash TWRP recovery, you don't need odin. I have used heimdall myself and found it to be very easy.
- Install heimdall. You can also install samsung usb driver for linux if you have issues connecting your phone to your pc.
- Boot into Download Mode (For me volume down + home button + power button)
- Have phone plugged in to pc and at least 60% charge
- Start Terminal, Cd into folder with your recovery.img and use this command to install your recovery (of course replace "recovery.img" with your recovery):
heimdall flash --RECOVERY recovery.img --no-reboot
- Now turn your phone off, and since my phone automatically rebooted at this point, try to stop this by instantly using your key combo as soon as the screen turns black to boot into recovery mode (volume up+home button + power). I had issues here. If you don't manage to do this and get stuck in bootloop just boot into download mode again and install recovery once more to try again.
- Now you can download your preferred rom, boot your phone into twrp recovery and connect to your pc to copy, wipe everything in twrp (obviously save any file you'd like to keep) and install your Custom ROM.
- Most ROMs (but not all! read ROM description!) come without GAPPS installed so you will have to download and install it manually after you have installed your ROM (I recommend GAPPS pico for your custom ROM version). You don't have to do this if you don't want to use google applications.
- Before leaving twrp and booting into your OS install Magisk in TWRP(Download latest version and install in twrp after GAPPs).
- Wipe Cache/Dalvik
- Now reboot into System (and don't install TWRP manager system app)
- Install Magisk Manager after after restart
ROMs:
The best LineageOS ROM I have found to be this: https://lineageos.wickenberg.nu/zerofltexx
It seemed to have the least amount of flaws. The bugs for me were no fast charging unless you reboot plugged in. So no fast charging when you plugin and dont reboot and stay plugged in after reboot. Random connectivity issues. Microphone feedback. Camera crashes and camera issues whilst videocalling etc. Google safety net failure by default, but you can fix this with MagiskHide Props.
Haven't tried the Pixel one here but it seems to have the same microphone issue where nobody can hear your voice.
The Marduk Debloated Stock ROM, also here on XDA, is based on the older Android 7.0 but works very well. Lacks the extended settings and features you find on LineageOS, but least buggy and fast and battery efficient.
Have fun
waffelschnitten said:
Hello,
as I have installed a custom ROM myself on my S6 G920f only a few weeks ago, I can help you out as far as my knowledge goes and as far as I haven't forgotten it. Bear in mind though that I am not an expert and had to look up a lot of stuff myself.
First, after trying many different up-to-date ROMs and after becoming very frustrated, I kind of accepted that there is currently no up-to-date ROM for the S6 that does not have one or the other big flaw. Some didn't even Boot and instead did load for 5 minutes and rebooted into twrp. The critical flaws on the others were random shutdowns, microphone issues ranging from my voice not being transmitted at all to constant feedback where the other person was hearing her or his voice. The feedback issue I experienced on all the ROMs. Also, with the ROM that I thought I could arrange with I noticed that sometimes, randomly, the calls coming in were just blocked/didn't come through for whatever reason. Also, fast charging is an issue and the camera is bad since you won't have Samsung's camera app and the necessary framework that optimizes it. Google safety net was a big issue with the Android 10 ROMs too, but magiskhide props solved that for me.
I'm sure many people have different reasons to use ROMs but for me it was just not worth it at this time. Maybe this will change later. Just wanting to let you know since you asked for it. I found my current happy place with the Marduk Stock Rom which you can find in the S6 Development section. It is based on the stock ROM which is Android 7, I find it to be fast, it has a good battery life and for me it is very stable. Also no microphone or connectivity issues, fast charging works only with screen off, camera is good since it's the original camera app. No google safety net issue.
Now to your questions.
Debloat means the pre-installed apps that you cannot uninstall and that clutter your phone are removed. Deknoxed as far as I know refers to Samsungs knox which is a safety plus as long as you use your phone unrooted but (tries to) restrict rooting and installing custom ROMs etc. Don't know much more than that tho.
Yes, your bootloader seems to be unlocked.
Now install twrp first. Go to twrp website and download the version you need for your phone. To flash TWRP recovery, you don't need odin. I have used heimdall myself and found it to be very easy.
- Install heimdall. You can also install samsung usb driver for linux if you have issues connecting your phone to your pc.
- Boot into Download Mode (For me volume down + home button + power button)
- Have phone plugged in to pc and at least 60% charge
- Start Terminal, Cd into folder with your recovery.img and use this command to install your recovery (of course replace "recovery.img" with your recovery):
heimdall flash --RECOVERY recovery.img --no-reboot
- Now turn your phone off, and since my phone automatically rebooted at this point, try to stop this by instantly using your key combo as soon as the screen turns black to boot into recovery mode (volume up+home button + power). I had issues here. If you don't manage to do this and get stuck in bootloop just boot into download mode again and install recovery once more to try again.
- Now you can download your preferred rom, boot your phone into twrp recovery and connect to your pc to copy, wipe everything in twrp (obviously save any file you'd like to keep) and install your Custom ROM.
- Most ROMs (but not all! read ROM description!) come without GAPPS installed so you will have to download and install it manually after you have installed your ROM (I recommend GAPPS pico for your custom ROM version). You don't have to do this if you don't want to use google applications.
- Before leaving twrp and booting into your OS install Magisk in TWRP(Download latest version and install in twrp after GAPPs).
- Wipe Cache/Dalvik
- Now reboot into System (and don't install TWRP manager system app)
- Install Magisk Manager after after restart
ROMs:
The best LineageOS ROM I have found to be this: https://lineageos.wickenberg.nu/zerofltexx
It seemed to have the least amount of flaws. The bugs for me were no fast charging unless you reboot plugged in. So no fast charging when you plugin and dont reboot and stay plugged in after reboot. Random connectivity issues. Microphone feedback. Camera crashes and camera issues whilst videocalling etc. Google safety net failure by default, but you can fix this with MagiskHide Props.
Haven't tried the Pixel one here but it seems to have the same microphone issue where nobody can hear your voice.
The Marduk Debloated Stock ROM, also here on XDA, is based on the older Android 7.0 but works very well. Lacks the extended settings and features you find on LineageOS, but least buggy and fast and battery efficient.
Have fun
Click to expand...
Click to collapse
Thank you waffelschnitten (no waffel icon) for your extensive answer.
I've learn a lot yet.
As this phone is for experiment, I'll try your Howto.
Forgive my ignorance but the first step is not clear for me. TWRP looks to be an Android app. So I have to install it on the phone, but as I mentioned in my previous post I can't access in it, I don't have the code.
Is it possible to bypass the code? Maybe this device is only good for the recycling? Could you be more accurate in the process?
No worries. No your device should be fine.
TWRP stands for Team Win Recovery Project. It is a Custom Recovery System, it's not an app. You don't need to boot into your System OS to install it. You have to flash it onto your phone by using the Samsung Download Mode. Only with a Custom Recovery System such as TWRP you can easily install new ROMs, Root your phone etc.
To install TWRP, you first need to download TWRP for the S6 onto your PC: https://eu.dl.twrp.me/zeroflte/. Download the .img file version.
Now you have to boot into the S6 Download Mode. To do this, make sure your phone is turned off. Then boot it up by pressing and holding Volume Down Button+Home Button+Power Button at the same time for a few seconds. This should get you into Download Mode.
When in Download Mode, connect your phone to your Linux PC via USB.
Make sure you have installed heimdall on Linux. Start Linux Terminal. Remember, your phone should be connected to your PC and in Download Mode. Now check if heimdall detects your phone with this command:
heimdall detect
If it is not detected, try and install Samsung USB drivers for Linux.
If it is detected, navigate to the folder with the TWRP file in your Linux Terminal with the Cd command.
Then, flash your twrp.img file on your phone with this command:
heimdall flash --RECOVERY recovery.img --no-reboot
Replace recovery.img with your twrp.img file. For the latest one it should be twrp-3.3.1-0-zeroflte.img
So this would be the command:
heimdall flash --RECOVERY twrp-3.3.1-0-zeroflte.img --no-reboot
Just to make sure, do you know how to navigate/use the linux terminal?
If you have followed these steps, you should have installed your Custom Recovery. With this you have access to your File System etc. Continue as described in my first reply. As already said, to boot into your newly installed TWRP recovery, you have to press Volume up+Home Button+Power Button at the same time and hold for a few seconds, even after the S6 logo appears.
Many, many thanks,
I am not too bad with Linux, user for around 10 years, only newbie with mobile devices and Android.
I had to wait long time for the battery be empty and the phone power off. I can't find other way with buttons.
I did a download mode restart and connected to my Linux box. Then detect OK, then flash the phone.
Code:
heimdall flash --RECOVERY twrp-3.3.1-0-zeroflte.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
After that I power off with Vol-, Vol+, Home, Power together long time but had no time to restart in TWRP mode.
I wait again to discharge the battery and try again.
See you
MrNice said:
Many, many thanks,
I am not too bad with Linux, user for around 10 years, only newbie with mobile devices and Android.
I had to wait long time for the battery be empty and the phone power off. I can't find other way with buttons.
I did a download mode restart and connected to my Linux box. Then detect OK, then flash the phone.
Code:
heimdall flash --RECOVERY twrp-3.3.1-0-zeroflte.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
After that I power off with Vol-, Vol+, Home, Power together long time but had no time to restart in TWRP mode.
I wait again to discharge the battery and try again.
See you
Click to expand...
Click to collapse
You can force your phone to turn off by pressing Vol- and Power Button together and holding it until it turns off, maybe this helps. Good luck!
Very good, now I am in TWRP and I have a lot of questions.
I did WIPE, Format Data, "yes" and Back.
Should I reboot now? What will be the OS/ROM at self reboot? Should I reboot with Vol up, Home, Power instead?
I connected the phone to my linux computer but no connection.
How (with detail as you did perfectly) to upload the new ROM image to the phone?
As you are happy with Marduk Stock Rom, I'll try it.
Could you provide the link to the thread and the download to this rom?
Thanks a lot again
Edit:
In Marduk Stock Rom, is there any GAFAM app/link/account needed?
Is the version v4.5 (12/10/2019) the last one?
Is it the good link to the thread?
Edit 2:
After disconnect and reconnect, I got the phone in my file manager in Linux (Internal Storage). I can transfer the rom file. What should be the extension of the file? .img or .zip or other? Waiting to your confirmation for the version.
MrNice said:
Very good, now I am in TWRP and I have a lot of questions.
I did WIPE, Format Data, "yes" and Back.
Should I reboot now? What will be the OS/ROM at self reboot? Should I reboot with Vol up, Home, Power instead?
I connected the phone to my linux computer but no connection.
How (with detail as you did perfectly) to upload the new ROM image to the phone?
Asyou are happy with Marduk Stock Rom, I'll try it.
Could you provide the link to the thread and the download to this rom?
Thanks a lot again
Click to expand...
Click to collapse
Advanced Wipe everything (but USB)
If you reboot without going into TWRP you will probably face bootloop. But that's no issue since you can always boot down and up into recovery. In TWRP, you can also go to Menu -> Reboot -> Recovery
If you connect your phone via USB to your PC in TWRP it should be detected, so that is weird. You can try to use different usb cables and USB ports on your PC, you can also try to install Samsung USB Drivers and ADB if nothing helps and try again.
Marduk ROM you can find here:
[ROM][ESE3][MAY PATCH] Galaxy S6 Marduk Stock ROM v4.1 [04/07/2019][G920/5/I/F]
WELCOME TO MY S6 MARDUK STOCK ROM No one is allowed to modify or use anything from ROM without first contacting me. READ INSTALLATION INSTRUCTIONS TO AVOID ANSWERED QUESTIONS INSTALLATION INSTRUCTIONS: - Do full wipe and factory reset -...
forum.xda-developers.com
See his/her instructions for your model:
- Do full wipe and factory reset
- Flash ROM using latest TWRP recovery
- Flash latest Magisk Manager
- Reboot
- First boot will take a while
Click to expand...
Click to collapse
You don't need GApps for this, but you need additional Magisk. magiskmanager.com
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
When you have finished and installed your OS install the magisk manager app as an App.
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
MrNice said:
Very good, now I am in TWRP and I have a lot of questions.
I did WIPE, Format Data, "yes" and Back.
Should I reboot now? What will be the OS/ROM at self reboot? Should I reboot with Vol up, Home, Power instead?
I connected the phone to my linux computer but no connection.
How (with detail as you did perfectly) to upload the new ROM image to the phone?
As you are happy with Marduk Stock Rom, I'll try it.
Could you provide the link to the thread and the download to this rom?
Thanks a lot again
Edit:
In Marduk Stock Rom, is there any GAFAM app/link/account needed?
Is the version v4.5 (12/10/2019) the last one?
Is it the good link to the thread?
Edit 2:
After disconnect and reconnect, I got the phone in my file manager in Linux (Internal Storage). I can transfer the rom file. What should be the extension of the file? .img or .zip or other? Waiting to your confirmation for the version.
Click to expand...
Click to collapse
Extension should be zip. Version 4.5 is the right one. Dont forget to flash Magisk after installing the ROM and wiping Cache/Dalvik right after flashing Magisk. Then reboot into OS and wait
Ahrrr...
After Wipe, Advanced Wipe, select all but not USB Storage, Wipe then reboot, Recovery, when I connect to PC, I get SAMSUNG Android device and Internal Storage. If I open this directory I get error:
Code:
The forlder contents could not be displayed.
Sorry, could not display all the contents of "Internal Storage". The connection is closed
I tried to reboot with 3 buttons, same issue.
In Linux dmesg says:
Code:
[23088.108086] usb 2-4: new high-speed USB device number 13 using ehci-pci
[23088.265639] usb 2-4: New USB device found, idVendor=04e8, idProduct=6860
[23088.265647] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23088.265652] usb 2-4: Product: SAMSUNG_Android
[23088.265656] usb 2-4: Manufacturer: SAMSUNG
[23088.265661] usb 2-4: SerialNumber: 0815f83172eb2d01
[23088.267224] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[23096.897800] pool[17212]: segfault at 54b62d50 ip 00007feb702ed9d6 sp 00007feb65ffab68 error 4 in libc-2.26.so[7feb70252000+1b1000]
[23383.203939] pool[17338]: segfault at 54b62d50 ip 00007f4154ef69d6 sp 00007f4142ffcb68 error 4 in libc-2.26.so[7f4154e5b000+1b1000]
I'll try more
Any idea?
MrNice said:
Ahrrr...
After Wipe, Advanced Wipe, select all but not USB Storage, Wipe then reboot, Recovery, when I connect to PC, I get SAMSUNG Android device and Internal Storage. If I open this directory I get error:
Code:
The forlder contents could not be displayed.
Sorry, could not display all the contents of "Internal Storage". The connection is closed
I tried to reboot with 3 buttons, same issue.
In Linux dmesg says:
Code:
[23088.108086] usb 2-4: new high-speed USB device number 13 using ehci-pci
[23088.265639] usb 2-4: New USB device found, idVendor=04e8, idProduct=6860
[23088.265647] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23088.265652] usb 2-4: Product: SAMSUNG_Android
[23088.265656] usb 2-4: Manufacturer: SAMSUNG
[23088.265661] usb 2-4: SerialNumber: 0815f83172eb2d01
[23088.267224] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[23096.897800] pool[17212]: segfault at 54b62d50 ip 00007feb702ed9d6 sp 00007feb65ffab68 error 4 in libc-2.26.so[7feb70252000+1b1000]
[23383.203939] pool[17338]: segfault at 54b62d50 ip 00007f4154ef69d6 sp 00007f4142ffcb68 error 4 in libc-2.26.so[7f4154e5b000+1b1000]
I'll try more
Any idea?
Click to expand...
Click to collapse
Maybe install Samsung USB drivers
More and more I think the issue is in the phone.
When I wiped with: Wipe, Advanced wipe, select all but USB Storage, this selection included "Internal Storage".
Now in this window, I can "Repair or Change File System" directories. When I select System or Data or Cache or USB Storage, and press "Repair or Change File System" button, I get info on the selected item and I could do more. When I select "Internal Storage" instead, I get error: "Invalid partition selection".
As I can;t find it with the file manager, my question is
This directory has issue, is it a real dir or a soft link to a real dir?
How to restore as previous?
Edit 1:
In phone, Wipe page I can read on top:
Wipes Data, Cache and Dalvik
(not including internal storage)
Click to expand...
Click to collapse
What does mean "not including internal storage"?
Should I not wipe it?
MrNice said:
More and more I think the issue is in the phone.
When I wiped with: Wipe, Advanced wipe, select all but USB Storage, this selection included "Internal Storage".
Now in this window, I can "Repair or Change File System" directories. When I select System or Data or Cache or USB Storage, and press "Repair or Change File System" button, I get info on the selected item and I could do more. When I select "Internal Storage" instead, I get error: "Invalid partition selection".
As I can;t find it with the file manager, my question is
This directory has issue, is it a real dir or a soft link to a real dir?
How to restore as previous?
Edit 1:
In phone, Wipe page I can read on top:What does mean "not including internal storage"?
Should I not wipe it?
Click to expand...
Click to collapse
Did you allow modifications here?
https://www.android-hilfe.de/attachments/default-twrp-welcome-screen-jpg.643125/
You can try to mount partitions in TWRP mount option.
I dont know about the Repair options. I didn't have to do that. Also, I dont think your issue is with corrupted file directories.
I would first try to reboot into DOwnload Mode and try and see if USB works in Download Mode. Maybe ADB sideload is possible in Download mode? I don't know about this, though.
If I were you, I would try to connect it to the PC, install Samsung USB and ADB drivers. If it still doesnt work, connect to a different PC, maybe your Windows 10 OS. If that doesn't work, Flash TWRP again and try again.
Wipe/Cache Dalvik does not include internal storage. That is just to make clear that you can wipe it without losing your os or phone data. You should still wipe it, and it will not block wipe of internal storage.
Following this howto I succeeded to transfer and install the new ROM.
I didn't reboot so far as I have to install Magisk.
I downloaded Magisk-v21-4.zip but I don't know how to transfer and install it as I still can't access to "Internal Storage"
I am in the good way, any help?
Nice. So you used ADB sideload to transfer your ROM onto your device? Do the same with the Magisk.zip and flash it just like you have flashed the ROM. Then wipe Cache/Dalvik and reboot into OS.
I did the same process with Magisk, OK then wipe and reboot without TWRP install.
I had to wait at least 5mn then got the new screen.
It seems to work fine and I started to follow setting.... but I got a Google account to create and other thing like that I don't like at all...
I see this ROM is not what I want but I will try a bit
Thank a lot for your help
See you
MrNice said:
I did the same process with Magisk, OK then wipe and reboot without TWRP install.
I had to wait at least 5mn then got the new screen.
It seems to work fine and I started to follow setting.... but I got a Google account to create and other thing like that I don't like at all...
I see this ROM is not what I want but I will try a bit
Thank a lot for your help
See you
Click to expand...
Click to collapse
Hey, yes this ROM is not de-googled. Sorry for that. Go ahead and try other ROMs. Good job installing the Marduk ROM though and have fun
I spend some time to test some features.
So far I found that the fingerprint is not working.
I removed the Google icon but can't remove the apps in Settings > Apps. Is it possible?
How I could install alternative apps store like Apkpure, Aptoide? There are a lot of them but I don't know if I can trust them.
Do you know trusted app shop, good one?
Later if needed, I'll change the ROM. Just to be sure, should I use the same process as previously: Boot to TWRP > ADB sideload > Install the ROM > Install again Magisk.zip (?) > Wipe Cache/Dalvik and reboot into OS.
Question about Magisk.
If fact I don't understand the usage. I have read it's usefull to root devices. My device is rooted, so why I need it? What is the difference between Magisk.zip and Magisk Manager that I have in the apps?
When I start Magisk Manager, at the top page, there are 2 links "Install" to update Magisk and Manager, both look up-to-date. Strange, as the apps are up-to-date why I see these links? Have you the same?
Thank you for your patience.
Edit:
Just to say I don't have any browser where I could display and download apps. Maybe I should start first to install one. BTW what do you advise as browser outside GAFAM?
MrNice said:
I spend some time to test some features.
So far I found that the fingerprint is not working.
I removed the Google icon but can't remove the apps in Settings > Apps. Is it possible?
How I could install alternative apps store like Apkpure, Aptoide? There are a lot of them but I don't know if I can trust them.
Do you know trusted app shop, good one?
Later if needed, I'll change the ROM. Just to be sure, should I use the same process as previously: Boot to TWRP > ADB sideload > Install the ROM > Install again Magisk.zip (?) > Wipe Cache/Dalvik and reboot into OS.
Question about Magisk.
If fact I don't understand the usage. I have read it's usefull to root devices. My device is rooted, so why I need it? What is the difference between Magisk.zip and Magisk Manager that I have in the apps?
When I start Magisk Manager, at the top page, there are 2 links "Install" to update Magisk and Manager, both look up-to-date. Strange, as the apps are up-to-date why I see these links? Have you the same?
Thank you for your patience.
Edit:
Just to say I don't have any browser where I could display and download apps. Maybe I should start first to install one. BTW what do you advise as browser outside GAFAM?
Click to expand...
Click to collapse
You can manually degoogle your phone I am sure, but I would advise you to just install a (stable) ROM that is already de-googled.
You can try lineageOS 17.1 if you want (best version I have found was this: https://lineageos.wickenberg.nu/zerofltexx), or look for older official lineageOS builds in this forum, or just any other ROMs.
My fingerprint sensor works, so I dont know about yours. But it won't work without Google apps, I think. At least not on this ROM I guess.
Yes, if you want to change your ROM later, that is what you would do. IF you want Google Apps and it is not included in the chosen ROM, you would have to install GApps additionally. But since you dont want google, you only need to Root and flash Magisk.
Most people use FDroid for a free App Store I think.
About your Question regarding Magisk:
Magisk.zip is the thing you root your phone with. Usually you have to root your phone again every time you install a new ROM.
Magisk Manager is an App that helps you manage your root permissions, so you can grant root access to apps or deny them. It is also there to hide your root from the google system and from apps that require un-rooted devices. I guess you can't run them without Google safety net etc anyways. Furthermore, there is a repository in the magisk manager app from which you can download various tweaks and scripts etc for your phone and flash it directly onto it, without needing to boot into recovery first.
Yes, I see the same installation buttons even though it is up to date. Maybe it is there to give you the option to re-install things to fix issues.
I would advise using Firefox as your browser.
Thank you again waffelschnitten I learn a lot with you.
So far I installed
F-Droid, APKPure
Firefox, Opera, Brave
Signal but I can't start it because I need to update Google Play Services. I had reading about it and understand it is very difficult to avoid as it is a layer between hardware and software (?).
As you know I don't like GAFAM stuff but I'll be pragmatic and use it unless you know another way.
The issue now is when I start Signal, it ask to update Google PS and I am back to the previous window when I click update button. I checked that it is installed version 11.9.75 and the 2 buttons Disable and Force Stop are grey out.
Any idea how to get ride of this issue?
BTW what Instant Messaging app do you advice/use?