Database Users

[Q] Nexus 7 Frozen in Bootloader Mode -- Help? :(

Was trying to use a one-click root/unlock program for the Nexus 7. Apparently all the drivers did not install correctly. My tablet rebooted into bootloader mode, but is not responding to any volume button or power button pushes, or any combinations of button presses that I could think of.
I'm stuck at the "Start" bootloader screen. The text in the bottom left says the following:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - [...]
SIGNING - not defined yet
LOCK STATE - LOCKED
Click to expand...
Click to collapse
ADB is no longer detecting the tablet as being detected, and no fastboot commands did anything at all.
I have no idea how to do a hard reset on this tablet, and can't find anything about it. Somebody? Anybody? Help?
edit: Power + VolDown seemed to work, but I had to hold it for quite awhile... much longer than I ever expected. Phew.

Did you get it to reboot normally? Go do a search for the Nus 7 image files. It will be a life saver.
Sent from my Nexus 7 using Tapatalk 2

sc4fpse said:
Was trying to use a one-click root/unlock program for the Nexus 7. Apparently all the drivers did not install correctly. My tablet rebooted into bootloader mode, but is not responding to any volume button or power button pushes, or any combinations of button presses that I could think of.
I'm stuck at the "Start" bootloader screen. The text in the bottom left says the following:
ADB is no longer detecting the tablet as being detected, and no fastboot commands did anything at all.
I have no idea how to do a hard reset on this tablet, and can't find anything about it. Somebody? Anybody? Help?
edit: Power + VolDown seemed to work, but I had to hold it for quite awhile... much longer than I ever expected. Phew.
Click to expand...
Click to collapse
As long as you have boot loader mode your in good shape. Download the system images from https://developers.google.com/android/nexus/images#nakasijrn84d and flash the images via terminal or cmd prompt
Sent from my Galaxy Nexus using xda premium

I have got the exact same problem. I have tried to flash the stock images to the device but as the bootloader is locked it won't work. Does anyone have any other solutions?
Edit: How long roughly should you have to hold down power and VolDown to hard reset the device?

conor253 said:
Edit: How long roughly should you have to hold down power and VolDown to hard reset the device?
Click to expand...
Click to collapse
Until it turns off.
You can also pull the back off with a fingernail or something and pull the battery connector, it isn't too hard.

Google brought up this topic. I received a used Nexus 7 bought from Amazon Warehouse Deals today. It seems that whoever had it before me botched something, as I cannot get past the initial boot. I was able to get to the bootloader mode, and the info near the bottom of the screen is identical to the original poster. I've never learned how to root or unlock a device before, but before I even try to learn that, I would highly appreciate if someone here can let me know if such a fix is even possible since the lock state is marked as "locked". If the bootloader is not unlocked, how will I reinstall the original firmware correctly?
Thanks so much to anyone that can help me. The physical device seems great - no creaks or screen lift, and very little backlight bleed. It'd be a shame to have to return this if I can just figure out how to undo whatever the previous owner messed up.

You can easily unlock it but before you do that, can you get into recovery? Make sure your device is connected to a powered on PC before going into recovery. Once in recovery, you can attempt to restore to factory.

I plugged the tablet into my MacBook before entering the bootloader screen. When I select "Recovery" from the options available to me, it just brings up the white Google logo and then the screen cuts to black.
Glad to know I'll be able to unlock the device... I was just worried that the fact that it is locked in its current state might make such a task difficult. Guess I'll start looking into how to go about unlocking the device - thanks for your help!

Well, problem I'm running into is that I can't put the tablet into the correct mode to be recognized by a program like mskip's Nexus 7 toolkit. The only part of the tablet I can access in the fastboot or bootloader menu (not sure of the correct term...), so when I attempted to connect the device up to my computer to use the program, it just got hung up on attempting to find my device. All the instructions talk about putting the tablet into USB mode and such, but I can't actually get into the OS to change any settings.

I only know how to do it on a PC. Maybe someone with a mac can chime in.

I do have access to a PC; could you explain what is needed? Thanks!

Go here, download and install the android sdk. Once complete, the android sdk manger will open. From the sdk manger, also install the android platform tools and google USB driver. Other options are not necessary.
http://developer.android.com/sdk/index.html
Then come back here for additional instructions. I'll be here for the next hour.

Done and done. Thanks very much for your assistance! What's next?

Now, go to the installation directory of the android sdk and you should see several files and folders. Of the folders, there should one labeled "platform tools" and another labeled "extras".
Go in to the "extras" folder then "google" folder. Within the google folder, there is a folder labeled "usb-driver". Just make sure the usb driver files and folders are in there.
Now, put your device in bootloader mode and connect it to the PC. Your PC will start installing the drivers. If it succeeds then double check it in device manager. If it does not, you need to manually install the drivers from device manager and point it to the "extras" folder as the location of the driver.
When the drivers are properly installed, in the device manager, it should say "android bootloader interface" under "android device" or something similar to that. If it doesn't, review the previous steps as you can’t go any further if the PC does not recognize the device.

Okay that is done - I see "Android Device" listed under Device Manager, as well as an entry for Google Nexus 7 Bootloader Interface... next?

Presuming the drivers are properly installed, go back to the android sdk installation folder and go in to the "platform-tools" folder. In that folder you should see several folders and files including “adb.exe” and “fastboot.exe”. Once in that folder, press the "shift" key AND the right mouse button to bring up the context menu. In the context menu selection, click "open command window here" and a command window will open up.
With your device still connected to the PC and the device in bootloader mode, in the command window, type “fastboot devices” without the quotes. If the drivers are properly installed, it will display your device’s serial number in the command window. If it does not, you have to review the above steps and correct the issue before proceeding forth.

The serial number is displaying; progress! Now?

Very good!!!
Once it displays your device’s serial number, you are all set to start flashing the factory image. Leave the device connected to you PC and leave the command window open. Go here and download the factory image:
https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Once downloaded, extract it using winrar or whatever archive decompressor you are currently using. When extracted, you should have the following files:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jro03d.zip
Copy the “bootloader-grouper-3.34.img” and “image-nakasi-jro03d.zip” files into the “platform-tools” folder.

Or, just read this: http://forum.xda-developers.com/showthread.php?t=1907796

Ok, did that. Then?

[Q] Big troubles: only got fastboot and apx, without cuid.

Hi everyone!
I am workiing on my problem since soo many days, now I am asking for help.
Here is all infos I can provide to you:
1) In january, I played with ROMs and CW, but I don't remember the names or versions I played with. For all those months since january, my A500 worked perfectly. August 20th, in the morning, I pressed POWER to play with it, and nothing happened: only the Acer logo.
- I can't open in recovery, when I press Power + VolumeDown, I have this:
Erasing cache before sd update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
Click to expand...
Click to collapse
- USB from my PC can't communicate with the tablet at this point, so I can't use any ADB commands.
- I can open the tablet in fastboot ! I tried to flash with the command: fastboot flash recovery recovery.img, but the tablet respond:
Fastboot: Not support the command in Lock Mode
Failed to process command download: 004d7000 error(0x2)
Click to expand...
Click to collapse
Even if I launch, in this right order:
fastboot oem unlock
fastboot flash recovery recovery.img
[got the same error msg from the tablet]
- I can open the tablet in APX mode ! But I don't have the CUID of the device........... I tried to find it from USBdview, and I even tried with Linux.
I tried all I could find on Internet. Maybe someone here can help me ? i'm sad that there is nothing to "plug and reset"
Thank you!

