[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Didn't work for me, I tried with the AOSP_super.tar, which succeeded, but got a boot loop.
I tried with the AP_AOSP_.., but it fails, I got "Only official released binaries are allowed to be flashed (SUPER)". The same occurs with Havoc tar.
When I tried the AOSP_super.tar again, I got the same message, instead of a boot loop.
Steps:
Unlock bootloader (OEM unlock is also permanently triggered in developer settings)
Power off phone
Download mode (volume up + power on) and connect USB
Load tar file in AP slot (other slots are empty)
Factory reset and clear cache
Flashing back the stock rom still works. Stock rom: A217FXXU5BUB4
Any ideas?
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Is there a way to install Havoc OS prerooted?
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Yeah I think I know why, There's a filesystem problem, the UUID and filesystem has to be the same as the system.img of OneUI
The UUID depends in the device binary that you have (in the firmware)
I'd help you but, all my steps just led to a dead end sadly
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Hi i flash havocos but not reboot in rom reboot in download mode help please
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Can you make a unrooted gsi? If you could please use dot os 5.2 it would mean world for me. The community also i think.
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
EatABRick said:
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
Click to expand...
Click to collapse
It worked, but with older version of OneUI installed. I don't have this phone anymore but maybe i can help
Related
About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...
I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.
THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build
Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!
Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones
Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.
Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:
Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.
Greetings,
Both my devices are stuck in bootloop but they are facing different issues; details are as followed:
Devices Information:
- Manufacturer: SAMSUNG
- Devices Model: SM-J200GU
- Devices Nickname: j2lte
- Region: XME
- Firmware: J200GUDXS3AQG2
- Baseband: J200GUOLB3APC1
PC info:
WIndows 7 Ultimate SP1 with latest updates
Java 8 Update 144.
______________________________________________________________________________________
I know there are thousands of similar threads, most solutions I found were "enable USB debugging", "use ADB Fastboot", "reinstall drivers" and so on but trust me, I've tried every single options I could; few of them are:
REINSTALLED both Android and Samsung USB drivers (from version 1.3.8.5 to 1.5.6.3), whether you mean both installed together or separately
REINSTALLED Minimal ADB and FASTBOOT (1.3, 1.4, 1.4.2, 1.43)
TRIED using different versions of ODIN. (v1.85, v3.09, v3.10.6, v3.11, v3.12)
_____________________________________________________________________________________
Issue for Device #1: PC UNABLE TO DETECT DEVICE
Screen Options: Stock Recovery, Bootloader, Bootsplash/Bootlogo
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
I have tried 3 different cables from SAMSUNG OFFICIAL, Lenovo and another off-market (REMAX) respectively on all the 8 USB PORTS that I have, and yes I have reinstalled the USB PORTS and also DISABLED and re-ENABLING it. I am able to boot into stock recovery but it's written "E: UNABLE TO MOUNT /SYSTEM" when I tried to perform HARD RESET. This only happens after I flashed the latest Firmware (J200GUDXS3AQG2).
_____________________________________________________________________________________
Issue for Device #2: PC ABLE TO DETECT DEVICE
Screen Options: Bootlogo/Bootsplash ONLY
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: OFFICIAL
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED
No matter what key combination I pressed, IT ONLY BOOTS INTO BOOTLOADER MODE. Yes, not even a chance to peek at the BOOTSPLASH/BOOTLOGO screen. Stock firmware flashing was SUCCESSFUL but it BOOTS back to the damn same BOOTLOADER page (without all the details), able to flash TWRP (v2.87, v3.0.0, v3.0.2, v3.1.1) SUCCESSFULLY but FRP LOCK is ON.
_____________________________________________________________________________________
I hope the details given are sufficient enough for all you GRANDMASTERS, HACKERS, DEVELOPERS or even PASSER-BYs to provide me with a solution other than what I have done. In summary;
Device #1: PC unable to detect device, HARD RESET successful with ERROR "E: unable to mount /system".
Device #2: Tried flashing TWRP but FRP Lock ON, tried flashing stock firmware SUCCESSFULLY but boot into BOOTLOADER mode again, unable to enter stock recovery page or any other screens EXCEPT FOR THE BOOTLOADER.
_____________________________________________________________________________________
Thank you in advance & have a great day.
No one?
DaRdamnDoG said:
No one?
Click to expand...
Click to collapse
Have you tried using a different windows computer ?
George Malas said:
Have you tried using a different windows computer ?
Click to expand...
Click to collapse
Device #1 has been fixed, apparently another third party USB cable managed to get my PC to detect it in bootloader mode, the rest was easy.
As for Device #2, I was told by mobile shop owner that in recent months many of Samsung devices (especially Galaxy S7 variants and Galaxy Notes) had the same issue as I mentioned and he explains further that it is some sort of the manufacturers' effort or tactic to encourage mobile users to upgrade our devices.
How big of a ****ing asshole is Samsung to do such thing. Really ? They want to kill your ,quote on quote ,old device just so you can buy a new one. Just so I can clear things up in my mind , you mentioned above that you tried flashing TWRP on device #2 but FRP Lock was ON. But FRP Lock has nothing to do with TWRP. FRP Lock is Factory Reset Protection which purpose is to prevent someone from setting up the phone without knowing the credentials of the Google Account previously linked with the device. As long as your bootloader is unlocked , you can hop on TWRP ,flash a custom ROM and your problem should be solved.
SORRY WAS INACTIVE FOR SOMETIME... NOW IM BACK YOU CAN ASK AGAIN...
ALL CHIPSETS UNBRICKING METHOD HAS BEEN POSTED
Hi you may ask me anything related to android and I promise to answer within 24 hours and m reply will definitely work for you.
*****************************************************
SPECIALIST IN ROOTING, DEVELOPMENT, HACKING, SECURITY BYPASS, RECOVERY, FLASHING, CUSTOM ROM'S
*****************************************************
SEE YOU SOON
*****************************************************
•NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE•
LG Aristo v10g Metropcs
How do i start configuring this phone without a google account?
A friend who was using it gave me this phone but forgot the boot password and the google account was not of him. So, now, we can´t use the phone.
Mephis96 said:
How do i start configuring this phone without a google account?
A friend who was using it gave me this phone but forgot the boot password and the google account was not of him. So, now, we can´t use the phone.
Click to expand...
Click to collapse
You mean to say that the phone is in frp mode?
(Factory reset protection)
Yes
FRP..... thanks, id did not know what it means.
Yes, it is in FRP
Mephis96 said:
FRP..... thanks, id did not know what it means.
Yes, it is in FRP
Click to expand...
Click to collapse
Can you please tell me the phone model and it's info.
LG Aristo v10g from Metropcs
x.ak**** said:
Can you please tell me the phone model and it's info.
Click to expand...
Click to collapse
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
[PC] HOW TO CURE A BRICKED M-TEK DEVICE!!
///////////////////////////////////////////////////////////////////////////////////////////
• Download and Install the Android USB drivers for your device that I have mentioned below.
• Power Off your device and remove the battery (only if it's removable)
• Download the stock ROM or the Custom ROM on your PC that you want to flash. (GIVEN BELOW)
• Download and extract SPFT (Smart Phone Flash Tool) on your PC, you will be able to see the files shown in the picture below. (Pic 1.1)
• Open Flash tool.exe (Pic 1.2)
• Once SPFT is launched tap on Download tab. (Pic 1.3)
• In download tab click on Scatter-Loading button. (Pic 1.4)
• Now locate the Scatter File that you will find in the Stock ROM folder that you downloaded in step 3. (Pic 1.5)
• Click on Download button to start the flashing process.(Pic 1.6)
• After finishing a success message will appear. (Pic 1.7)
///////////////////////////////////////////////////////////////////////////////////////////
Downloads:-
https://androiddatahost.com/b9cyw (DRIVERS)
https://spflashtool.com/download/SP_Flash_Tool_v5.1744_Win.zip (SPFT)
https://www.needrom.com/download/lenovo-s850/ (ROM FOR LENOVO S850, REGISTRATION NEEDED ON WEBSITE TO DOWNLOAD THE ROM)
///////////////////////////////////////////////////////////////////////////////////////////
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
I was working on another project that you can see below give me 1 hour I'll get back to you ASAP.
Best tool like SetCPU for controlling CPU with profiles?
SetCPU doesn't allow core control though
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
How to BYPASS FRP LOCK!
Test conducted on Virtual Machine on my PC
****************************************************************
I am not responsible for any damage you may cause to your device!
****************************************************************
****************************************************************
Never wanted to upload it but did it because I aim at helping people.
****************************************************************
Google FRP (factory reset protection) is aimed at making a stolen phone less valuable.
We usually keep our phones locked with a password or pattern but once its stolen it is easy to erase the data (via Hard Reset) and reuse the phone. With Google FRP in place, whenever the phone is formatted using hardware keys it will ask for the last synced google account details before proceeding further.
///////////////////////////////////////////////////////////////////////////////////////////
Until now, everytime some sort of hack comes out to bypass this screen and then its patched with a security update very soon. Same is the case with LG Aristo. There is a working solution as of now but it may not last long. Let’s see how to get this working –
///////////////////////////////////////////////////////////////////////////////////////////
How to Bypass LG Aristo Google Account –
This process is lengthy, but it’s a sure shot method and works every time.
We need 2 apps to complete this bypass process. They are Shortcut Master Lite and Sidebar Lite. Download the zip file from below link.
DOWNLOAD
>Extract the zip file and transfer the apk files to a micro sd card. Install the SD card in your LG Aristo before proceeding further.
///////////////////////////////////////////////////////////////////////////////////////////
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
Done
Drop a like on all my replies so I can stay encouraged and help you further.
YeshYyyK said:
Best tool like SetCPU for controlling CPU with profiles?
SetCPU doesn't allow core control though
Click to expand...
Click to collapse
You may use Kernel Manager it's super useful and will do what you're asking for!
Hi ! Could you help me with my problem ?? https://forum.xda-developers.com/search.php?searchid=446201503
No one seems to be able to help me... thanks a lot!!!!
antoflos said:
Hi ! Could you help me with my problem ?? https://forum.xda-developers.com/search.php?searchid=446201503
No one seems to be able to help me... thanks a lot!!!!
Click to expand...
Click to collapse
I will definitely help you just give me one hour but can you post the following info:
Model Number:
Exact Problem:
How that problem occured:
Model Number: SM-G935F / Galaxy S7 edge
Exact Problem : I can't go back to the dock ROM
How that problem occured : Last week, I wanted to try to change my phone a SM-G935F on a custom rom " Minotaurus Oreo V10". I did it successfuly but didn't like it so much so I decided to go back to stock Rom.
I used Odin and a stock ROM for that but I think I made a big mistake by not wiping with TWRP before flashing with Odin.
It resulted that my phone was stocked on the S7 edge logo. Luckly I can go on download mode so it's not hard bricked but Odin failed on every flash I've tried. It stoped at the step "config.msi"
To flash I used this dock Rom : SM-G935F_1_20161201150115_pbdym44h2s_fac
x.ak**** said:
I will definitely help you just give me one hour but can you post the following info:
Model Number:
Exact Problem:
How that problem occured:
Click to expand...
Click to collapse
Hey man this quite difficult and i need to install this phone's firmware on my VIRTUAL Machine, basically I request you to wait for the time being so I can save your phone.
Drop a like on all my comments above to encourage me.
Huawei P10+ Firmware on Huawei P10 - by accident
Hi:
On my P10, I used Firmwarefinder for Huawei to find the firmware (Oreo with EMUI 8) and after verifying, I downloaded and upgraded the P10 to new firmware. After reboot, the dpi is seemed changed (as picture attached) and when I went to check it on about phone, it says Model is VKY (which is Huawei P10+) - picture attached.
Is there a way to rollback and install the correct firmware on this phone somehow?
antoflos said:
Model Number: SM-G935F / Galaxy S7 edge
Exact Problem : I can't go back to the dock ROM
How that problem occured : Last week, I wanted to try to change my phone a SM-G935F on a custom rom " Minotaurus Oreo V10". I did it successfuly but didn't like it so much so I decided to go back to stock Rom.
I used Odin and a stock ROM for that but I think I made a big mistake by not wiping with TWRP before flashing with Odin.
Click to expand...
Click to collapse
***********************************************************************************
I AM NOT RESPONSIBLE FOR ANY FURTHER DAMAGE THAT MAY BE CAUSED TO YOUR DEVICE...(UNLIKELY TO HAPPEN)
***********************************************************************************
For being able to make the downgrade operation you will have to use a Windows based computer on which you will then install Odin (an official program developed by Samsung and used on update types of operations).
***********************************************************************************
Download Odin on your computer; afterwards install the program by following on screen prompts.
The Samsung Galaxy S7 Edge USB drivers must be installed on your PC too – use Samsung KIES in that respect.
Download the stock / official Android OS for your S7 Edge – from SamMobile or from Samsung’s official website.
Power off your device and reboot into download mode: press and hold the Power, Volume Down and Home buttons for a few moments; then connect your phone with your computer with the help of the USB cable.
After making sure that Odin has recognized your device (the “added” message must be displayed and the ID:COM field should be turned yellow or blue) from the program select the PA option.
Load the firmware file; don’t select the Re Partition and Auto Reboot options; click on Start when done.
Wait while your SGS7 Edge is being updated; when done, remove the USB cord and reboot your phone.
For further info related to the update process reply to my thread
LIKE ALL MY COMMENTS TO ENCOURAGE ME TO HELP YOU.
xironimoh said:
Hi:
On my P10, I used Firmwarefinder for Huawei to find the firmware (Oreo with EMUI 8) and after verifying, I downloaded and upgraded the P10 to new firmware. After reboot, the dpi is seemed changed (as picture attached) and when I went to check it on about phone, it says Model is VKY (which is Huawei P10+) - picture attached.
Is there a way to rollback and install the correct firmware on this phone somehow?
Click to expand...
Click to collapse
No pictures attached!! and yes you can roll back to the stock ROM or even customize the DPI according to your phone [ROOT REQUIRED]
Let me know which one you prefer?
Also like all my comments above to encourage me to help you even faster.
hello all,
yesterday i decide to root my old phone, to see if i could get spoofing working on pokemon go.
flashed it manged it to get superSU , installed magisk, passed the safetycheck, and got spoofing working. but since the phone was full of old apps, i decide to do a factory reset, but looks like this ruined everything, so i went did all steps again, at 1 point i forget to enable oem option.
so i get the msg, custom binary blocked by frp, once i turn my phone on. after hours of searching i found the right firmware, and i could fix this problem.
but now, no matter what i do, if i press volume down, home, power i keep getting in download modus, instant of recovery modus.
i need to get in twrp to install magisk from there.
because if i try, it from the magisk app manager, like i did it the first time, it say say failed to load boot.img
personally i think that i have flashed some wrong roms or something, but i am really stuck now on what do to, is there something easy to uninstall everything i have done? or anyone can point me in a direction of what do now?
Samsung j510fn(2016)
Build: nmf26xj510fnxxu2brb1
thanks, and sorry for my bad english
Hi , if your device is not boot properly try to flash this 4 file firmware:
http://www.mediafire.com/file/h884u0o8dy9va0l/J510FNXXU2BQJ8_7.1.1_4File.zip
Before you do that :
- Make sure that your battery is full charged !
- Put your device into Download mode.
- Load those files properly inside Odin flash tool.
- Connect your device with usb 2.0 port and once Odin detects your device click on Start .
If that doesn't help you to with latest firmware for your region :
https://updato.com/firmware-archive-select-model?q=j510fn&exact=1&r=&v=Nougat(Android+7.1.1)&rpp=15
Good luck
Teddy Lo said:
Hi , if your device is not boot properly try to flash this 4 file firmware:
Before you do that :
- Make sure that your battery is full charged !
- Put your device into Download mode.
- Load those files properly inside Odin flash tool.
- Connect your device with usb 2.0 port and once Odin detects your device click on Start .
If that doesn't help you to with latest firmware for your region :
Good luck
Click to expand...
Click to collapse
Thx my friend it worked
have other question maybe you can help me also? i need to deodex my system, but i read everywhere that i need more then 25% free space on my /system folder. currently i have 0,1mb free of the 3gb. while my internal storage have 8gb free space, is there a easy way to make /system bigger so i can deodex it?
greetz
I don't know , but maybe this can help you:
https://www.samsungdeodex.com/2017/08/rom-deodex-samsung-j510fn.html?m=1
or
https://4pda.ru/forum/index.php?showtopic=925236&st=140
You must to know that phone modification can brick your device permanently !!! So think twice before you do anything.
Hi,
I updated this tablet using Lenovo Smart Upgrade Assistant - update to TB_8504F_USR_S001019_1909091114_Q12000_ROW seems fine except my Wifi/WLAN is totally dead.
If I turn it on, it looks turns back to off quickly, but never actually turns on, and sometimes tablet hangs for a while sometimes when I try to turn wifi on.
I saw a previous post where someone also had this problem and solved it by flashing a modded ROM then flashing the stock ROM and Wifi worked again (with a strange MAC address after that procedure)
But I am stuck because the option to enable OEM Unlocking in Developer Options is greyed out - underneath it says to Connect to the internet or contact your carrier.
I have tried unlocking via ADB but this does not work either.
If I go into settings, WLAN Preferences, it says my MAC Address is 02:00:00:00:00:00 which seems to match other people with this problem.
I tried installing a terminal emulator, "ip link show" returns request send failed: Permission denied, "ip link" says I have:
1: lo:
2: duumy0:
3: [email protected]:
I don't have wlan0 or wlan1, and lo/dummy0/[email protected] did not show the 02:00:00:00::00:00 address.
Please does anyone have any ideas for me?
If I cannot get wifi working, is there any way I can connect to internet using USB to my PC?
I eventually found a version of QFIL that works (part of the QPST package) https://droidfilehost.com/download/download-qpst_2-7-480/
I found a ROM https://drive.google.com/file/d/1C1Fd5m7BMLqrhURAj0kWdqeiZGIuU95k/view (password: https://firmware247.com)
It seems to have downgraded, but now when it starts, I get the screen where I can choose location, and after a few seconds it reboots.
RobinGill said:
I eventually found a version of QFIL that works (part of the QPST package) https://droidfilehost.com/download/download-qpst_2-7-480/
I found a ROM https://drive.google.com/file/d/1C1Fd5m7BMLqrhURAj0kWdqeiZGIuU95k/view (password: https://firmware247.com)
It seems to have downgraded, but now when it starts, I get the screen where I can choose location, and after a few seconds it reboots.
Click to expand...
Click to collapse
Please try to format data (if you don't have important data in the device) and reboot. If that doesn't help, download latest firmware (S001031). You can also try a custom ROM. Below are links to them:
LineageOS 16.0 (Android 9)
LineageOS 17.1 (Android 10)
Resurrection Remix OS (Android 10)
crDroid (Android 10)
adazem009 said:
Please try to format data (if you don't have important data in the device) and reboot. If that doesn't help, download latest firmware (S001031). You can also try a custom ROM. Below are links to them:
LineageOS 16.0 (Android 9)
LineageOS 17.1 (Android 10)
Resurrection Remix OS (Android 10)
crDroid (Android 10)
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately I can't load any custom ROM's because my bootloader is locked.
I downloaded twrp-3.2.3-0-tb_8504x.img and renamed that to recovery.img and put in the folder with the rest of stock ROM and reflashed the downgraded stock ROM (TB-8504F_S000029_170518_ROW_QFIL) but same problem, and I still have normal recovery, not TRWP so I can't load custom ROM's.
Any chance you can please share a link to S001031 please to see if that helps?
I just tried flashing stock ROM TB_8504F_USR_S130004_1902221150_Q12000_SCP and now OEM Unlocking is not greyed out, but I'm still stuck with Android Recovery instead of TRWP. Hopefully will have fun tomorrow.
Ok, today installed TWRP 3.3.1-0 and tried various ROM's but still no luck:
crDroidAndroid-10.0-20210731-TB8504-v6.20 Boot logo loop
RROS-Q-8.6.9-20210519-TB8504-Unofficial Boots but no wifi or bluetooth
RROS-Q-8.7.1-20210726-TB8504-Unofficial Boots but no wifi or bluetooth
lineage-16.0-20200319-UNOFFICIAL-TB8504 Boot logo then rebooting to TWRP
lineage-17.1-20210408-UNOFFICIAL-TB8504 Boot logo then rebooting to TWRP
All current official firmwares for TB8504F:
TB_8504F_S110006_181015_YZ Boots but no wifi or bluetooth
TB_8504F_S140008_190215_UK Boots but no wifi or bluetooth
TB_8504F_USR_S120010_1901181601_Q12000_HFT Boots but no wifi or bluetooth
TB_8504F_USR_S130004_1902221150_Q12000_SCP Boots but no wifi or bluetooth
TB_8504F_USR_S001019_1909091114_Q12000_ROW Boots but no wifi or bluetooth
Anyone got any ideas for me?
Damn, somehow ended up with tablet bricked and now I have 900E Diagnostics connection. Trying to use a deep flash cable to get it into EDL mode but doesn't seem to work for me.
Deep flash cable didn't work.
Found a Yourtubr clip about changing the Qualcomm driver from 900E to 9008 - didn't work.
But found a video on the internet that got me out of trouble.
In the clip it says to leave the battery unplugged - that did not work for me. I needed to short the test points, plug in USB, then connect battery and it's flashing again in 9008 mode.
After flashing I had to disconnect and reconnect the battery to get it to boot normally.
Looks like I will be back where I was a day or two ago.
Interesting - when I recovered using TB_8504F_S110006_181015_YZ I now have wifi again - I'm not sure if I'm going to just leave it like this or play around further.
RobinGill said:
Interesting - when I recovered using TB_8504F_S110006_181015_YZ I now have wifi again - I'm not sure if I'm going to just leave it like this or play around further.
Click to expand...
Click to collapse
can you post download link? I have the same problem with wifi
thanks
I have just found TB_8504F_S110006_181015_YZ, will be a day or two for me to upload and send you the link.
Here is the link - it will be active for one week, then I will take it down as I have limited storage.
3.24 GB folder on MEGA
145 files
mega.nz
thanks! I´ll try it later
RobinGill said:
Here is the link - it will be active for one week, then I will take it down as I have limited storage.
3.24 GB folder on MEGA
145 files
mega.nz
Click to expand...
Click to collapse
brother can you please re-upload it.
RobinGill said:
Here is the link - it will be active for one week, then I will take it down as I have limited storage.
3.24 GB folder on MEGA
145 files
mega.nz
Click to expand...
Click to collapse
bro pls can you upadated the link pls
3.24 GB folder on MEGA
145 files
mega.nz