Hi guys,
First, English isn't my first language so, sorry if it hurts your eyes :/
Second, I'm new to TWRP / root etc... (since yesterday) and I don't fully understand the exact meening of all words like flash / rom etc...
So: I'm actually blocked in the "Your device can't be checked for corruption. Please lock the bootloader". Apparently it's a normal screen now, when we boot we always see this. OK ( at least that's what I read)
My volume keys aren't doing anything and I can't access my phone anymore.
I can access TWRP if I want.
Thx for responding :good:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
coremania said:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
Click to expand...
Click to collapse
How can I know if ADB recognize my phone?
I can access TWRP so I don't need to flash it again ? Is there a difference between just flash TWRP and flash TWRP with fastboot ?
Sry, my bad, i miss read that you can access twrp, sry, I thought you can't, what happens if you flash a rom, which twrp is installed, what were your steps that you end stuck on bootloader message ?
Edit: if your issue is that you don't know how to start flashing, read the Los thread and follow the op.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
Download all files from the thread and put them on to your microsdcard, if your twrp is up to date you don't have to do this again. Flash the zip files in the order of the instructions, just press install at twrp and choose the zips, you can add multiple and flash them together.
Man, trust me, I'm not a lazy man and all I want is to have my phone back even if it's stock
I don't understand what you're trying to make me do, sincerely
If you can give me a link where I can have a guide steps by steps or make this guide for me that would be the best thing of my day...
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
I really don't know your issue, except you seem not to read enough. What guide you want ? How I flash a custom rom to my phone ? How to use twrp ?Why you unlocked your bootloader ? How did you manage to have the stock recovery back ?
I have to guess what you want and what you already did . If you need a guide, here are severals in the guide section.
https://forum.xda-developers.com/axon-7/how-to
TheGreatNarchy said:
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
Click to expand...
Click to collapse
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
JTruj1ll0923 said:
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
Click to expand...
Click to collapse
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Choose an username... said:
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Click to expand...
Click to collapse
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
JTruj1ll0923 said:
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
Click to expand...
Click to collapse
The thing is, after you flash the universal bootloader, the TWRP on the sd gets replaced. but the TWRP that you are using is loaded in RAM. So even if you install a TWRP version you'll stay in the version you flashed before until you reboot. If you install the universal bootloader and then install the TWRP img you'll keep everything as-is on the next reboot. I discourage rebooting without a system especially on a G because any interruption might lock the phone in DFU. On an a2017U that wouldn't be a problem because the phone boots into edl if any software error is present
Related
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Brilliant! Thank you so much! Do you know any custom ROM what is better than the factory ROM?
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Adreno306™ said:
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Click to expand...
Click to collapse
Do you think it's easier/possible to adapt a ROM from a similar device like say, the Alcatel
Pop 2 (5) Premium ? I don't know if there's any ROM for that phone tho, but since it's branded as Alcatel you might get more support from the community here than by using Vodafone's name.
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Adreno306™ said:
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Click to expand...
Click to collapse
Hey, Andreno306
I don't know much about Rom's in that level of expertise I'm afraid :/ but I did some digging and came across this simple tutorial on XDA:
http://forum.xda-developers.com/showthread.php?t=2387941
I imagine it does not work for every single device out there, at least not with modifying stuff after, but it might be a good starting point I think, in fact I would try to actually make one myself had I a working PC currently at home. But even if I did I had no way of testing it because this is currently my daily driver phone.
Just wanted to say that I'm also very interested in getting a slim ROM for this device. I can't offer any expertise I'm afraid! Just wanted to show that there are people interested in your project.
:highfive:
Stock Kernel
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
vojta_horanek said:
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
Click to expand...
Click to collapse
I have one
https://mega.nz/#!tMJD3B4T!f6m2ELYCVupqGCcN2aGbkrNzEqijLu7au-7usEfeVL0
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Demonlord6 said:
I have one
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Click to expand...
Click to collapse
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
vojta_horanek said:
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
Click to expand...
Click to collapse
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Demonlord6 said:
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Click to expand...
Click to collapse
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
vojta_horanek said:
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
Click to expand...
Click to collapse
Yeap, that's not the same version as my ROM, mine is not 130FNN etc. Maybe that's why it didn't work
Enviado do meu GT-S5280 através de Tapatalk
Sorry for the stupid question but... does it works on Smart Prime 7 too?
Has anyone installed that linked ROM? It seems to be what we are looking for... a slim debloated rom.
I presume we need to be rooted, install this TWRP, then flash that ROM?
It mentions unlocking the bootloader, I dont think I've seen any info anywhere about unlocking the bootloader.
Can anyone give a quick lowdown on all the steps required to install that ROM please?
Hi everyone, I discovered that Elephone Trunk and Smart Prime 6 have (almost) identical specs: https://www.devicespecifications.com...ison/c584481c6
So it would be great to "port" (or build ?) the official Nougat-OmniROM for Trunk to VF-895N: http://dl.omnirom.org/trunk/
Last but not least, here's official Vodafone Smart Prime 6 sources: Vodafone_Smart_prime_6_20150413.tar.xz
TWRP for vodafone smart max 4 990N (coolpad 8890u).
I tried this recovery image for vodafone smart max 4 990N (coolpad 8890u).
The phone is in a bootloop state. I think i have usb debugging enabled already.
So, in fastboot mode i can see the device in my pc in adb fastboot cmd.
Im trying to ''fastboot boot recovery.img" but it stops in ''booting..''.
Dont know whats the problem but for sure i can not find a specific twrp image for this device.
If i enter fastboot oem device-info it says ''(bootloader) Device unlocked: true''.
Any ideas ?
hi i was wondering if you could share how you did this or if you can make one for the Vodafone smart n9 (VFD720) it would help a lot of people out looking for this
Needed to root a Vodafone Smart Prime 6 (VF 895N) (got it from a friend because it became unresponsive from all the updated google play stuff ) to get linux-deploy running. Just wanted to leave a big thank you here for Adreno306 for his TRWP 3.0.0-0. it did the job very well!
Only the procedure to get it installed differed quite a bit for me, since Flashify is no longer available.
I wanted to preserve boot and just flash trwp to recover, what worked quite well.
The first thing I did was to boot the phone manually in recovery mode (Power+Vol up) and reset it to factory settings from there. It takes a little while. Then follow the setup, go to phone settings, enable developer mode and set usb debugging. If "unlock oem" is not available there, reboot into recovery again, set unlock there and reboot into bootloader.
The prerequisites are adb and fastboot, both must work. Means adb devices and fastboot devices must show the phone. What can make problems under win10 as it sometimes does not detect the phone in bootloader mode. An actual google usb driver is needed, as provided by google.
For me adb worked well, but when rebooted into bootloader with adb reboot bootloader, fastboot didnt detect the phone. With the phone still connected, the windows device manager showed an unknown device with and exclamation mark (!). Right click, install driver, select driver manually, select driver from device list, mark all devices (first entry) and click "disk", then point to the usb driver director and select "ADB fastboot driver". ( A more comprehensive description is available here )
Once adb and fastboot detect the device, it is time to prepare it. Boot to system (normal operation) first. Make sure that the TRWP 3.0.0-0.img is renamed to trwp.img and then
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot boot trwp.img
Now the phone should show the trwp menu, set it up to root the phone and install SuperSU. Reboot into bootloader and
fastboot flash recovery trwp.img
fastboot reboot
Verify with adb reboot recovery, you should see trwp now. Reboot to system.
Now finally go into the app selector, start SuperSU, and root the phone. SuperSu uses trwp recovery mode to install its image and root is done.
Again, big thanks for providing the TRWP image!
Adreno306™ said:
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Click to expand...
Click to collapse
Hi, I would like to try your tutorial but I can't root this phone (which is an important step in the tutorial), is there any way someone could help me??
Thanks
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload
MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!
Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Baron Zemo said:
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Click to expand...
Click to collapse
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
levone1 said:
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
Click to expand...
Click to collapse
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Baron Zemo said:
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Click to expand...
Click to collapse
Yes, flash 118 fw. If you want to save data, back it up first.
levone1 said:
Yes, flash 118 fw. If you want to save data, back it up first.
Click to expand...
Click to collapse
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Baron Zemo said:
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Click to expand...
Click to collapse
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
levone1 said:
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
Click to expand...
Click to collapse
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Baron Zemo said:
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Click to expand...
Click to collapse
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
levone1 said:
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
Click to expand...
Click to collapse
There's why it's so odd to me. Not the 1st time i'm doing this too. I would have waited even longer if it was stuck, but it was looping continuously back to the start.
I suspect could simply be a hardware fault developed. Anyway, i've given up. Probably best excuse to get a new phone
Many thanks for trying to help :good:
I haven't been able to get mine to reboot to recovery either, so i just boot recovery.img from fastboot anytime I want to mod. Kinda annoying but I haven't figured a way around it.
Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
SweetyVolty said:
Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
Click to expand...
Click to collapse
The questions you need to answer:
Is your bootloader unlocked?
Do you have a custom recovery installed?
Is your storage encryped?
What's your actual rom?
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Please give EXACT file names of the files you're trying to flash!
Is your bootloader unlocked? Yes, although I locked then unlocked again for trying.
Do you have a custom recovery installed? yes, I tried both
Is your storage encryped? probably no, I wiped everything but before it wasn't necessary to enter a unlock code or fingerprint etc.
What's your actual rom? It was on oreo, now I don't have a rom lol
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Installing from Ota wasn't successful, sideload does not work, installing custom recoveries result in qualcomm boot (black screen with white led)
only twrp working is this untouched twrp but it has not able to flash the new pie.. https://twrp.me/oneplus/oneplus5.html
twrp from the clockworkmod not able to boot.
My intent is to flash new pie and root. I can't able to flash the pie's original beta recovery too. https://oxygenos.oneplus.net.s3.amazonaws.com/recovery.img
Also I can't mount vendor too I don't know if this causes the problem or not....
SweetyVolty said:
Also I can't mount vendor too I don't know if this causes the problem or not....
Click to expand...
Click to collapse
Ok, so it seems you have an old Oreo stock oos rom before without vendor partition and trying to flash an pie rom and pie recovery, but still on Oreo firmware that's not possible cause newer recoveries need pie firmware which comes along with oos pie roms and you're missing the vendor partition which comes with 5.1.4.
Your starting point is the same as mentioned here https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656/post79251968
OOS 5.1.4 then you have a vendor partition, then you can install one of those stock Pie oos roms.
You can install oos 5.1.4 with stock recovery or with siankatabg's or with this one
https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Then you just need to follow the instructions for the stock oos or beta rom.
If you have any concerns or further questions, please feel free to ask here