Accidentally deleted stock firmware, help please. - Huawei GX8

Hi there,
I have a Huawei Rio L02, Australian Vodafone version.
I wanted to root my phone so I could use the gyroscope feature.
I was following a guide and managed to unlock the bootloader and install TWRP and SuperSU ok, upon trying to install cyanogenmod I got error 7 and it said to wipe the system which i did and still got error 7. (I did not realise at this time the stock firmware needed to be updated to marshmallow before installation) so I wiped the files again and didn't realise until it was too late I had system checked. Now I can access TWRP, but I can not figure out how to install any firmware on the device.
- I have tried multiple stock firmwares
- I have tried the forced update and fastbootloader methods
- I have tried manually installing the files using TWRP
I had a backup file, but unfortunately did not back it up to my pc before wiping my system, stupid and a noob mistake I know.
If anyone has a Nandroid backup of the stock system that would be fantastic (If you can use a same model, but different devices backup)
Any Ideas? Is there an old version of cyanogenmod i could install without any O.S. on the device and would this allow me to update to the newer cyanogenmod?
Would really appreciate any assistance.
Thank you

Easiest way IMO would be to download stock firmware, put it on sdcard in dload folder.
Turn off the phone. Press and hold Vol_ & Vol+, press power button. Huawei firmware update will start. You'll have stock firmawer without root and twrp.
That's why I always keep, stock firmware on sd card in dload folder so can quickly flash stock firmware if something goes wrong

Related

Cannot access recovery after attempted TWRP update, noob to HTC Devices

I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
the0f said:
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Click to expand...
Click to collapse
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
efrant said:
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
Click to expand...
Click to collapse
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
the0f said:
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
Click to expand...
Click to collapse
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
efrant said:
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
Click to expand...
Click to collapse
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
the0f said:
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
Click to expand...
Click to collapse
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
efrant said:
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
Click to expand...
Click to collapse
Thank you again sir, I'll give that a try this evening when I get back home. The help and the hand holding is very much appreciated. I thought that I knew a fair bit about android phones and custom ROMs from my time with my old Samsung devices, and have had to do a lot of learning when it's come to the One M9. Never had a device with the S-ON feature before and have had a lot of trouble trying to find info on what I need to do. I did find that forum post you linked, but wasn't sure if that applied to my device or not. Again VERY much appreciated.
Yup, 6.0 stock is installed and working, TWRP 3.0.0-2 installed and working as well. This time took a system backup and stored it in a safe place (as I expect much the same trouble when Android N or any other major update happens). Thank you again for all of your assistance in getting my phone fixed and updated.

D851 Marshmallow root and install fulmics 5.1(5.2,5.3)

