WARNING: You can't downgrade anymore once you flashed U4/S4 March update !
https://samfrew.com/model/SM-A805F/
SM-A8050
SM-A805F
SM-A805N you can't unlock bootloader on this variant! (R1Q_KOR_SINGLE.pit)
You will need:
-Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
-Galaxy A80 Latest USB Driver
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
You want to download latest firmware directly from server? (fast download)
Samfirm 0.4.1 or Frija 1.4.2
https://samfirmtool.com/samfirm-v0-4-1
https://github.com/wssyncmldm/frija/releases
Frija not working ? install both vcredist_x00 for your device !
(Check your windows settings to know which version to install).
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
-https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
-https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-A805F) and your CSC : (mine is LUX).
(All CSC's and models on Samfrew: https://samfrew.com/model/SM-A805F/).
-Download and extract SM-A805XX_1_00000000000000_xxxxxxxxxx_fac.zip
On your device:
If you want to unlock bootloader:
-Go to Settings then to About phone and find your build number.
-Tap on your build number 6 times until you see “You’re now a developer”.
-Go in Developer options > enable OEM unlocking.
-Connect the device to your PC.
-Power off your device with POWER and volume DOWN and directly hold volume UP and DOWN together!
-Device will boot in DOWNLOAD MODE.
-Long press volume UP to unlock the bootloader. This will wipe your data and automatically reboot your device!
If you dont want to unlock bootloader:.
-Download and extract Odin and open it as administrator.
Still in DOWNLOAD MODE:
-Click on BL and select BL_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on AP and select AP_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
-Click on CP and select CP_A805FXXXU4AXXX_CP14483800_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on START and wait for installation, when done you can unplug your device.
ROOTYour KNOX status will be tripped if you follow this tutorial...What's knox ? : https://www.google.com/search?q=samsung+knox+explained
-Download the latest stock firmware for your Samsung Galaxy A80 with Samfirm/Frija app (faster) or Samfrew/Sammobile website (way slower).
https://samfrew.com/model/SM-A805F/
-Extract the SM-A805XX_1_EXAMPLE_0000000000_fac.zip file with 7zip or any other unzipper.
-Copy the (AP_A805XXXXU1XXXX_CL00000000_QB00000000_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5) file and transfer it to your internal storage.
-Download and install Magisk Manager APK https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
-Open Magisk Manager and go to Install > Install > Select and Patch a file.
-Navigate through the storage and select the extracted AP file.
The firmware will be patched and will be found in Internal Storage/Download/magisk_patched.tar.
-Transfer the patched file to your PC.
-Turn OFF your device and boot into DOWNLOAD MODE.
-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.
The tool will flash Magisk V20 on your Samsung Galaxy A80.
To boot in recovery or boot the system with Magisk installed:
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
My storage was reduced from 128gb to 32gb after doing this. Is there a fix?
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
haanz85 said:
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
Click to expand...
Click to collapse
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Nazato said:
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Click to expand...
Click to collapse
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Could you please be more detailed in this steps?? I got this problems too. plz help.
hosheaxu said:
Could you please be more detailed in this steps?? I got this problems too. plz help.
Click to expand...
Click to collapse
read carefully every step bro. after flashing magisk patched then setup phone from beginning without setup google acount just skip, then check again by activating developer menu & usb debugging on. at the end reset from about menu..then phone's should reboot, after that install magisk manager then follow until finished process. & now after reboot u already got rooted beloved phone . congrats
haanz85 said:
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Click to expand...
Click to collapse
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Nazato said:
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Click to expand...
Click to collapse
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
haanz85 said:
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
Click to expand...
Click to collapse
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Nazato said:
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
yeah it's possible for sensitive pricing from first launching. in my country first launching price going around $705 then after few month until approaching new device release info to be released in February. on new years then the price going down until just left $549,50 then i decided to bought it :victory:
maybe many people's thinking like me, wait & see before grab this phone's :laugh:
Nazato said:
I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
tin2404 said:
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
Click to expand...
Click to collapse
but what about this device? are u still make exception from regular ongoing development.. until now there's no famous developer that saw it for builds known roms out there although this doll already succesfully rooted, but none of them build us twrp with fully support & maybe one or two working cust roms
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
BK said:
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
Click to expand...
Click to collapse
Is This only for france devices?
android 10
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
uae.coool said:
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
Click to expand...
Click to collapse
go right ahead I'm rooted on Android 10 right now just follow the instructions again
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
uae.coool said:
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
Click to expand...
Click to collapse
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Nazato said:
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Click to expand...
Click to collapse
ok thanks will try it now
other things is losing the memory showing 32gb after the root and when wipe no root ???
and one more things please how to install TWRP i tried many time but stack in the samaung logo ???
thanks again
Related
READ ME FIRST I am more than willing to help you guys, so if you have questions, please ask me via my facebook page, as I get notifications there instantly. http://facebook.com/vacationlandtech
Also of note, I no longer have a LG G2, and it has been a long time since I made this, if you can be as descriptive as possible when asking questions, that would help a lot. Also, because it has been quite a while since I've been in the G2 community, I'm not up to speed on anything newer than early November, 2014. I don't have experience with ZVE+, CM12+, CloudyG3, etc. so if you have problems with new ROMs and software, get help from the people who make/support those ROMs and software.
Good luck!!
So I've been helping around the forums with people trying to install CyanogenMod on the Sprint LG G2 (LS-980). I have done this successfully and will outline my steps to do so below. A small caveat – I've only gotten this to work the way I'll outline below. I've tried getting CyanogenMod after the LS980ZVA/C/D OTA and no matter what I do I cannot get it to work. That being said, let's get to it.
Edit: I've added videos!!
Part 1: http://youtu.be/NRwlxeUprZE
Part 2: http://youtu.be/7rohyf_W13k
Part 3: http://youtu.be/Uw3J5ZTb3ro
*REMEMBER* - Always create Nandroid backups before flashing a ROM or doing anything, really.
Required Materials (some of these files (LS980ZV8_13.TOT) are over 2GB, FYI):
EDIT: I have put all the required files into a .ZIP archive and uploaded it to Mega
There has been a report that that the CyanogenMod .zip in my file is corrupt. You can still download the file I uploaded, just get CyanogenMod from the link below.
Update: I uploaded *just* the LS980ZV8_13.TOT file to Mega. Here is the link (beware it's not zipped, it's over 3GB).
Code:
* LS980ZV8_13.TOT - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LS980ZV8_13.zip[/URL]
* LGLS980_20130904_LGFLASHv151.dll - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LGLS980_20130904_LGFLASHv151.dll[/URL]
* LG Flash Tool - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/Setup_LGFlashTool_1.8.1.1023.exe[/URL]
* MegaLock.dll - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/MegaLock.dll[/URL]
* IOroot25 - [URL]http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip[/URL]
* LG G2 (Verizon) USB Driver - [URL]http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427[/URL]
* GApps - [url]https://s.basketbuild.com/gapps[/url]
Now, back up any files you want to keep from your phone. This process will remove EVERYTHING from your phone INCLUDING Internal Storage! Also install the USB Driver.
Let's get to it (please read all instructions before doing anything):
Resetting to Stock
Required files: LG Flash Tool, MegaLock.DLL, LS980ZV8_13.TOT, USB Drivers.
1. Install LG Flash Tool , but don't launch it yet!
2. Copy MegaLock.DLL to the root of the installation directory of LG Flash Tool.
3. Launch LG Flash Tool.
4. Check “Manual Mode”
5. Browse to the .DLL file you downloaded by clicking the “...” button to the right of the first text box.
6. Browse to the .TOT file (it'll have to be unzipped) by doing the same thing for the 2nd box.
7. Click okay, then click the green arrow at the top right of the window.
8. Wait for one of the boxes to turn green and say “Ready”
9. Turn off your phone.
10. Plug in the phone to your computer while holding the Vol+ key to put your phone in download mode.
11. Open Device Manager on your computer by pressing Win+R and typing “devmgmt.msc” without the quotes, then pressing enter.
12. Scroll down to “Ports” and expand it.
13. There will be an Android entry, right click it and select “Properties”
14. Select the Port Settings tab, and select Advanced.
15. Change the port number to 41.
16. You may have to unplug and reconnect your phone.
17. The box that said ready should now have some messages inside it (ie. “Waiting for connection.” and stuff about phone checks).
18. Allow the flash tool to do its job, after anywhere between 10 minutes and half an hour the phone will be done resetting. In my experience, the flash tool will always say there was an error after the phone reboots, this is because the phone reboots into Android, but the flash tool has done everything it needs, don't worry!
19. You can now unplug your phone and close LG Flash Tool.
20. Your phone is now on stock LG firmware LS980ZV8!
** - If you're going on to flash CyanogenMod, get through the initial set up, let the phone activate, but don't worry about getting apps or settings, they'll be gone after we flash CM.
Rooting
Required files: IOroot25, USB Drivers
** - I'm going to write this as if you've just reset to stock firmware.
1. Navigate to Settings > About Phone > Software Information
2. Tap on Build Number 7 times, or until there is a pop-up stating that “You are now a developer!”
3. Go back to Settings
4. Go into Developer Settings
5. Enable USB Debugging
6. Plug your phone into your computer.
** - If there is a RSA Fingerprint pop-up, accept it and check Remember this fingerprint
7. Navigate to Ioroot (you may have to extract/unzip the files) and execute root.BAT
8. Follow the on-screen instructions.
** - Note that Ioroot automatically backs up your EFS partition, make sure to keep these files in a safe location, as they can come in handy if something goes wrong.
9. After Ioroot is finished, you can close the program, unplug your phone and disable USB debugging.
10. You're now rooted, you may verify by downloading a Root Checker app from the Google Play Store.
Installing a Custom Recovery
Required Files: None
1. On your phone, navigate to the Google Play Store.
2. Search for FreeGee and install it.
3. Open FreeGee and allow it to download the device list.
4. After the download is finished, you will see a changelog list, close this.
5. Tap on install TWRP (or CWM if you're more comfortable with ClockWork Mod).
** - I recommend TeamWin Recovery Project for newer users because it is more end-user friendly, touch-capable, etc.
6. Wait for FreeGee to do its thing, then you have a custom recovery installed.
7. If you want to, let FreeGee reboot you into Recovery in order to verify.
Installing CyanogenMod 11
Required Files: CyanogenMod 11 ZIP, USB Drivers
** - Get the CyanogenMod 11 ZIP from https://download.cyanogenmod.org/?device=ls980 I recommend using the latest SNAPSHOT – get the NIGHTLY only if there are problems with the SNAPSHOT.
1. Place the CM 11 ZIP on the root directory of your internal storage.
2. Power off your phone (without it plugged in).
3. Turn on your phone holding PWR+VOL-Down until the screen says “Recovery mode”
** - The screen may say something about a factory reset, in this case press the power button 3 times and you'll be brought into recovery.
4. Tap on install
5. Scroll down to the CM 11 ZIP and tap it
6. Follow the instructions and when prompted to wipe the dalvik and cache, select yes.
** - you may have to do an advanced wipe and select everything except for internal storage, but do this only if CyanogenMod doesn't install properly.
7. You now have CyanogenMod 11 on your phone!
**- You will have to install GApps in order to access the Google Play Store and other Google Apps. You can download it using the browser on your phone or by transferring the .zip file to the root of your phone.
**- To install GApps just boot into recovery, select Install, and navigate to the GApps .zip. Swipe to install.
If you have any questions or any issues, just let me know. Not everything is accurate as I don't have access to Windows right now so I'm going based off memory. I plan on reinstalling Windows 8.1 Professional and making a video to go along with this. If at any point throughout this walkthrough you find inaccurate information or something goes wrong, let me know and I'll help out/update the article. Good luck!
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
damiloveu said:
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
Click to expand...
Click to collapse
I use CyanogenMod 11 as my everyday ROM, never have any issues (besides some personal preferences). To confirm that you have a good stable build, check your build number and info. I will post mine below for you to compare to.
To check your build number navigate to Settings > About Phone
Code:
Model Number.................LG-LS980
CyanogenMod Version..........11-20140804-SNAPSHOT-M9-ls980
Android Version..............4.4.4
Baseband Version.............M8974A-AAAANAZM-1.0.190034
Kernel Version...............3.4.0-CM+
[email protected] #1
.............................Sun Aug 3 22:34:14 PDT 2014
I used this download for my CM: Direct Download from CyanogenMod
official.xian said:
I use CyanogenMod 11 as my everyday ROM, never have any issues (besides some personal preferences). To confirm that you have a good stable build, check your build number and info. I will post mine below for you to compare to.
To check your build number navigate to Settings > About Phone
Code:
Model Number.................LG-LS980
CyanogenMod Version..........11-20140804-SNAPSHOT-M9-ls980
Android Version..............4.4.4
Baseband Version.............M8974A-AAAANAZM-1.0.190034
Kernel Version...............3.4.0-CM+
[email protected] #1
.............................Sun Aug 3 22:34:14 PDT 2014
I used this download for my CM: Direct Download from CyanogenMod
Click to expand...
Click to collapse
I am using the same ROM as yours. I will flash back to Stock ROM and if the GPS still doesn't work, I have to contact LG to get a replace one.
damiloveu said:
I am using the same ROM as yours. I will flash back to Stock ROM and if the GPS still doesn't work, I have to contact LG to get a replace one.
Click to expand...
Click to collapse
Sounds good. I can confirm that my GPS works fine on this ROM so... Good luck. Let me know if you have any questions!
Can U help me with this....
I have LG G2 LS980ZVC Rooted device, and SuperUser is installed.
I want to migrate from stock ROM to CyanogenMod ROM.
But I want the device to work as of the LG G2 D802 (International).
As I will be using it in INDIA (GSM 850/900/1800/1900).
I am very much new to Android and confused to pick the ROM and about the installation procedure.
Seek expert advice about this concern.
Plz suggest... ( attach Hyper link of threads / Videos about the procedure of installation and ROM download link while replying).
Thanks in Advance.......
AJ, I will do some research as to unlocking this phone. I am a bit busy right now but I'll reply by the end of the day.
This phone is already unlocked and works fine with Indian SIM
This phone is already unlocked and works fine with any Indian SIM. I Just want to migrate to CyanogenMod ROM.
official.xian said:
AJ, I will do some research as to unlocking this phone. I am a bit busy right now but I'll reply by the end of the day.
Click to expand...
Click to collapse
I can't find any information regarding unlocking on CyanogenMod specifically, but maybe you could do the same steps at: http://forum.xda-developers.com/showthread.php?t=2655133 after you follow my instructions to install CyanogenMod.
:Confused
This phone is already unlocked and works fine with any Indian SIM.
I am Just confused to pick between these two CyanogenMod ROMs :
1. (ls980 LG G2 (Sprint))
https://download.cyanogenmod.org/?device=ls980
https://download.cyanogenmod.org/get/jenkins/78482/cm-11-20140804-SNAPSHOT-M9-ls980.zip
OR
2. (d802 LG G2 (Intl))
https://download.cyanogenmod.org/?device=d802
https://download.cyanogenmod.org/get/jenkins/78458/cm-11-20140804-SNAPSHOT-M9-d802.zip
And any guidelines to install the CynogenMod ROM, as I am New to this.
Thanks in Advance. .
official.xian said:
I can't find any information regarding unlocking on CyanogenMod specifically, but maybe you could do the same steps at: http://forum.xda-developers.com/showthread.php?t=2655133 after you follow my instructions to install CyanogenMod.
Click to expand...
Click to collapse
Never, I repeat NEVER flash or install ANYTHING that is not specifically for your phone!! This is the fastest way to brick your device, possibly permanently. I understand that you have already unlocked your phone, but you've done so on a stock ROM. What I was saying is follow my instructions to install CyanogenMod (the LS980 version) on your phone, then (re)unlock it following the instructions at the thread I linked to. I'm not sure how to unlock on CM11, but it can be done: LG G2 LS980 GSM UNLOCKED!: http://youtu.be/r8XCpm046-k
damiloveu said:
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
Click to expand...
Click to collapse
I did try and after a lot of got it to work CM11, you only need ZV8 modem/radio.
Had problems with the GPS even try a lot of apps none of them got it to work, then change the gps.conf file for the orginal LG conf and worked great. The only ROM that the GPS worked since the start was PA all of the others are based on CM so the file wont work, at least for me.
The gps.conf file its on "etc" folder.
CM really its great but to me Omni and most of all that i try in this days (trying to get a good GPS just to play Ingress) Its PA
Good luck
emi_fer said:
I did try and after a lot of got it to work CM11, you only need ZV8 modem/radio.
Had problems with the GPS even try a lot of apps none of them got it to work, then change the gps.conf file for the orginal LG conf and worked great. The only ROM that the GPS worked since the start was PA all of the others are based on CM so the file wont work, at least for me.
The gps.conf file its on "etc" folder.
CM really its great but to me Omni and most of all that i try in this days (trying to get a good GPS just to play Ingress) Its PA
Good luck
Click to expand...
Click to collapse
I've never had an issue with CyanogenMod. If you wipe before you install and don't do anything funky with it you shouldn't have a problem. Following my instructions CyanogenMod works flawlessly (for me at least).
official.xian said:
I've never had an issue with CyanogenMod. If you wipe before you install and don't do anything funky with it you shouldn't have a problem. Following my instructions CyanogenMod works flawlessly (for me at least).
Click to expand...
Click to collapse
Always Wipe data/Factory reset when change to a different ROM, as i said the only one that worked for me its PA because uses the stock gps.conf thats all
emi_fer said:
Always Wipe data/Factory reset when change to a different ROM, as i said the only one that worked for me its PA because uses the stock gps.conf thats all
Click to expand...
Click to collapse
How long ago did you have problems?
official.xian said:
So I've been helping around the forums with people trying to install CyanogenMod on the Sprint LG G2 (LS-980). I have done this successfully and will outline my steps to do so below. A small caveat – I've only gotten this to work the way I'll outline below. I've tried getting CyanogenMod after the LS980ZVA/C/D OTA and no matter what I do I cannot get it to work. That being said, let's get to it.
*REMEMBER* - Always create Nandroid backups before flashing a ROM or doing anything, really.
Required Materials (some of these files (LS980ZV8_13.TOT) are over 2GB, FYI):
Code:
* LS980ZV8_13.TOT - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LS980ZV8_13.zip[/URL]
* LGLS980_20130904_LGFLASHv151.dll - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LGLS980_20130904_LGFLASHv151.dll[/URL]
* LG Flash Tool - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/Setup_LGFlashTool_1.8.1.1023.exe[/URL]
* MegaLock.dll - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/MegaLock.dll[/URL]
* IOroot25 - [URL]http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip[/URL]
* LG G2 (Verizon) USB Driver - [URL]http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427[/URL]
Now, back up any files you want to keep from your phone. This process will remove EVERYTHING from your phone INCLUDING Internal Storage! Also install the USB Driver.
Let's get to it (please read all instructions before doing anything):
Resetting to Stock
Required files: LG Flash Tool, MegaLock.DLL, LS980ZV8_13.TOT, USB Drivers.
1. Install LG Flash Tool , but don't launch it yet!
2. Copy MegaLock.DLL to the root of the installation directory of LG Flash Tool.
3. Launch LG Flash Tool.
4. Check “Manual Mode”
5. Browse to the .DLL file you downloaded by clicking the “...” button to the right of the first text box.
6. Browse to the .TOT file (it'll have to be unzipped) by doing the same thing for the 2nd box.
7. Click okay, then click the green arrow at the top right of the window.
8. Wait for one of the boxes to turn green and say “Ready”
9. Turn off your phone.
10. Plug in the phone to your computer while holding the Vol+ key to put your phone in download mode.
11. Open Device Manager on your computer by pressing Win+R and typing “devmgmt.msc” without the quotes, then pressing enter.
12. Scroll down to “Ports” and expand it.
13. There will be an Android entry, right click it and select “Properties”
14. Select the Port Settings tab, and select Advanced.
15. Change the port number to 41.
16. You may have to unplug and reconnect your phone.
17. The box that said ready should now have some messages inside it (ie. “Waiting for connection.” and stuff about phone checks).
18. Allow the flash tool to do its job, after anywhere between 10 minutes and half an hour the phone will be done resetting. In my experience, the flash tool will always say there was an error after the phone reboots, this is because the phone reboots into Android, but the flash tool has done everything it needs, don't worry!
19. You can now unplug your phone and close LG Flash Tool.
20. Your phone is now on stock LG firmware LS980ZV8!
** - If you're going on to flash CyanogenMod, get through the initial set up, let the phone activate, but don't worry about getting apps or settings, they'll be gone after we flash CM.
Rooting
Required files: IOroot25, USB Drivers
** - I'm going to write this as if you've just reset to stock firmware.
1. Navigate to Settings > About Phone > Software Information
2. Tap on Build Number 7 times, or until there is a pop-up stating that “You are now a developer!”
3. Go back to Settings
4. Go into Developer Settings
5. Enable USB Debugging
6. Plug your phone into your computer.
** - If there is a RSA Fingerprint pop-up, accept it and check Remember this fingerprint
7. Navigate to Ioroot (you may have to extract/unzip the files) and execute root.BAT
8. Follow the on-screen instructions.
** - Note that Ioroot automatically backs up your EFS partition, make sure to keep these files in a safe location, as they can come in handy if something goes wrong.
9. After Ioroot is finished, you can close the program, unplug your phone and disable USB debugging.
10. You're now rooted, you may verify by downloading a Root Checker app from the Google Play Store.
Installing a Custom Recovery
Required Files: None
1. On your phone, navigate to the Google Play Store.
2. Search for FreeGee and install it.
3. Open FreeGee and allow it to download the device list.
4. After the download is finished, you will see a changelog list, close this.
5. Tap on install TWRP (or CWM if you're more comfortable with ClockWork Mod).
** - I recommend TeamWin Recovery Project for newer users because it is more end-user friendly, touch-capable, etc.
6. Wait for FreeGee to do its thing, then you have a custom recovery installed.
7. If you want to, let FreeGee reboot you into Recovery in order to verify.
Installing CyanogenMod 11
Required Files: CyanogenMod 11 ZIP, USB Drivers
** - Get the CyanogenMod 11 ZIP from https://download.cyanogenmod.org/?device=ls980 I recommend using the latest SNAPSHOT – get the NIGHTLY only if there are problems with the SNAPSHOT.
1. Place the CM 11 ZIP on the root directory of your internal storage.
2. Power off your phone (without it plugged in).
3. Turn on your phone holding PWR+VOL-Down until the screen says “Recovery mode”
** - The screen may say something about a factory reset, in this case press the power button 3 times and you'll be brought into recovery.
4. Tap on install
5. Scroll down to the CM 11 ZIP and tap it
6. Follow the instructions and when prompted to wipe the dalvik and cache, select yes.
** - you may have to do an advanced wipe and select everything except for internal storage, but do this only if CyanogenMod doesn't install properly.
7. You now have CyanogenMod 11 on your phone!
If you have any questions or any issues, just let me know. Not everything is accurate as I don't have access to Windows right now so I'm going based off memory. I plan on reinstalling Windows 8.1 Professional and making a video to go along with this. If at any point throughout this walkthrough you find inaccurate information or something goes wrong, let me know and I'll help out/update the article. Good luck!
Click to expand...
Click to collapse
I am in the process of resetting everything back to stock. However, I was reading other articles and it mentioned that you must choose the correct files that correspond to either the 16gigs or 32 gigs. In this set of instructions however, it only provides users with one zv8 file for download. I just don't want to mess something up by using the incorrect files. Would appreciate someone's help. Thanks
Robles23 said:
I am in the process of resetting everything back to stock. However, I was reading other articles and it mentioned that you must choose the correct files that correspond to either the 16gigs or 32 gigs. In this set of instructions however, it only provides users with one zv8 file for download. I just don't want to mess something up by using the incorrect files. Would appreciate someone's help. Thanks
Click to expand...
Click to collapse
I have seen what you're talking about elsewhere but I don't believe that this applies in this situation. I have the 32GB LS980, and haven't had an issue, still have all my storage space. From everything that I've gathered from the internet when learning how to do everything a wrote the size doesn't matter. If you're still concerned I can do some more digging, but I don't think you'll have a problem.
official.xian said:
I have seen what you're talking about elsewhere but I don't believe that this applies in this situation. I have the 32GB LS980, and haven't had an issue, still have all my storage space. From everything that I've gathered from the internet when learning how to do everything a wrote the size doesn't matter. If you're still concerned I can do some more digging, but I don't think you'll have a problem.
Click to expand...
Click to collapse
Very much appreciate your answer brother. I also have a 32gb model. No need to do more research. I will try this method ones I get home from work today. Ones again, I appreciate your repay and tutorial.
Robles23 said:
Very much appreciate your answer brother. I also have a 32gb model. No need to do more research. I will try this method ones I get home from work today. Ones again, I appreciate your repay and tutorial.
Click to expand...
Click to collapse
Glad to help. If you feel unsure about anything I'm also working on a video to upload to YouTube as well (after I finish it I'll edit the OP) that goes over the process. Good luck.
official.xian said:
Glad to help. If you feel unsure about anything I'm also working on a video to upload to YouTube as well (after I finish it I'll edit the OP) that goes over the process. Good luck.
Click to expand...
Click to collapse
Hell yeah I will love to watch and follow that tutorial. I will wait for it. Thank you!
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
ZB2016 said:
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
Click to expand...
Click to collapse
Restoring the backup is the only solution it seems.
Yes ... hmmm ... backup ... that was what I intended to do that morning when the BAMMMM happened. I really had a bad start with the 7X ...
So in case someone has a backup of a clean or nearly clean system partition, please send me a PN. Tnx in advance!
Normal make a Backup in Twrp before modify the System Partition.
Make not an Official Ota Update with Rooted and Twrp installed Rom
Its not the phones mistake that you mess up and wakeup and take the phone for a spin in half sleep
and bamm, i really dont know what that meant. i would say go to the honor care center and get it to them to work.
the procedure which i know of is tough and things like bamm happening might worsen things like TWRP not starting at all.
i have seen people bricking their phones but its never the phones fault.
i would never recommend doing a "BAMM" thing doing and flashing all the stuff randomly cz i dont think magisk is supported fully yet to our phone and you flashed it without asking anyone.
the other russian forums are flashing chinese stock firmware which is the only original firmware available, but the task to change the settings to work for other variant is a huge stock which i gave link to a few people but for you i wont recommend that cz obviously your situation is totally different so go to the honor center and explain them and they would help you.
good luck! next time verify and be careful before flashing anything at random cause its not the phones fault.
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
ZB2016 said:
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
Click to expand...
Click to collapse
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
sid21 said:
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
Click to expand...
Click to collapse
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
ZB2016 said:
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
Click to expand...
Click to collapse
I am in contact with the user who posted the article and tested it himself and requested a proper one in english language but he is busy so it hasnt proceeded.. But soon he ll be free to write one up for me so i will post it on XDA..
I'm in a very similar boat. The Magisk v15 update bricked my L24. I had another one available and have made back ups through twrp to restore on the bricked one. It actually boots, but all I get is a black screen with the menu, home, and back buttons now. Holding power gives me the options to restart and power off. Hope they release the stock rom soon, or custom roms be available soon.
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Sudeep Duhoon said:
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Click to expand...
Click to collapse
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Back to life ... at least about 80%. Rooting leads to corrupt system partition (unable to boot afterwards) and bootloader can only be reached while a USB cable is connected (unusual behaviour). Nevertheless ... got it running. SID ... you are my hero of the day. Will PM you regarding comments for your thread.
ZB2016 said:
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
Click to expand...
Click to collapse
i think i have to write a guide now. this was the first but more can come soon enough. may be today i'll write a guide to backup your phone (all 48 partitions) and then root so you always have all the necessary files to restore it back to life.
sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Plz give link of custom rom for honor 7x
dhananjay 007 said:
Plz give link of custom rom for honor 7x
Click to expand...
Click to collapse
Who made custom rom for the phone?
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I have honor 7x.
dhananjay 007 said:
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
I have honor 7x.
Click to expand...
Click to collapse
So why are you even asking me for a custom rom?
If you know no one has made yet
UPDATE ... got it back to life, at least partly. The only thing is, that constantly the android adaptions of Huawei is making it unnecessary complex or is stopping progress at all. This is the log of my actual tasks. Key to progress was the unlocking of the system fs, which has some inconsistencies in the file system. In general, it gives me a 7X, that boots and I can install apps via HiSuite. Nevertheless I have no idea how to deal with Gapps. If I install opengapps, I will not be able to register an account - just hangs for a long period and then comes back (are there any logs written on the device to analyze a bit deeper?). Gapps without an account maks no sense. So I tried it without opengapps but with installing play services via HiSuite, granting rights, rebooting twice, installing Playstore, granting rights, rebooting twice, but starting Playstore after this procedure just tells me, that gms has to be installed (which in fact is already).
Any hint?
- prep like described by SID21 including HiSuite-Installation
- optional: download Nova Launcher, Firefox and Total Commander from "apkmirror.com"
- boot into TWRP
- mount system r/w
- format data
- wipe all partitions besides external SD
- mount vendor
- install image VENDOR.IMG
- reboot to bootloader- USB-connect to PC
- kill HiSuite in case it comes up
- Start MultiTools
- Click on "Unbrick" in upper list
- enter Path to prepared folder in grey field
- Validate: at least 4 checked boxes
- Click on Box labeled "Unbrick"
- Validate messages: "Completed", "All images are flashed successfully"
- Click "Recovery" in upper list
- in frame labeled "Flash custom Recovery/eRecovery":
- Click Button labelde "Select image" and navigate to file twrp_Honor_7x.img and select
- Click button "Flash Recovery"
- in Popup window select "Restart from fastboot" and unplug the phone from USB- Stop Multitools
- Wait for first restart, phone comes up
- Adapt phone settings:
- Security & Privacy/Additional Settings:
- set "Unknown sources"
- set "Allow HiSuite to use HDB" - About phone:
- Click 7 times in a row on "Build number" to activate developer options - Developer options:
- Activate "USB debugging"
- optional: Activate "Allow ADB debugging in charge only mode" - WiFi:
- connect to your WiFi network- USB-connect phone
- Phone popup: set "Allow access to device data?" to "Yes, allow access"
- Phone popup: set "Allow connection in HDB mode?" to "Yes, allow access"
- Phone popup: set "Allow USB debugging?" to "Ok"
- PC HiSuite Popup to inform about installation of services to manage device
- optional: PC HiSuite Apps:
- Install a proper Launcher (e.g. Nova Launcher) and make it the default launcher
- Install a proper file manager (e.g. Total Commander)
- install a browser (e.g. firefox)
- Download opengapps from opengapps.org and save to sd card- USB-disconnect phone
- Restart phone into TWRP
- do not get access to system partition
- Mount: Validate: system is not mounted at all
- Advanced/Terminal:
- enter "ls -l /dev/block/platform/hi_mci.0/by-name/system"
- validate: the filesystem points to /dev/block/mmcblk0p44
- ONLY DO THE FOLLOWING IF YOU KNOW WHAT YOU ARE DOING!!!
- enter "resize2fs /dev/block/mmcblk0p44"
- Validate Message: The Filesystem is now 1200128 blocks long.
- enter "e2fsck /dev/block/mmcblk0p44"
- Validate message: system clean, ... - Mount:
- check "system"
- uncheck "Mount system partition read-only" and swype in next screen to get access to system
- check "system" - Install:
- Select storage: Micro SDCard
- install SuperSU (I've chosen 2.82)
- Wipe Cache/Dalvik - Reboot:
- reboot to system
- do not install TWRP app- Reboot takes long time
- During boot animation another reboot occurs
- Boot animations gets finalized, phones comes up normally
The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo
Thanks. So this is GSI? Bugs?
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain
DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)
I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?
I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany
well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse
I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6
Will this image work with the SM-A505G version?
USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.
InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel
the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP
hey man, the project is being upgraded? Tanks for your time
InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware
I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.
Hi All!!
This thread will now contain pre rooted Odin files for F926B users to flash and update
Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE
THIS IS FOR F926B ONLY
The process requires knowledge of basic adb and YOU MUST HAVE ADB INSTALLED BEFORE TRYING THIS
This will no longer wipe data but it is advisable to backup first anyway - i wont be responsible for any data lost that could have been backed up
PROCESS to update from rooted a11 or a12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP mount menu disable MTP
5 - ONLY IF YOU DONT HAVE A MAGISK.ZIP ON INTERNAL STORAGE copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer)
6 - go to the TWRP flash menu and you should see the app-debug.zip, flash it to root your A12 device - this needs to be done everytime TWRP is flashed in Odin it seems
7 - reboot to system from TWRP power menu
You will boot rooted, updated and with intact data if all the steps above are followed correctly
------------------------------------------------------------------------------------------------------------------
PROCESS IF COMING FROM STOCK A12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC (please ensure dev settings are enabled and that you have unlocked bootloader and checked "Oem unlock" is faded out under dev settings)
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP wipe menu and format device (type yes and press enter) - then reboot TWRP
5 - when TWRP has rebooted, go to the mounts menu and disable MTP -> this will allow us to send app-debug.zip (magisk) to your sdcard
6 - copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working
7 - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer) - go to the TWRP flash menu and you should see this app-debug.zip, flash it to root your A12 device
8 - as stated previously, i have disabled encryption therefore we just need to boot STRAIGHT to SYSTEM from the TWRP POWER MENU
9 -When phone reboots, set up as normal and you should now see a magisk stub in the app drawer meaning you are rooted
PLEASE NOTE THAT THE MAGISK PATCHED AP FILE IS UPLOADING AND WILL BE AVAILABLE IN A FEW HOURS
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
ok my teammate has built a tested and working AP file to use in the guide above - this will be up very shortly
mine was fine however my internet connection is not lol
Ok guys - sorry for the muck about!! the patched AP file is now live in the first post - therefore you can go ahead and root!
Follow the steps carefully, please also read and make sure you have everything prepared before you start
Had a couple of peeps join my telegram chat asking about OEM option being missing.
Please note that this guide only covers the WWE F926B at the moment (US models have a locked bootloader afaik)
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
JazonX said:
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
Click to expand...
Click to collapse
At the moment there is sadly no camera til the bootloader is relocked. Hopefully a fix is found soon
exocetdj said:
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
Click to expand...
Click to collapse
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
Hi mate have you managed to access it yet? if not ill try sort links out
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
try this alternative link
If not ill ask my teammate to mirror to Mega
exocetdj said:
Hi mate have you managed to access it yet? if not ill try sort links out
Click to expand...
Click to collapse
Yeah, after an hour or so it let me in again, and didn’t fail this time. :O)
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
ultramag69 said:
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
Click to expand...
Click to collapse
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
exocetdj said:
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
Click to expand...
Click to collapse
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
ultramag69 said:
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
Click to expand...
Click to collapse
So from my understanding, Knox was actually designed for dual rom booting, as a way to keep the original firmware in tact and safe, but also be able to flash a custom rom for dual boot. But investors, carriers, and the like decided they weren't happy with that and saw that it could also be used to lock the device down to make everything more secure for their intents. After like 4 iterations where Samsung kept being pushed, it became what it is today.
I'm assuming they thought if they just impliment everything that a person would root for, that it would make people OK with it, but of course not the case. In the end, just like any other major corporation, they let money push them around
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
As soon as you flash any custom binary then your software is classed as custom and will not boot at all with a locked bootloader. It would soft brick requiring a stock odin flash to revive device most likely
dirtybudha said:
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
Click to expand...
Click to collapse
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum
Samkey apparently now supports f926b but I'm getting unsupported firmware errors on AUG8 and AUHF. I really want to get rid of this three bloat
Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5EEA 13.0.3Global 13.0.1Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.
Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.
Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!
Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.
thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks
Can i update ota to 13.0.2 after rooted? Just update and root again?
Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2
How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?
thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.
vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img
kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet