Related
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Different reactions
Hi,
My device could still boot on fastboot mode, and flashes successfully through it on MiFlash Beta. However, the device remains stuck on Mi logo. I've already tested flashing on EDL mode apparently successfully, with the same results. I've flashed TWRP, but the device don't enter recovery mode. What can I do? Any suggestion will be welcome.
benzersizadam said:
Many thanks for this thread, I stuck on my mi max with no reaction at anything, I read more than 100 threads, I tried testpoint, DFC (deep flash cable), click inside usb terminal to pc, windows 8, 7 10, 32 bits, 64 bits, programms like qfil (qpst), flasher tools for other phones and nothing, before with other apps at first second gives me error "can not read from port COM...", and now at least advance to 5 seconds with same error, I need to know it is neccesary too disconnect, remove two plastic cables down where places the battery
Click to expand...
Click to collapse
Working also with Hydrogen. Thanks.
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
coffee-turtle said:
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
Click to expand...
Click to collapse
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
SubwayChamp said:
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
Click to expand...
Click to collapse
Hi @SubwayChamp Everything I did was in the post and video from above in the first post by benz....
His instructions were perfect along with the youtube video. It's tricky, true, but with patience you can go through the steps and get your device running again. I was so glad that @Qulox gave me this link to this thread.
As you go through the steps, if you get stuck, we can try to give you advice.
This works for Hydrogen as well.
Many thanks
I have two dead mi max. One 128gb helium and one 32gb hydrogen.
128gb helium is completely lifeless. No charging led, no vibrations, no fastboot mode. Though i could bring it up to edl mode showing right qualcomm device in device manager. I tried flashing stock rom as mentioned in this guide which rather went successful without giving any error, even while battery connector was removed.
But mobile is still in same lifeless condition. Other than flashing process going through, it didnt make any difference. Dont know whats wrong. Also i didnt have to use two miflash versions as mentioned in steps as flashing process didnt give any error.
32gb hydrogen, boots up in flashboot mode, shows charging led, mi logo even edl model worked without any issue. It even boots up, but gives error of encryption unsuccessful asking me to reset device. I tried factory reseting it. Tried flashing twrp and wiping, formatting data, changing file system to all formats like fat, f2fs, ext1, ext2, ext3, ext4. Tried flashing crdoid and RR based on orea. Nothing working.
With twrp it keeps bootlooping showing mi logo. And with stock rom, recovery shows up encryption error. Followed procedure mentioned in this guide as well.
Is there anything am i missing or can do? Btw, bootloader is locked for both the devices. I could flash twrp referring another guide which suggested to replace stock recovery in rom files/ folder and flashing it like stock rom through miflash tool.
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
cobben said:
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
Click to expand...
Click to collapse
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Hello,
trying with both Helium & Hydrogen. Still on error like say these logs.
log#1
Code:
[0,02 COM7]:[COM7]:start flash.
[0,02 COM7]:received hello packet
[0,02 COM7]:can not found programmer file.
log#2
Code:
[0,00 COM7]:[COM7]:start flash.
[2,03 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[4,56 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,11 COM7]:try to reset status.
[7,13 COM7]:Switch mode back
[7,13 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,14 COM7]:Riferimento a un oggetto non impostato su un'istanza di oggetto.
Hope anyone can help me. What's my wrong following the guide.
Thanks
harpy.eagle said:
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Click to expand...
Click to collapse
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
rizkhan77 said:
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Click to expand...
Click to collapse
This is the video of Test Point https://youtu.be/SqcVY8IWkZI
benzersizadam said:
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Click to expand...
Click to collapse
hi, could someone share with me the miflash beta? I can download the rest but I cannot download the beta one.
thanks
Wanted to say thank you was able to recover my mi max 64gb unit.
Android 9.0 on Your MiPad2!
We all hate that Xiaomi didn't update their MiPad 2 to latest Android. Or at least Marshmallow.. but! Today I found a way to get Android 9.0 to boot on our devices . As You know MiPad 2 uses x86_64 CPU which gives us HUGE possibilities. But it's not perfect. It's pretty buggy and booting most OS's is simply impossible. But today, I found a way to boot most likely any OS, INCLUDING ANDROID X86!
Guide:
1. Prepare: At least 8GB USB drive, USB Hub, Keyboard & Mouse, OTG Type C adapter. And make sure that You have at least 50% battery.
2. Download Rufus 2.18 or latest version.
3. Download Android x86_64 7.1 rc2.iso from android-x86.org UPDATE: Use this link for Pie! BlissOS 11.x Pie
4. Open Rufus and plug in Your USB drive.
5. Inside Rufus choose: Partition type GPT for UEFI.
Make sure that Quick Format is selected.
6. Change FreeDOS to ISO Image and choose Your ISO file.
7. Tap start.
8. Plug Your USB drive and keyboard & mouse into Your USB hub and then plug it into Your MiPad 2 through OTG adapter.
9. Turn off Your MiPad 2.
10. Quickly tap F2 button on Your keyboard multiple times and turn on Your MiPad 2.
11. Tap the F2 until You see bios.
12. Inside bios go to Device Management> Security/boot > Change GMIN to Windows and disable secure boot.
13. Tap F10 to save and then go to main BIOS menu and choose boot device.
14. Choose EFI USB drive.
15. When You see Android x86 GRUB menu tap "e" on Your keyboard and find androidboot.hardware=androidx86_64 edit it to make sure it looks like this androidboot.hardware=androidx86_64 nomodeset and then tap F10 to boot.
16. Wait for Android to boot. It will take around 5-15 minutes depending on Your USB drive speed.
17. Enjoy Your MiPad 2 running Latest Android!
Touch works. Yes! WiFi too.
Bugs:
Sound doesn't work in live mode(maybe after installing the Android it would fix the sound.)
Video playback is broken.
Brightness control is broken.
Probably other stuff too. But maybe installing it or trying Bliss OS or Remix OS would help .
Can confirm that Bliss OS with 4.9 kernel boots and works fine too.
Also tried Remix OS 3.0 and it works fine, as well as Ubuntu 17.10. Touch works in all OS's.
ProtoDeVNan0 said:
Android 7.1.2 on Your MiPad2!
Enjoy Your MiPad 2 running Latest Android!
/QUOTE
@ProtoDeVNan0 Sounds very interesting but I have a few questions:
- what I understand is the MI PAD2 boots from USB and runs in Live mode. So does the USB need to be connected al the time?
- does it affect your current MI PAD2 ROM?
- same procedure every time you need to reboot?
- Can from live mode do an install on your tablet (confirmed to work)?
- how is the performance?
But thanks for sharing, sound prommissing
Click to expand...
Click to collapse
@ProtoDeVNan0 Sounds very interesting but I have a few questions:
- what I understand is the MI PAD2 boots from USB and runs in Live mode. So does the USB need to be connected al the time?
- does it affect your current MI PAD2 ROM?
- same procedure every time you need to reboot?
- Can from live mode do an install on your tablet (confirmed to work)?
- how is the performance?
But thanks for sharing, sound prommissing
Edwin184 said:
@ProtoDeVNan0 Sounds very interesting but I have a few questions:
- what I understand is the MI PAD2 boots from USB and runs in Live mode. So does the USB need to be connected al the time?
- does it affect your current MI PAD2 ROM?
- same procedure every time you need to reboot?
- Can from live mode do an install on your tablet (confirmed to work)?
- how is the performance?
But thanks for sharing, sound prommissing
Click to expand...
Click to collapse
It runs from live mode but can be installed as main OS. But then You will lose Android/MIUI.
If You run any of these OS's in Live mode then Your current rom won't be affected.
Depends on what You have installed. Android x86 aftet reboot will boot back to Android x86. And If You reboot from Live mode, it will boot back into GRUB or if You remove Your USB drive it will boot back to MIUI.
Yes. It can be installed. Haven't tried that yet because I was testing all Linux Distros and Android x86 versions but it should work just fine. Just make sure to edit grub to boot every time with nomodeset.
Performance.. it's a bit slower than MIUI. But then again. I used Live mode + extremely slow usb hub which is really bad and installing anything with it takes hours. Even on a high end desktop. But since the general stuff works quite decently. I'd say that if You installed it on Your tablet, then it would run pretty smoothly. And You would get similar Antutu score to MIUI(+/- 5-7k).
Also I tried a lot of linux distros and all of them had touch working. Native resolution worked too.
I might later try different kernels and install Android x86 on my MiPad 2 as default OS to see how it runs.
Do you try to install bliss os or remix os ?
Sounds Sweeeeet!
I am going to try it.
So I wondering now...
- If I try this with INSTALLING, not LIVE MODE, what happens to Recovery Mode and Fastboot Mode? Will they still exist? So that I can backup and restore with TWRP?
-Did you have any bugs with Remix OS 3.0? It would be cool if I can fully use it.
YeonsK said:
I am going to try it.
So I wondering now...
- If I try this with INSTALLING, not LIVE MODE, what happens to Recovery Mode and Fastboot Mode? Will they still exist? So that I can backup and restore with TWRP?
-Did you have any bugs with Remix OS 3.0? It would be cool if I can fully use it.
Click to expand...
Click to collapse
I have tried installing Android x86 but messed up recovery and fastboot partitions really badly. But! Thanks to DNX Fastboot Mode I was able to
fastboot boot loader.efi
fastboot flash gpt gpt.bin
(And then flash all files inside images folder, including oemvars battery disabled or else Your battery will get stuck at 42%)
And my tablet was good again .
Bugs on all OS's are pretty much identical. Like a week ago Bliss OS released Oreo update but it's alpha and it didn't boot on my MP2. And there are bugs like: no sound, rotation not working, brightness doesn't work, etc.
I think some of these could be fixed but these x86 Android OS's are stuck inside .sfs files and repacking them usually makes the rom not boot anymore.
And if You want to try to install Android x86 then I'd recommend to first install Win10 on Your tablet(so that partitions will be changed from Android ones to Windows ones) and then format "C partition/windows partition" and try to install Ax86 into that partition.
Not sure how installation looks like on RemixOS though. It might be easier or the same.
And if You won't remove/format Fastboot or TWRP partition then it should stay there. But installing Win10 will remove them. So You can try manually installing Ax86 and see how it works. Just don't delete partitions that are called: ANDROID_BOOTLOADER or ANDROID_RECOVERY. These most likely contain Fastboot and TWRP.
And if You delete any of these and Your tablet will be dead, then just remove USB cable from Your tablet, hold vol up, vol down, power until You see DNX Fastboot and follow my guide above. And don't worry. MiPad 2 seems to be unbrickable.
Hey guys!
Maybe I'm the noob but anywhere I tried to find bliss rom or remix os 3.0 for mi pad 2 I had no luck with it. Can anyone help me with a link for these roms and a proper gude how to install them? I'm really interested in remix os 3.0 but curious about bliss os as well, cause I've not heard of it yet.
Thanks in advance.
Have a nice day you all
Hi all, I tried almost all recent distros and it works fine to boot in Live mode. All flavours of Mint, ubuntu. I booted up with "nomodeset" option. I did install and now, when I call grub with "Shift" and edit the installed system with nomodeset option, all I got is black screen. If someone installed any distro on MiPad 2, can someone tell me what should be done to boot into installed system? Thanks so much
is this work on Xiaomi Mi Pad 2 16gb variant?
Can I do this for Mi Pad 2 16 GB variant?
Are there any news? With Bliss Rom you can make daily use?
InfinityCore said:
is this work on Xiaomi Mi Pad 2 16gb variant?
Click to expand...
Click to collapse
It should .
After several week research, my current Mi Pad 2 can install Windows 10 (woah!!).
But for this time I need several tools (like USB C OTG Y cable, also USB Hub) to help me installing another OS like Remix or Ubuntu.
By the way anyone succeed install Remix OS 3.0 in mi pad 2 tablet?
there is any bug?
I tried to install in my Mi Pad 2 16gb Phoenix Os, Android x86 and Bliss Os but none boot in live mode. I wait almost 30 minutes for each.
Anyone success installing Another OS to our Mi Pad 2?
I tried to install Ubuntu, it's installed, but I can't boot into it.
Need Help.....
How about remix os?
InfinityCore said:
Anyone success installing Another OS to our Mi Pad 2?
I tried to install Ubuntu, it's installed, but I can't boot into it.
Need Help.....
Click to expand...
Click to collapse
You can boot to installed system by going to Advanced Option in Grub -> Recovery-> Resume boot
Good News! Today I found out that BlissOS 10.0 Oreo 8.1 works on Mi Pad 2!
Bugs are identical to earlier Android versions. But as You can see, Mi Pad 2 HW is capable of running Oreo
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?
I was looking to install LineageOS 18.1 and was having a hell of a time.
I was following the instructions, and I can get as far as booting into the LineageOS recovery, but then I can't navigate to ADB using the front button on the box. I am also finding it difficult to find a working OTG cable that works and has the ability to provide power. (so I can remove the USB cable from my laptop and plug in a USB keyboard without powering off the android box)
Anyone have any tricks or suggestions on a OTG cable or USB switch they know works on this? Or better yet, how to get the front navigation button working on the Onn Box working ot how I can enter recovery mode if I try fastboot flash (Impossible to enter recovery instead of boot to OS) instead of fastboot boot?
Here are the instructions I was using. Great until you get to the fastboot flash, since once you reboot it goes straight into the OS and will over right the custom recovery. Then when I fastboot boot, it works, but then the navigation button doesn't work to get to the next step. lol.....
Install LineageOS on dopinder | Odd Solutions Wiki
wiki.oddsolutions.us
on a side note, I have a OTG cable that splits and works on my laptop to fastboot boot the recovery. But once I am in the LineageOS recovery and connect a USB keyboard, it doesn't respond either. (So maybe the LineageOS recovery is the problem?)
I've tried both from https://updater.oddsolutions.us/#/devices/dopinder/builds
lineage-18.1-20220324-recovery-dopinder.img
lineage-18.1-20220317-recovery-dopinder.img
I also tried the 19.0 revoceries (stays in Onn fastboot even after successful fastboot boot) I also tried the earliest 18.1 recovery.
Tried:
lineage-19.0-20220228-recovery-dopinder
lineage-19.0-20220114-recovery-dopinder
lineage-18.1-20210804-recovery-dopinder
Releases · ods-releases/dopinder
Contribute to ods-releases/dopinder development by creating an account on GitHub.
github.com
Has anyone had success getting LineageOS 18.1 flashed on the Dopinger devices? If so, which recovery did you use? (maybe an earlier release works?) If so, where can I get it? (the above link only has the last 2 releases)
Right now I am very suspicious that the recoveries are not working properly for this device.
Here's the extra instructions after you adb reboot into the bootloader using the guide:
1) fastboot flash recovery <recovery file name >
2) fastboot boot <recovery filename> **to get into lineageos recovery mode
At this point the recovery is unresponsive to any inputs (i.e onn 4k button pushes or USB keyboards)
3) In lineageOS recovery mode you can use the basic adb command to reboot recovery into sideload mode
adb reboot sideload **Devs apparently specially enabled this as a workaround for the no input in the recovery
From here you can continue to use the official guide to sideload the lineageos. At this point I was basically dirty flashing, which worked. But I'm sure people can format and erase the stock OS via adb commands if they're motivated enough.
Two issues I noticed with Onn 4k is that plex was super stuttery for almost everything I played (never tested plex on stock OS).
I also performed a factory reset, and afterwards WiFi was unable to reconnect. So I gave up for now and went back to my mibox s until I have time to look further.
Thanks again for the information to help me get lineageos on this device!
htc_softbank said:
I was looking to install LineageOS 18.1 and was having a hell of a time.
I was following the instructions, and I can get as far as booting into the LineageOS recovery, but then I can't navigate to ADB using the front button on the box. I am also finding it difficult to find a working OTG cable that works and has the ability to provide power. (so I can remove the USB cable from my laptop and plug in a USB keyboard without powering off the android box)
Anyone have any tricks or suggestions on a OTG cable or USB switch they know works on this? Or better yet, how to get the front navigation button working on the Onn Box working ot how I can enter recovery mode if I try fastboot flash (Impossible to enter recovery instead of boot to OS) instead of fastboot boot?
Here are the instructions I was using. Great until you get to the fastboot flash, since once you reboot it goes straight into the OS and will over right the custom recovery. Then when I fastboot boot, it works, but then the navigation button doesn't work to get to the next step. lol.....
Install LineageOS on dopinder | Odd Solutions Wiki
wiki.oddsolutions.us
Click to expand...
Click to collapse
What I ended up doing was hardwiring an extra USB cable internal, wasn't too hard soldering isn't my strongest skill by any means, but it's held up. I don't know exactly what the connection beside the USB is, but if I'm remembering correctly that's where i ended up wiring to it. Actually just tried to stay as close to the other power input as possible Just because it seemed like it would be best practice.
Also in case anyone needs them. decent internal photos
Best of luck, I've been running it this way for almost 6 months now
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
iamnotsunshine said:
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
Click to expand...
Click to collapse
[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices
Amlogic G12*/SM1 Family Devices - Your warranty is now void. - You have been warned. - Use at your own risk. Introduction: This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices. Downloads: Please follow...
forum.xda-developers.com
iamnotsunshine said:
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
Click to expand...
Click to collapse
note that on dopinder, unofficial LOS19.1 installs & works, but L1 still not working (as of today ... hopefully npjohnson & others can fix it) in the lineage19.1 version linked by BTK19 in previous post. so, if you are set on DRM content, might want to wait. I bought a Dynalink/wade while I wait, and Lineage19.1 unofficial works well on that. just costs 2X $ !
After spending 2 days on the forums and softbricking my device for several times, here's my 2 cents about on how to do the upgrade from Andorid 10 to Android 11 or even to downgrade ... on the HA units from Dasaita.
First of all, a small disclaimer:
This worked for me, it might not work for you.
You might end up in bootloop, blackscreen, softbrick, be aware of this risk
My device is a Dasaita Max11, I wanted to downgrade to A10, in order to get Magisk and Hal9k v5 mod installed.
After purchasing modinstaller 3pro, and trying to install Andorid10 I ended up in a blackscreen. Hopefully @Hal9k_ will be able to fix this in his further releases.
Remember, this was ONLY tested and worked on a MTCE_HA device. A rather new model sold by Dasaita last december. If you have a HTC or other device this has no or litlle importance to you, since the images atached are ONLY for HA devices. Also, if you have an older Dasaita model, it might not work as described bellow:
What you'll need:
- a USB A to USB A cable (as short as possible)
- the purple usb plug cable (labeled carplay/android auto) that comes out of the back of de divice (this is the only one that recognized my device in bootloader mode. Feel free to try the others, in function of what configuration your device might have.
- driver assistant (see google drive link)
- flash tool (see google drive link)
- full system image of Android 11 or 10 regarding what you want.
- a pin or paperclip to push the reset button.
The procedure is rather simple:
1. Download and install the driver assistant (google drive link at the end), run it to install the drivers on your windows machine
2. Unpack rkdevtool and run the exe (google drive link at the end). At this point the program will display a huge message in the bottom part saying: "no devices found". That's good.
3. Connect the Usb cable to the HU and to the PC, while the device is turned off (like no power, not in sleep mode)
4. Push the reset button and keep it pushed. While doing this turn on the device. At this point if everything is setup correctly you should hear a notification sound from windows and RKDevTool should say: "Found one bootloader device".
4a) If you only hear the notification and the device is not found in boot loader mode by RKDevTool, check Device Manager and try to reinstall the drivers / install other drivers, try another USB port. (at this point, the usbA to usbA might be to long if the device manager shows: unrecognized device)
4b) If you hear no sound, RKDevTool still shows no devices: Turn off the HU, (really of, no power). After 10-30 seconds turn it on, while it is on, press the reset button and keep it pressed (even after side leds flashing) until the device enters bootloader mode and it is recognized by the RKDevTool.
4c) If none of the above work, switch the usb port on the HU, or try another combination of reset pushing (like trying to enter recovery)
4d) If the PC won't recognize the device in bootloader mode, it might be a situation in which the device is not capable of this, and you might need to take it apart and use the direct SOM flash method ... search the forums.
During step 4 the HU display should remain black, so the only indication of being in bootloader mode and connected to the PC, is the windows notification sound and the messege displayed by RkDevTool.
5)With the device in bootloader mode, connected to the PC, in RKDevTool go to the tab that says: Upgrade firmware. Click on the line(empty rectangle) that says firmware and browse for the desired android img. (10 or 11). See drive link. Attention: the zips from the drive MUST be unpacked and the update.img must be loaded in RkDevTool.
6)After selecting the desired update.img, click on the ERASE FLASH button, wait until the process completes. If everything goes well, the device should reboot in maskrom mode.
7)After the device enters maskrom mode, RkDevTool shoul display the message: "Found one MASKROM device". At this point, just click the UPGRADE button. The new android is flashed on the HU. When the process is finished the HU reboots ITSELF. If that doesn't happen after 1-2max, cut the power and power on.
It should boot in the new android.
Final thoughts after 2 days of thinkering:
This worked for me to downgrade from 11 to 10, and also to upgrade from 10 to 11. Be aware it might NOT work for you!
In theory, if one can get the device in bootloader mode it should work also to upgrade from andoid 9 to 10. This is just a theory and I did not test it.
The advantages of Android 10 over 11 are (for me):
- root access via Magisk (for the time being I could not root 11 with any of the tutorials found online)
- less crap and restrictions imposed by the growing Google censorship..
- the possibility to install the Hal9k v5 mod, one of the greatest and customizable mods ever made for MTCD/MTCE devices.
- using both 11 and 10 I could very certainly tell you, that (from my point of view), 11 has no advantages over 10, nor in stability nor in sharpness.
The images from the google drive are vivid for android 10 and max for android 11. Again, this are FULL images, not just OTA. I put them here after endless hours of searching the net. I respectfully thank to those that took the time to upload them on xda and dasaita forums.
Once you install the base 10 or eleven you can easily switch from vivid to max via update.zip flashed from an usbstick.
Also: there are many tutorials that involve a sdcard, sdcardtool and different combinations of zip images. I tested them ALL using the side sd card slot of the device. NONE OF THEM worked for me. I found the OTG flash method to be the fastest and most reliable, once I figured out how to connect de HU to my pc in bootloader mode.
PX6 MTCE_HA Android 10 full image, Android 11 full image, RkDevTool, Driver Assistant link: https://drive.google.com/drive/folders/1eigYrCKl8Z34KQxBoX3Q91Foy2K15CGm?usp=share_link
Nice! Do you perhaps know where to find the files for other headunits? I have a MTCE_HT and have no idea where to look!