MillerXL said:
- I can open the tablet in APX mode ! But I don't have the CUID of the device........... I tried to find it from USBdview, and I even tried with Linux.
I tried all I could find on Internet. Maybe someone here can help me ? i'm sad that there is nothing to "plug and reset"
Thank you!
Click to expand...
Click to collapse
If you were playing with roms and CWM earlier, then there is a good chance your UID number is in one of the Clockworkmod back-up files. Check your external SD card (hope you didn't do something foolish like format it).
You get the "erasing cache etc, because the recovery is borked, and it's trying to run some update file that isn't/is there because it can't boot the OS. Also, bootloader/recovery versions may be mismatched.
With ICS+ you have to have the unlocked bootloader to use fastboot commands. Can't do it on a stock bootloader.
If you do not have a UID, you have to use Linux or an Ubuntu install on your PC. There's a couple threads on how to do this, and what scripts to run. @dibb_nz knows a little more about using linux to get the UID.

MillerXL said:
Hi everyone!
I am workiing on my problem since soo many days, now I am asking for help.
Here is all infos I can provide to you:
1) In january, I played with ROMs and CW, but I don't remember the names or versions I played with. For all those months since january, my A500 worked perfectly. August 20th, in the morning, I pressed POWER to play with it, and nothing happened: only the Acer logo.
- I can't open in recovery, when I press Power + VolumeDown, I have this:
- USB from my PC can't communicate with the tablet at this point, so I can't use any ADB commands.
- I can open the tablet in fastboot ! I tried to flash with the command: fastboot flash recovery recovery.img, but the tablet respond:
Even if I launch, in this right order:
fastboot oem unlock
fastboot flash recovery recovery.img
[got the same error msg from the tablet]
- I can open the tablet in APX mode ! But I don't have the CUID of the device........... I tried to find it from USBdview, and I even tried with Linux.
I tried all I could find on Internet. Maybe someone here can help me ? i'm sad that there is nothing to "plug and reset"
Thank you!
Click to expand...
Click to collapse
Your bootloader is not unlocked which is why u have the fastboot error.
As @Moscow Desire said, if u do not have a nandroid backup stashed somewhere,u need linux to get yr cpuid use this guide here http://forum.xda-developers.com/showthread.php?p=28294316
Sent from my GT-I9300 using Tapatalk 4

I followed all the stepts provided to get the uid with ubuntu. But I got this message from the terminal:
[email protected]:~$ cd Desktop
[email protected]:~/Desktop$ sudo su
[email protected]:/home/ubuntu/Desktop# gcc apx.c -o apx -lusb-1.0
apx.c: In function ‘main’:
apx.c:22:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘uint64_t’ [-Wformat]
[email protected]:/home/ubuntu/Desktop# ./apx
Error: Failed to open device!
Click to expand...
Click to collapse
I left a message in the topic, now I wish for a path to solve the error.
Thanks for your help !

There's quite a bit of info all thru that thread, you may find an answer in there somewhere. I can't help with linux side of things sorry. .if u are u runnin 32bit rather than 64bit there is a slight alteration to the commands, thats about all I can offer at this point
Sent from my GT-I9300 using Tapatalk 4
---------- Post added at 08:02 PM ---------- Previous post was at 07:55 PM ----------
MillerXL said:
I followed all the stepts provided to get the uid with ubuntu. But I got this message from the terminal:
I left a message in the topic, now I wish for a path to solve the error.
Thanks for your help !
Click to expand...
Click to collapse
dibb_nz said:
There's quite a bit of info all thru that thread, you may find an answer in there somewhere. I can't help with linux side of things sorry. .if u are u runnin 32bit rather than 64bit there is a slight alteration to the commands, thats about all I can offer at this point
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Oh, one other thing...power off yr tab and enter apx mode via the buttons...use paper clip to push in the reset button, you should feel a click as u push it...hold it in and then press the power button, wait for the power light to come on and then release the power button. After another second release the reset button. .it can be finicky to get right..if I remember correctly yr tab should vibrate too
Sent from my GT-I9300 using Tapatalk 4

[ROOT][LOLLIPOP] Root Mi2 with Lollipop 5.0 !!