Hello everyone.
I am newbie here.
I own t-mobiles lg g3 and updraded to marshmallow as the ota updates became available. But due to certain reasons, i wanted to install custom rom. The primary hurdle was rooting the device. Through trial and error method i have now successfully installed the fulmics 5.3.
I want to share my experience in this regard.
Device : d851 ( t-mobile lg g3)
Software veesion : 6.0 official marshmallow.
Root :-
Through mobile's browser, google for kingsroot. Download and install. ( donot reboot as this is temporary root, one the cell is rebooted the device will regain its previous status).
download twrp.image for d851 and save in sd card.
Now download flashify from play store and open the app. It will give three options. Select the first option ( browse image file or some thing like this) and select the twrp file you have recently downloaded. The flash will b completed in few seconds.
Congratulations, you have installed twrp.
Download a copy of custom rom ( fulmics 5.1 recommended) and save in sd card.
Now reboot the device in recovery mood ( either by turning off the cell, and then pressing simultaneously volume down+ power button, as the lg logo appears, release the power key and again press it. You will see two options, select the YES twice.
In recovery mode, first select wipe, advance wipe, system and then slide to wipe. Once done, go back and install the custom rom. After the successful installation, dont select the reboot option. Instead go back and again select wipe, factory reset.
congratulations, rom has been installed.
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
Enjoy the new custom rom.
Thanx.
Sorry for poor presentation and, offcourse, my weak english.
Man! Thanks for this! I have been looking everywhere for a way to do this and you are all the help I needed! Thank you!!!
If i may ask you, where can we get the modem and which one do you recommend? I have tried this and always i get the imei, baseband and number unknown
Enviado desde mi LG-D851 mediante Tapatalk
imrock666 said:
If i may ask you, where can we get the modem and which one do you recommend? I have tried this and always i get the imei, baseband and number unknown
Enviado desde mi LG-D851 mediante Tapatalk
Click to expand...
Click to collapse
google for this
downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/30D/LG-D85130D-Flashable.Modem.zip
Sure could have saved a lot of time if I had found this first.
I did install TWRP using a kingroot temporary root, got lost in a boot loop installing Fulmics 5.1 lost my data connection and imei information and finally downgraded back to stock Marshmallow feeling blessed to have restored my data connection. Had just finished transferring the flashable modem zip over to the SD card with an idea that I would try to move the mountain once more when I stumbled across your post which is priceless with the wealth of solutions to the problems I've had to overcome with the install. Flashify was the route to go. Lost TWRP on last flash and was just about to go through my torturous route of installing Fulmics 5.1 from scratch (root/adb/twrp/rom/bootable modem/etc.. Instead in the time it took to sign up so I could thank you for the easiest directions to this LG G3 D851 nightmare, I'm up an running on Fulmics 5.1 with full data connection. Your method eliminated a lot of the problems introduced by going the other route. Also you highlighted the main things. The factory reset is crucial and with the tricky temp root of Kingroot, it's easy to get stuck. Same with SuperSU flash/WRP and the modem flash. This should be a sticky on most sites related to LG G3 because it is the simplest way to go.
Jesus christ! Is this the only way to root my t-mobile D851? Seems like this is a dangerous way to live! Lol. But Really...
thank you, i will try it could you please give me fulmatic 5.3 room link for (d851)
Thanks for sharing
I am a newbie and do not have much experience with rooting or installing flash. But I followed your instruction and installed the fulmics.. I am struggling to flash the modem file. Can you please provide step by step instruction to do that pls. I am using flashify app
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
I am no expert either, but I believe you need to flash it in TWRP. Boot in to TWRP recovery and flash the modem zip. TWRP recovery-> Install-> modem zip-> reboot when finished
KingoRoot just seems shady to me, I wouldn't touch it personally. Here's what I did (just yesterday), from Stock MM Unrooted:
Downgrade back to original factory stock image: http://www.androidexplained.com/downgrade-lg-g3/
Root (used PurpleDrake "manual" method as auto script didn't work): http://lgg3root.com/lg-g3-root/how-to-root-lg-g3/
Once rooted, install SuperSU & TWRP Manager from Play Store
From TWRP Manager install latest version of TWRP
Boot into TRWP and do a factory reset/clear cache; flash ROM (Blisspop for me, but same general steps should apply for any ROM) and Gapps from TWRP; factory reset/clear cache again for good measure
Edit: Data works with 20B modem.
How to prevent apps from being unistalled in stock rom? In other roms u can lock the package installer .
In stock simply u just hold and drag the app to unistall button . installation of an app can be locked but unistallation cant be locked . is there anyone to solve the issue . sorry for bad english
i flashed another kernel and it is not that good... is it possible to find the kernel and just flash it ? without reflashing the rom?
KingRoot is not working for me, says Root Failed, somebody know why? What can i do?
Shady282 said:
i flashed another kernel and it is not that good... is it possible to find the kernel and just flash it ? without reflashing the rom?
Click to expand...
Click to collapse
You should be able to get the stock kernel back by "dirty flashing":
-boot into recovery (twrp)
-flash ROM *without* wiping anything.
Not to lecture, but this can all be prevented by following this simply advice:
-ALWAYS take a backup before flashing anything/customizing this or that.
-ALWAYS double and triple check that the ROM/Kernel/Whatever you're flashing is for your SPECIFIC MODEL and CARRIER.
Happy modding
Semi Fahid said:
Hello everyone.
I am newbie here.
I own t-mobiles lg g3 and updraded to marshmallow as the ota updates became available. But due to certain reasons, i wanted to install custom rom. The primary hurdle was rooting the device. Through trial and error method i have now successfully installed the fulmics 5.3.
I want to share my experience in this regard.
Device : d851 ( t-mobile lg g3)
Software veesion : 6.0 official marshmallow.
Root :-
Through mobile's browser, google for kingsroot. Download and install. ( donot reboot as this is temporary root, one the cell is rebooted the device will regain its previous status).
download twrp.image for d851 and save in sd card.
Now download flashify from play store and open the app. It will give three options. Select the first option ( browse image file or some thing like this) and select the twrp file you have recently downloaded. The flash will b completed in few seconds.
Congratulations, you have installed twrp.
Download a copy of custom rom ( fulmics 5.1 recommended) and save in sd card.
Now reboot the device in recovery mood ( either by turning off the cell, and then pressing simultaneously volume down+ power button, as the lg logo appears, release the power key and again press it. You will see two options, select the YES twice.
In recovery mode, first select wipe, advance wipe, system and then slide to wipe. Once done, go back and install the custom rom. After the successful installation, dont select the reboot option. Instead go back and again select wipe, factory reset.
congratulations, rom has been installed.
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
Enjoy the new custom rom.
Thanx.
Sorry for poor presentation and, offcourse, my weak english.
Click to expand...
Click to collapse
I did this but got stuck on the LG logo boot screen. What am I doing wrong?

Rolling Taiwan HTC 10 back to stock

Hello All
I am the textbook Long-Time-Lurker First-Time-Poster. I apologise for some very clueless questions, but I am largely self-taught when it comes to ROM flashing etc on Android.
I have a Taiwan HTC 10 (currently with software version 1.55.709.5). I have flashed TWRP recovery and SuperSU Free 2.72. I have backed up the System and the Sytem Image (two separate backups) on to my external sdCard (I think I should have done that prior to flashing the SuperSU - my bad I guess).
I now want to revert back to stock recovery so I can recieve the new 1.80.709.1 update and so I know how to do this in the future. Because I have the Taiwan version there is no RUU for me to be able to easily flash back to stock, so I think I have to flash both the TWRP Backup and the Stock Recovery for 1.55.709.5 from the Stock Collection page. I assume that I would do it in this order:
1. Flash the TWRP Backup first using the standard method in TWRP and perform the standard TWRP wipes. I assume that I should also let the phone do a full system reboot before going to the next step.
2. Then I would flash the Stock Recovery - but I am not totally sure how to do this. Is there a method to do it using TWRP itself or should I do it from fastboot using the command "fastboot flash recovery 1.55.709.5_rec.img"? Is there something else I will have to do after that (e.g. wiping caches) and, if so, how do I do that?
Am I correct in my thinking?
To explain my cluelessness I have come from using Galaxy devices for the past few years where I just wanted to get away from TouchWiz as fast as possible - so I have never reverted a device back to stock. I also have used ClockworkMod as my recovery (because it was what I learnt with my Nexus One back in the day).
I thank you in advance for your help, and if you need me to post other information about my phone, please remember I may be tardy in replying due to timezones - I am in New Zealand.
Restore your stock system image and boot if you made one before modifying sytem. If not grab the one in the stock thread for your phone. Then boot to download mode and flash stock recovery with fastboot. Reboot to system and take ota
Sent from my HTC 10 using XDA-Developers mobile app
No need to wipe anything.
Just restore System img (already SU? Then Download one from the other Thread here on xda) and you can also restore recovery in TWRP simply Switch to img files instead of zip at the bottom of installing files.
All in one go, Reboot system take OTA and fastboot Flash twrp again.
If you Flash Systemless SU in the future you can still take OTAs
Thank you both for your help. I have been able to restore back to stock pretty much following your suggestions. For others who may be in the situation as I here are the steps I went through:
1. I "system image" backed up my setup - just in case.
2. using TWRP, I flashed the stock image for current software (1.55.709.15) from the [STOCK] Guides and Stock Backups/Recovery/OTA/RUU thread.
3. I had to do the standard three wipes in TWRP to get it back to stock as well - this was the only way that I could get rid of the SuperSU app and I had to go through the first-time-starting setup again. This made me confident that I was back to a pure stock installation.
4. I booted into download mode and used fastboot to flash the stock recovery for 1.55.709.15 (from the same thread as above).
5. Restarted the system and from there downloaded and installed the update - and after 10-15 minutes it successfully rebooted and gave me the message that it had worked.
Thanks again.
hi
are u htc cidnum HTC__621 ?
now can u OTA update ?
because my htc10 rom ver 1.55.709.1 .
now i cant ota update.
htcppadol said:
are u htc cidnum HTC__621 ?
now can u OTA update ?
because my htc10 rom ver 1.55.709.1 .
now i cant ota update.
Click to expand...
Click to collapse
Yes that is my CID, and yes I have updated. Did you change your recovery or system? Because that is what I did, and the process I describe above is how I got it back to stock so I could get the latest OTA update.
Hello,
I've a Taiwanese HTC 10 converted to USA (CID and MID) and flashed with official Nougat RUU. It's working quite good however I wanted to return it to default Taiwanese version and I couldn't.
What I had done:
1) Flashed latest version of TWRP
2) I changed CID and MID to default settings
3) I restored the backup of Taiwanese version downloaded from a thread here using TWRP.
4) I restored original recovery downloaded from a thread here
Following these steps my phone was unable to boot again and a boot loop occurred. To fix the phone I changed CID and MID to USA and thankfully the RUU restored my device to a working state.
I think I'm missing some procedure in TWRP. I only restored a backup using TWRP. It took about a minute or less to complete "successfully".
Do I need to do an extra procedure? Apparently the phone never recognized the Taiwanese version as in download mode the device shown the version of USA ROM even with the backup restored using TWRP.
I'm s-off (Sunshine) with bootloader locked. I think this shouldn't affect as TWRP installed properly and I'm s-off.
Thank you.
markthirteen said:
Thank you both for your help. I have been able to restore back to stock pretty much following your suggestions. For others who may be in the situation as I here are the steps I went through:
1. I "system image" backed up my setup - just in case.
2. using TWRP, I flashed the stock image for current software (1.55.709.15) from the [STOCK] Guides and Stock Backups/Recovery/OTA/RUU thread.
3. I had to do the standard three wipes in TWRP to get it back to stock as well - this was the only way that I could get rid of the SuperSU app and I had to go through the first-time-starting setup again. This made me confident that I was back to a pure stock installation.
4. I booted into download mode and used fastboot to flash the stock recovery for 1.55.709.15 (from the same thread as above).
5. Restarted the system and from there downloaded and installed the update - and after 10-15 minutes it successfully rebooted and gave me the message that it had worked.
Thanks again.
Click to expand...
Click to collapse

G8 Stuck in twrp loop

This is the first time I've ever done this, but I just hated the UI on the Huawei G8 (laggy) and decided to try the xda way. PS: knowing that it's easier to help someone when they tell all the details, I am going to post all of it. So sorry for the long post.
First thing I did was try to update to unofficial marshmallow downloaded from here. But it didn't work saying installation failed ... Did some research and found out the device OS is from Iran (I'm from the middle east), so probably the reason why it didn't allow me to install an EU update.
What I did then was unlock bootloader by getting the unlock code from emui website. And then unlocking it from the adb terminal (adb.exe)
Then I loaded TWRP and did a backup.
I forgot to copy SuperSu to the SD card, and when TWRP asked me to root I accepted. So it got stuck on the Huawei logo while booting.
I then did a recovery from TWRP which worked perfectly
I should've just downloaded a new rom and flashed that , but I was like maybe it might allow me to install that update now the phone is unlocked so I tried installing it from the updater ->local update. And that's when the looping into recovery happened.
So I tried to do another recovery from my backup , but again it loaded into TWRP . Which I don't understand since I guess it should load the backed up System. Or is there something telling the device to reload the update from the SD card causing it to crash again ?
UPDATE: I went into file manager and renamed the dload folder to dloadxxx but that didnt help. Then I downloaded the latest TWRP and flashed that, and recovered the backed up system and THAT worked . The restore took longer than with the older TWRP . I have no clue why it worked like this. But maybe this can help someone in the future.
Thanks
Had the same thing. Exept that this happend during OTA update ....
Get a stock ROM of your choice (tested with xxxB130xxx).
Use update extractor to extract boot.img, system.img recovery.img
Wipe all partitions (except external SD Card) with TWRP. Select remove data and confirm. (you said you have backup). This allows a clean install.
Bring phone into fastboot mode (Vol down + power)
Flash bootlader with fastboot
Make Reset
Flash recovery and system
After reboot phone should start up normal.
Let me know if you got stuck somewhere.
Chilli
Edit: Root cause for the problem seems that Hauwei needs stock recovery for some update actions. -> When ever you want to make OTA or dload update flash back to stock recovery before (better flash completely to stock ).
vlatkozelka said:
This is the first time I've ever done this, but I just hated the UI on the Huawei G8 (laggy) and decided to try the xda way. PS: knowing that it's easier to help someone when they tell all the details, I am going to post all of it. So sorry for the long post.
First thing I did was try to update to unofficial marshmallow downloaded from here. But it didn't work saying installation failed ... Did some research and found out the device OS is from Iran (I'm from the middle east), so probably the reason why it didn't allow me to install an EU update.
What I did then was unlock bootloader by getting the unlock code from emui website. And then unlocking it from the adb terminal (adb.exe)
Then I loaded TWRP and did a backup.
I forgot to copy SuperSu to the SD card, and when TWRP asked me to root I accepted. So it got stuck on the Huawei logo while booting.
I then did a recovery from TWRP which worked perfectly
I should've just downloaded a new rom and flashed that , but I was like maybe it might allow me to install that update now the phone is unlocked so I tried installing it from the updater ->local update. And that's when the looping into recovery happened.
So I tried to do another recovery from my backup , but again it loaded into TWRP . Which I don't understand since I guess it should load the backed up System. Or is there something telling the device to reload the update from the SD card causing it to crash again ?
UPDATE: I went into file manager and renamed the dload folder to dloadxxx but that didnt help. Then I downloaded the latest TWRP and flashed that, and recovered the backed up system and THAT worked . The restore took longer than with the older TWRP . I have no clue why it worked like this. But maybe this can help someone in the future.
Thanks
Click to expand...
Click to collapse
h t t ps://mega.nz/#!P04D2S5Y!Yn2CL5wLC8ISb5AcNR9MTxzhAq3yVH3weG60go5zQCA download this archive, change twrp inside it with the lastest one that surdu_pertu provide.
go twrp wipe all things there
than
using adb "fastboot flash recovery stock.img"
after the first boot phone gonna think a new firmware is being installed just skip it and power off the phone
this will give you a nice start for flashing the Marshmallow from the begining.
Hello Demage,
I would be looking forward to having an Marshmallow image (if it supports my basebands). But Mega says the key is invalid. Can you double check?
Chilli
Thankfully, I managed to fix it.
1- Download Marshmallow G8 stock ROM.
2- Download Huawei update extractor, then extract recovery.img using the previous tool from the stock ROM Update.app file.
3- Go to the bootloader, then flash the extracted recovery.img into recovery.
4- Reboot by the command fastboot reboot.
5- You will get the default loading screen saying the device is reset, then you will be directed to the system welcome screen.
6- You can flash TWRP again, then superSU.

Anyone successfully rooted SM-A520W?

Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
Format data with the FORMAT DATA button first in TWRP then immediately flash Magisk (preferred) or latest Supersu.
Reboot.
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
Just wondering how you flashed TWRP (which version) and how? I'm having the same issue trying to get root on this phone and will probably just flash a custom
jermzii said:
Just wondering how you flashed TWRP (which version) and how? I'm having the same issue trying to get root on this phone and will probably just flash a custom
Click to expand...
Click to collapse
I have done it! Had the same problem and yes i have the Canadian a520w. I had to use Odin and then install superuser
Step one: Is to download Odin on pc mac or linux.
Step two: download superuser on your phone then move the file from your phone to
you computer.
Step three: open Odin and select the superuser zip file and it should say pass.
Step four: install root checker off Google play
This is not a full tutorial on how to install it but all you need to search is how to use Odin.
I got it!!
jermzii said:
I got it!!
Click to expand...
Click to collapse
Glad you got it to work did you use my method?
ashyx said:
Format data with the FORMAT DATA button first in TWRP then immediately flash Magisk (preferred) or latest Supersu.
Reboot.
Click to expand...
Click to collapse
Can you please provide a link to an appropriate TWRP version for SM-A520W?
Many thanks!
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
SlickSneeker said:
I have done it! Had the same problem and yes i have the Canadian a520w. I had to use Odin and then install superuser
Step one: Is to download Odin on pc mac or linux.
Step two: download superuser on your phone then move the file from your phone to
you computer.
Step three: open Odin and select the superuser zip file and it should say pass.
Step four: install root checker off Google play
This is not a full tutorial on how to install it but all you need to search is how to use Odin.
Click to expand...
Click to collapse
Please excuse my being a layman in this matter. I tried tot flash superuser.zip using ODIN but ODIN does not even see zip files (it only recognizes some other formats like .tar, .img etc). Could you please give a little more details on how you flashed superuser.zip using ODIN?
Thanks a lot in advance.
jermzii said:
I got it!!
Click to expand...
Click to collapse
Hi jermzii,
I apologize for my questions - I am not very experienced in all these. I would like to ask you a few questions:
Where did you get an appropriate TWRP version for SM-A520W?
Also, ODIN, does not "see" zip files. How did you flash the supersu.zip using ODIN?
Many thanks for your help in advance.
I just bought a Canadian A520W with with stock Nougat (Telus firmware A520WVLS2BRD2). I tried to root it using CF autoroot and TWRP and I had the exact experience as the OP dan.tjones. There is no TWRP specifically for A520W. After trying several versions I found one which is successfully flashed with ODIN (TWRP 3.2.1.0 for A520F). TWRP appears to install Magisk (latest version 16) successfully but it shows no root or su binary. TWRP also appears to install SuperSU zip (there is a specific version for A520W nougat) successfully, but when I open SuperSU app, it says the SU binary is occupied. Google shows two "fixes" ((1) clean uninstall using an option within SuperSU, then reinstall, and (2) uninstall SuperSU + install an earlier version of SuperSU then updating the binary (hangs). Both fixes do not work. Someone mention wiping DATA in TWRP would fix the problem, but it did not work for me.
The major problem seems to be KNOX keep saying "failed verification". At one point it was so screwed up that it just boot-loop / hang and the only thing that work was download mode. I install TWRP again and it sticks. Then I wiped everything (cache/ Dalvik, data, system, internal storage). I probably could try to flash the stock nougat firmware using ODIN, but it was still downloading (snail speed free download).
Since there is no more OS in the phone, I manage to install a 6.0.1 pre-rooted custom ROM using TWRP (I originally intended to downgrade from 7 to 6.0.1 anyway because of reports of poor battery life), and installation was successfully, giving me root. BTW I originally tried to downgrade from stock nougat to stock marshmellow using ODIN, but it does not work ("failed" message).
The TWRP version that I flashed with ODIN:
TWRP 3.2.1.0 for A520F ("recovery_a5y17lte-080318.img.tar")
https://androidfilehost.com/?fid=890129502657588962
The 6.0.1 custom ROM I installed with TWRP:
AXES ROM v.1 (they did say it is compatible with A520W)
https://forum.xda-developers.com/samsung-a-series-2017/development/rom-t3606231
I did not find any nougat custom ROM suitable for A520W. I am happy that I can find a rooted ROM and it does not matter to me whether it is marshmellow or nougat.
slim_thumb said:
I just bought a Canadian A520W with with stock Nougat (Telus firmware A520WVLS2BRD2). I tried to root it using CF autoroot and TWRP and I had the exact experience as the OP dan.tjones. There is no TWRP specifically for A520W. After trying several versions I found one which is successfully flashed with ODIN (TWRP 3.2.1.0 for A520F). TWRP appears to install Magisk (latest version 16) successfully but it shows no root or su binary. TWRP also appears to install SuperSU zip (there is a specific version for A520W nougat) successfully, but when I open SuperSU app, it says the SU binary is occupied. Google shows two "fixes" ((1) clean uninstall using an option within SuperSU, then reinstall, and (2) uninstall SuperSU + install an earlier version of SuperSU then updating the binary (hangs). Both fixes do not work. Someone mention wiping DATA in TWRP would fix the problem, but it did not work for me.
The major problem seems to be KNOX keep saying "failed verification". At one point it was so screwed up that it just boot-loop / hang and the only thing that work was download mode. I install TWRP again and it sticks. Then I wiped everything (cache/ Dalvik, data, system, internal storage). I probably could try to flash the stock nougat firmware using ODIN, but it was still downloading (snail speed free download).
Since there is no more OS in the phone, I manage to install a 6.0.1 pre-rooted custom ROM using TWRP (I originally intended to downgrade from 7 to 6.0.1 anyway because of reports of poor battery life), and installation was successfully, giving me root. BTW I originally tried to downgrade from stock nougat to stock marshmellow using ODIN, but it does not work ("failed" message).
The TWRP version that I flashed with ODIN:
TWRP 3.2.1.0 for A520F ("recovery_a5y17lte-080318.img.tar")
https://androidfilehost.com/?fid=890129502657588962
Before flashing custom ROM (in zip format), I use TWRP to wipe everything on the phone (cache / Dalvik, data, system, internal storage).
The 6.0.1 custom ROM I installed with TWRP:
AXES ROM v.1 (they did say it is compatible with A520W)
https://forum.xda-developers.com/samsung-a-series-2017/development/rom-t3606231
I did not find any nougat custom ROM suitable for A520W. I am happy that I can find a rooted ROM and it does not matter to me whether it is marshmellow or nougat.
Click to expand...
Click to collapse
You have rooted the device successfully the first time when you flashed magisk.Just root manager app was not installed.
If you have screwed up your device, do a clean flash of OS...then flash twrp and after flashing magisk the binary would be flashed but the app would
not be installed.To do that extract the app from the magisk zip that you flashed.It must be in common folder inside the zip.
Dont flash binaries on top of binaries.
Hope it helps
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
hey...im novice at this as well but I did get my a520w rooted with su on oreo with twrp...I flashed the latest su on twrp....twrp was hard to get on but there is somewhere that shows how...good luck
A Very Possible and Precise Solution
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
Hey Sir!
Soooooo I've been messing around with this all night and I figured it out somehow after nearly frying my new A5 (2017) lol
I'd recommend that you follow the directions as best you can and as fully to help you not have to redo all your software settings and stuff like I did haha. I think if all this is done in this order you shouldn't have to lose your data. I can't guarantee anything but figured I could share what worked for me. BONUS: I actually don't have an unlocked phone and I'm still locked to my carrier actually! So I don't think all these warnings are necessarily valid. Anyhow, hope it helps. :laugh:
NOTE: I'm not allowed to post website links here for some reason haha so sorry for the inconvenience! All the sites began with the https colon double slash btw! So MAKE SURE to add that to the addresses below (links are in italics)!
FIRST: Completely backup phone using Android Studio as can be found at Tech Republic website /article/how-to-create-a-full-backup-of-your-android-device-without-root/ . Also I'd recommend you do a Smart Switch full backup. Smart Switch will work to some extent and I personally restored from there pretty intact as I didn't have the Android Studio backup option before my phone got wrecked by the Verification error after I attempted to flash SuperSU onto the phone using TWRP.
1. BEFORE ANYTHING ELSE: Enable Developer Mode (by tapping on the Build Number several times), Turn OEM unlock on, enable USB debugging, and make sure all the "factory reset block" is off (or Allow factory reset option is on) and encrypted data features are off, I unlocked any Notes and disabled Secure Folder and Knox and Samsung Pass
2. Turn phone off
3. Boot phone into Custom OS install mode by holding Power+Volume Up+Home
4. I downloaded a TWRP installer file from tx5.androidfilehost.com/dl/TLLV1I5jSqS9Zg68RNh1hA/1538776061/890129502657588962/recovery_a5y17lte-080318.img.tar
5. Download the Odin software to flash TWRP onto your device, I got mine from drive.google.com/file/d/0B-2yp-J_x0LPaGJrSUlUcHE1a2s/view
6. Used Odin 3.1 to flash TWRP onto Recovery using the AP function, also turned Auto Reboot and F.Restart off (unchecked boxes)
7. Downloaded (newest file that's a zip) such as no-verity-opt-encrypt-6.0.zip from build.nethunter.com/android-tools/no-verity-opt-encrypt/ and put it on the SD card in the phone
8. Turned phone off and booted it into Recovery Mode by holding Power+Volume Down+Home
9. Used TWRP recovery to flash the no-verity-opt-encrypt-6.0.zip which sort of disables all the security things on Samsung (such as Health and Pass and Auto Updates) that would block your work, and this actually lets you reboot your phone instead of getting the Verification Integrity Check failed error and having to reset your phone every time.
10. After rebooting my phone, everything was running fine. I then downloaded SuperSU file SR5-SuperSU-v2.82-SR5-20171001224502.zip from download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
11. Used TWRP in Recovery Mode to flash SuperSU onto phone from SD card and hit Reboot. Slight boot loop was visible and then the phone restarted normally with SuperSU installed and full root access. Thanks be to God.
Again, I can't guarantee this will work BUT it is the first walkthrough that I know of on the web. Hope it helps at all!
Edit:
Originally gave up on this, but recently managed to flash TWRP.
Now in Verification Error on boot, and trying to flash the no-verity to get around that.
Success (almost rooted, but shouldn't be much harder)
Just flashed a custom OS using Odin_3.12.3, twrp-3.2.3-1-a5y17lte.img.tar, lineage-14.1-20181117-nightly-a5y17lte-signed.zip, and open_gapps-arm64-7.1-pico-20181204.zip.
With help from this discussion, the LineageOS wiki "Install LineageOS on a5y17lte", r/LineageOS "Heimdall Failed to send data" (a post by noahajac was very helpful. You'll find it soon after OP), and the Odin install guide.
Some problems I encountered was that heimdall isn't favoured for this, and that if you try to wipe your partition through TWRP and it says it couldn't mount /data, you need to format the partition before wiping it.
Edit: so upon using the phone for a bit, it became evident that the SIM card was not being detected. From what I've read so far, this is because the phone had Android Oreo and the LineageOS was for Nougat. So I will have to restore and then revert to a Nougat version of Android and try again from there...
Not gonna be finished tonight. As long as I can get the restore and cell service working...
Two Questions re: rooting the SM-A520W
1. How can I make a proper Nandroid Backup. Everytime I go into TWRP the /data partition is unavailable. Yes I formated it and flashed no-verity-opt-encrypt-6.0.zip but it still is Zero bytes.
2. After rooting, the Fingerprint scanner becomes non operational and the lock screen password/pin does not work (keeps asking for the same password/pin over and over even though they are correct.)
Thanks for the Help.
ethan_hines said:
1. How can I make a proper Nandroid Backup. Everytime I go into TWRP the /data partition is unavailable. Yes I formated it and flashed no-verity-opt-encrypt-6.0.zip but it still is Zero bytes.
2. After rooting, the Fingerprint scanner becomes non operational and the lock screen password/pin does not work (keeps asking for the same password/pin over and over even though they are correct.)
Thanks for the Help.
Click to expand...
Click to collapse
Which firmware are you running.
ashyx said:
Which firmware are you running.
Click to expand...
Click to collapse
I'm on Stock 8.0
I managed to fix problem 1 by flashing a modded Version of TWRP (3.2.3-TwrpBuilder) I am rooted with Magisk and now have access to the /data partition and can make a proper Nandroid Backup.
Problem 2 Is still there I seem to remember I have to replace Samsung Pass and Samsung Account, but I don't know where they are located I think I am supposed to create a directory in /prv-app I don't remember
I have that phone. I installed a custom recovery and used super SU.
SonicFan66 said:
I have that phone. I installed a custom recovery and used super SU.
Click to expand...
Click to collapse
I didn't want Super SU because it can't be hidden from apps that disable if root is detected esp. Snapchat
@ethan_hines did you figure it out? I am looking to do what you did.

Categories

Resources