Root Mi2 with Lollipop 5.0 !!
In Xiaomi 2, you need to carry out special procedures to root with the Android Lollilpop (5.0) version.
Credits: http://geek.miui.com/content-14-964-1.html#top
***This root kit is not made by me. I just translated it.***
1. Download the Root Mi2 Lollipop.zip (9.17 MB) in the attachments of this thread.
2. Unzip it in a location you like.
3. Open the "Command Prompt.bat" in the folder.
4. Enter fastboot mode in your Mi2 by shutting down and then long-press VOLUME - AND POWER BUTTON.
5. Connect it to your PC with USB CABLE.
6. In "Command_Prompt.bat" in Root Mi2 Lollipop, enter followings:
Code:
fastboot flash boot bootinsecure.img
fastboot reboot
7. It will then reboot. After boot, Open "Command Prompt.bat" and enter followings:
Code:
adb kill-server
adb root
adb remount
adb push busybox /data/local/busybox
adb shell
su
cd /data/local
chmod 755 busybox
./busybox
mount -o remount,rw /system
mkdir /system/xbin
cp /data/local/busybox /system/xbin
cp /data/local/busybox /system/bin
cd /system/xbin
busybox --install .
sync
reboot
8. This will install the busybox and reboot. After it boots, copy the "BETA-SuperSU-v2.19.zip" into the root directory(/sdcard0). Rename it "update.zip"
9. Shut the phone down. Long-press VOLUME+ AND POWER to open recovery. In recovery, choose the "update.zip" to flash.
10. Reboot and you are done!!
You now has root access on L on your Mi2!!
[EDIT] Thanks to zipalign, pointing out the second edition of the tool kit.
As the attachment is over sized, please use the external link below, thanks
Link: http://www.mediafire.com/download/h7i4hhh247ieql1/Root+Mi2+Lollipop-v2.rar

Have tried but it does not work for me and it does not install supersu.
Edit : ok just format the system and do a clear install and it works great !

Spiro67 said:
Have tried but it does not work for me and it does not install supersu.
Edit : ok just format the system and do a clear install and it works great !
Click to expand...
Click to collapse
Congrats! You can hit thanks!

Having problems with this approach on latest update from Ivan 11.28
Root is working but WiFi stops working at all. Cannot activate it.
Looks like after installing busybox wifi is not operational anymore.
Flashing ROM again helps wifi but removes root. So it is now either root or wifi.
Any other ways to get superuser app working?

demon_xxi said:
Having problems with this approach on latest update from Ivan 11.28
Root is working but WiFi stops working at all. Cannot activate it.
Looks like after installing busybox wifi is not operational anymore.
Flashing ROM again helps wifi but removes root. So it is now either root or wifi.
Any other ways to get superuser app working?
Click to expand...
Click to collapse
same here.
hard choice, root VS wifi

zipalign said:
same here.
hard choice, root VS wifi
Click to expand...
Click to collapse
Which model?? Mi2S or C??
Rooting works as expected on my Mi 2S but droidVpn malfunctions only. WiFi is ok.

henry0504 said:
Which model?? Mi2S or C??
Rooting works as expected on my Mi 2S but droidVpn malfunctions only. WiFi is ok.
Click to expand...
Click to collapse
Mi2S.
solved using the updated tool.
works like a charm now

In Windows ...
...
3. Open the "Command Prompt.bat" in the folder.
...
doesn't work.
I followed another's member suggestion from another thread... Instead of using "Command Prompt.bat", search in C: for "cmd.exe". It's in C:\Windows\System32 . Copy this in the unziped folder "Root Mi2 Lollipop-v2" where is the "Command Prompt.bat" . Right click and choose "Run as administrator".
Follow the rest steps as described...
All good! Root access GRANTED!!!

neto65 said:
In Windows ...
...
3. Open the "Command Prompt.bat" in the folder.
...
doesn't work.
I followed another's member suggestion from another thread... Instead of using "Command Prompt.bat", search in C: for "cmd.exe". It's in C:\Windows\System32 . Copy this in the unziped folder "Root Mi2 Lollipop-v2" where is the "Command Prompt.bat" . Right click and choose "Run as administrator".
Follow the rest steps as described...
All good! Root access GRANTED!!!
Click to expand...
Click to collapse
Flash from recovery latest super su

Problem rooting with Lollipop with Build LRX22G for MI2
henry0504,
Following your working procedure, I am facing difficulty in rooting my MI2 machine and it is detailed in below.
Before the rooting, I have updated the PC MI2 device USB driver (thru MI Suitre) and up-to-date ADB software. on the PC end.
After above, I have folloewd the rooting instruction provided in thread No. 1 to connect the phone in fastboot mode with PC thru an USB cable . Starting up ADB on PC and executed "fastboot flash boot bootinsecure.img" command with no problem. After issuing "ADB REBOOT" (second step), I am able to see ADB got a positive response from phone. The phone went into the rebooting mode. I have noticed a XIAOMI logo was displayed right in the middle of the phone screen but stayed there forever (more than 20 mins) without any other display. I guess, the phone has entered into a loop state. No choice but have to stopped the rooting process and recovered phone OS by booting system two.
What could be wrong or missing in above?
Below are info you may need to help identify the failed root procedure:
The download package for this update (per instruction)
- Version----------http://www.mediafire.com/download/h7i4hhh247ieql1/Root+Mi2+Lollipop-v2.rar
- Size----------14.7mb (15,445,546 bytes)
MI Suite
- Version----------2.2.0.7032
ADB
- Version----------1.0.31
Phone info
- Model Number----------MI2
- Android Version----------5.0.2LRX22G
- MIUI Version----------MIUI 5.7.10 Beta
- CPU----------Quad-core1.5GHz
- Baseband Version----------CEFWMAZM-2.0.128017
- RAM----------2.0GB
- Internal Memory----------3.60GB available, 16GB total
- Kernal Version----------3.4.0-perf-g9b728b6-00618-g346799f
- Build Number----------LRX22G
Let me know if you need additional info for the problem identification.
Thanks and Regards,
JayCee

Crap, after sending bootinsecure.img, it stucked at mi.com logo.

nyunyu said:
Crap, after sending bootinsecure.img, it stucked at mi.com logo.
Click to expand...
Click to collapse
Relax, I have had met the same issue before but have had the situation fixed already.
In order for us to help, please provide us screen shot of the "about phone" of your phone in trouble.
Or just reply with "model number", "android version" and "MIUI version".
-- JayCee

juliantchan said:
Relax, I have had met the same issue before but have had the situation fixed already.
In order for us to help, please provide us screen shot of the "about phone" of your phone in trouble.
Or just reply with "model number", "android version" and "MIUI version".
-- JayCee
Click to expand...
Click to collapse
My phone is Mi2S and it's currently stucked at mi.com logo. That's the thing, I can't gives you any of what you asked because it does not boot. Last Miui used version was v6 lollipop.

nyunyu said:
My phone is Mi2S and it's currently stucked at mi.com logo. That's the thing, I can't gives you any of what you asked because it does not boot. Last Miui used version was v6 lollipop.
Click to expand...
Click to collapse
OK. Got you.
I have an Xiaomi MI2. Strongly believe MI2/MI2S /MI2A operates the same.
If this is the first time you flash the phone, I am pretty sure you can recover the phone.
You may want to try below process to recover the phone just before last flash:
1. Power off phone (or take out the battery)
2. First press Vol Up (+) Button and then press Power Button simultaneously and firmly
3. When phone displays the Xiaomi Logo in the middle of the screen, you may now release the buttons
4. Phone is loading (takes a bit longer), wait until the Language Selection page comes up
**use Vol +/- (up/down) to navigate and use power button to select
5. Navigate to English (or Chinese) and select (press Power Button)
6. Navigate to Reboot and select
7. Navigate to "Boot To System Two" and select
8. It will take quite a bit of time for phone to fully boot (be prepared, it may take more than 30 minutes, don't panic)
9. After the reboot, believe System One and Two of phone are the same (identical)
10. You should have the phone recovered now
Wish you good luck...
Don't forget to provide the requested info if you want to root your phone.
--JayCee

juliantchan said:
OK. Got you.
I have an Xiaomi MI2. Strongly believe MI2/MI2S /MI2A operates the same.
If this is the first time you flash the phone, I am pretty sure you can recover the phone.
You may want to try below process to recover the phone just before last flash:
1. Power off phone (or take out the battery)
2. First press Vol Up (+) Button and then press Power Button simultaneously and firmly
3. When phone displays the Xiaomi Logo in the middle of the screen, you may now release the buttons
4. Phone is loading (takes a bit longer), wait until the Language Selection page comes up
**use Vol +/- (up/down) to navigate and use power button to select
5. Navigate to English (or Chinese) and select (press Power Button)
6. Navigate to Reboot and select
7. Navigate to "Boot To System Two" and select
8. It will take quite a bit of time for phone to fully boot (be prepared, it may take more than 30 minutes, don't panic)
9. After the reboot, believe System One and Two of phone are the same (identical)
10. You should have the phone recovered now
Wish you good luck...
Don't forget to provide the requested info if you want to root your phone.
--JayCee
Click to expand...
Click to collapse
Nope, no luck. Tried to boot to both system 1 and 2 but still same issue.
Finally able to flash cwm and reflash the rom again. The latest rom downloaded by MIUI still in the downloaded_rom folder.
So, I guess rooting a Mi2S v7 not yet available.

nyunyu said:
Nope, no luck. Tried to boot to both system 1 and 2 but still same issue.
Finally able to flash cwm and reflash the rom again. The latest rom downloaded by MIUI still in the downloaded_rom folder.
So, I guess rooting a Mi2S v7 not yet available.
Click to expand...
Click to collapse
Sorry to hear you were not able to recover the Android.
Xiaomi 2/2S Android has Global, Special and China version editions.
Only the China version has a Developer version which has the rooted function incorporated already.
Mi 2/2S MIUI 7 was only released in late August for all editions.
The latest China/Developer version is v5.9.2 （MIUI7） and my phone has flashed to this MIUI and ROM.
I have been using the rooted function for programs like Super Backup, ES File Explorer, etc, happily.
IMHO, the newest MIUI and ROM is quite stable.
If you are interested, you may get more info from " http://en.miui.com/download-2.html#2".
--JayCee

juliantchan said:
Sorry to hear you were not able to recover the Android.
Xiaomi 2/2S Android has Global, Special and China version editions.
Only the China version has a Developer version which has the rooted function incorporated already.
Mi 2/2S MIUI 7 was only released in late August for all editions.
The latest China/Developer version is v5.9.2 （MIUI7） and my phone has flashed to this MIUI and ROM.
I have been using the rooted function for programs like Super Backup, ES File Explorer, etc, happily.
IMHO, the newest MIUI and ROM is quite stable.
If you are interested, you may get more info from " http://en.miui.com/download-2.html#2".
--JayCee
Click to expand...
Click to collapse
Sorry, blunder on my part. My phone was on V6.

nyunyu said:
Sorry, blunder on my part. My phone was on V6.
Click to expand...
Click to collapse
Whether your phone is on Miui V6 or V7, Stable or Development Android , Global/Special/China Edition,
you should be able to get the required info (thru search) to root your Mi2S with the following page :
http://en.miui.com/type-26-411.html
--JayCee

Root Lenovo Yoga Tab 3 pro

Hi all,
Is there already a way to root the brand new Lenovo Yoga Tab 3 pro?
I want to buy it, but I can't imagine having an unrooted device...
Envoyé de mon LG-H815 en utilisant Tapatalk

Up?

misteurz said:
Up?
Click to expand...
Click to collapse
i have no idea not having access to such a device, but considering the similar hardware with the YT2 model (well better a little but not by that much) it should work with the exact same method uset for YT2. so yes 99% that it's root-able (maybe even unlock-able, someone on your thread asked me, yet he did not sent nothing no files when asked so i don't know much about the internals of YT3)

Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?

misteurz said:
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
Click to expand...
Click to collapse
there are other ways of knowing whether that or maybe even other new commands work, i would need from someone to send me a dump of his fastboot partition so i can check inside (my bet is that what works on YT2 willdo on YT3 too... and i am pretty sure it will work up to YT100 knowing how Lenovo works )

I don't have the tablet yet, so I can't have the files you need. Who has the yoga tab pro 3?

I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet

Shug69 said:
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Click to expand...
Click to collapse
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab

ionioni said:
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
Click to expand...
Click to collapse
Hallo,
Thank you for your work. I have a little bit afraid of this method .
Too bad that there are so few users here . But the Tab is still so new.
Perhaps an even experiencer user dares. Sorry !!!
At Weekend i will take your method and send you the file.

Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.

Shug69 said:
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Click to expand...
Click to collapse
we tried. it was rejected by the bios right from start and never even got the chance to load (that message means just that).
somehow, someway we must get a fastboot image so we can see what can we use (grab from the tab or from stock rom).
i've seen your stock rom avail yet i don't know if they are legit (they seem). also is a payed one.
one more try:
go in fastboot (droidboot) mode and try and see what these commands will output (to see if at least one is still valid):
fastboot flash /tmp/some_small_file some_small_file (use a real file ofcourse, to see if we can still write to the device)
fastboot oem unzip
fastboot oem fastboot2adb
fastboot oem factory2tmp
(they won't do nothing in this config, yet we'll be able to see if meaybe one is still working, ie it doesnt say 'unknown command')

Flash file gives cannot load,; the others give unknown command.

Shug69 said:
Flash file gives cannot load,; the others give unknown command.
Click to expand...
Click to collapse
try again the fastboot flash (i edited the syntax in the prev post)
however, i think that a droidboot.img will make things a lot more easier
so whoever grabs a stock rom...

So, @Shug69, did you try the edited commands?
Envoyé de mon LG-H815 en utilisant Tapatalk

Been travelling. Can try tomorrow but I agree we need to find a ROM. The site ionioni linked to may be legit but 25 bucks to find out seems a bit steep.
ok. back at pc - sure i'd bricked it there - ran 'fastboot oem unlock' and it unlocked the bootloader. woudnt boot normal though afterwards and it took several reboots after ' fastboot oem lock' to get past the Lenovo logo. Device is wiped of course

My experience has been a little different so far. Just picked up the tablet today.
I toggled Allow OEM unlock and enabled debugging in Developer Options. I installed the Lenovo Suite software (which was really just a driver pack) then ran adb reboot bootloader to reboot. It got me to a Lenovo splash.
fastboot oem unlock didn't work for me. It gave me an error message:
Code:
fastboot oem unlock
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.005s
Running fastboot oem unlock-go worked immediately and the tablet rebooted to the typical Android factory wipe screen. Could be coincidental, but I got an OTA notice after I did the whole first-time Android setup. I denied the update, but copied down the update name: YT3-X50F_S000015_150917_ROW_TO_YT3-X50f_S000016_151002_ROW

Hey everyone, kingroot now works to root the yoga 3 8".

Not on the pro unfortunately.

?
Envoyé de mon LG-H815 en utilisant Tapatalk

Thank you
ElrosMinyatur said:
Hey everyone, kingroot now works to root the yoga 3 8".
Click to expand...
Click to collapse
Great news. I have confirmed that it works using my non-Pro Yoga Tab 3 8". Do I need to keep the Kingroot app installed after I have unroot device? The only issue I have is updating the SU binary in SuperSU. More to come after I debloat my device.
Thank you once again.
Spunky168
"The Original Taepo Dong"

Newbie corner: How to unlock, install some OS on Galaxy S6

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?