Related
First and foremost all credit goes to @bender_007 for making this for me.
all i had to do is provide some files from the Sprint LS990
and he was able to create this mod "AutoRec" method to flash TWRP
Fastest Safest way to flash Custom Recovery for those on Stock Rom with Root Access ONLY.
DISCLAIMER: USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE NOR WILL I BE ABLE TO HELP YOU OUT OF A BRICK OR BOOTLOOP!
Finally what I and many of us have been waiting for!
Simple APK (AutoRec) flash TWRP (OneClick) method.
Must be on Stock Rom Lollipop and Rooted.
***ONLY FOR THE SPRINT VARIANT (LS990)***
has not been tested on any other devices.
Steps
- Download APK
- Install APK
- Open App
- Wait a few seconds while it does some backup.
- Wait for prompt to say that it is ready to flash.
- Click the button to Flash TWRP
- Wait for it to be done.
Once done Power off device and boot to racovery.
and finally... PROFIT!!!
Here is original download link from @Bender007 to him goes all credit
https://www.androidfilehost.com/?fid=95916177934553576
Please make sure to thank @bender_007 he is the original creator of "AutoRec" and he did all the hard work.
Unable to download. It says the website has moved permanently.
samuelmoya23 said:
Unable to download. It says the website has moved permanently.
Click to expand...
Click to collapse
Download link fixed in OP go ahead and give it a shot. :good:
ingoljosh said:
Download link fixed in OP go ahead and give it a shot. :good:
Click to expand...
Click to collapse
Does this unlock the bootloader or will I have to unlock it using bump?
It is bumping. It's doing everything for you.
cthedogg said:
Does this unlock the bootloader or will I have to unlock it using bump?
Click to expand...
Click to collapse
Yes bootloader bumped.
delete
If i do this method do i still have to use bump to flash a custom ROM?
No you don't. This is 1 click and you're ready. However I recommend you download the latest bumped twrp and flash it inside the current recovery. I'll add new versions soon and some more features
Sent from my LG-D855 using Tapatalk
I installed successfully, but when I rebooted out of TWRP I get "Security Error" boot loop. Any idea where I should go from here?
dashflach said:
I installed successfully, but when I rebooted out of TWRP I get "Security Error" boot loop. Any idea where I should go from here?
Click to expand...
Click to collapse
I had this problem but luckily before i flashed the twrp i downloaded a cm nightly onto my external sd card then after i flashed twrp and tried to boot the stock ROM i got the sercurity error so i went back to twrp and flashed CyanogenMod and it booted up fine..
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
purpleurkle said:
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Click to expand...
Click to collapse
So autorec downgrades the bootloader to jb ? And does it stay jb after I upgrade to 2.8.6.1 bump?
Sent from my LG-LS980 using XDA Free mobile app
Yup just rooted and installed TWRP on ZVA...got the same "Security Error" and power off. Downloading BarePapA to an SD card now, will post results once installed!
Yes it worked.
Here was what i did:
Started with a bone stock Sprint G3 running 5.0.1 ZVA
Ran the one click root for ZVA. Rooted successfully
Installed the TWRP one click APK. The phone booted into TWRP and went into download mode fine but would display "Security Error" and turn off if a regular boot was attempted.
I downloaded BarePapA V1 and threw it onto an SD card. Booted into TWRP and followed the install directions on the ROM page. Install was a success. It booted fine. Took a minute to prepare the apps as usual but everything works and i am rooted. Posting from the phone now. Great modded stock ROM by the way.
I've got the autorec also for zva. It doesn't boot because of more recent kernel. I can post it. Basically you can just flash a kernel and it will work.
EDIT:
Autorec ls990 ZVA - download
Poslano sa mog LG-D855 koristeći Tapatalk
this worked for me. But now we're on ZVB. i ended up downloading the pre-rooted from autoprime
Upload me the kernel please
Poslano sa mog LG-D855 koristeći Tapatalk
This worked for me on ZV8 with root. Thanks! I do have one question though. The boot.img of the stock kernel that was replaced and the new kernel that was installed is of a different size. The new kernel image is ~13.5 MB while the stock ZV8 kernel image is ~16.8 MB. What are the changes between the two or the origin?
On a side note, I attempted to flash a factory ZV8 boot image and the bootloader said no way. I then flashed a bumped factory ZV8 image and it worked as it should.
I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP.
TWRP was successfully flashed. So I try to boot into it using 'fastboot boot recovery.img' to boot into it.
I get the 'ERROR: Remote DTB not found' message. So booting into recovery using fastboot doesn't work.
I try booting into recovery manually (volume down + power). That doesn't work either. It freezes up at the OnePlus logo.
So, since TWRP isn't working, I flash stock recovery. That worked fine, and booted into it successfully (manually).
I boot into stock recovery and followed this guide to try updating manually using stock recovery. Of course, the update fails.
I then try flashing the full dump here. I factory reset, then flashed the full dump.
"Update successful."
Now, it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually freezes up too, just like TWRP did earlier.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I see that some other users in the OnePlus forums and in XDA are having the same problems when flashing TWRP.
I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
mechanity said:
I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP. Like a few others in the thread, I had the problem that when I try to boot manually into recovery, the screen shows the OnePlus logo with the android logo. Then the android logo disappears, and no matter how long I hold the down button while booting, the screen freezes at the OnePlus logo.
Fine, I'll just use fastboot boot recovery.img .
Nope, I get the 'ERROR: Remote DTB not found' message. Still stuck on the fastboot screen.
Great, I'll just flash stock recovery. Cool, it worked.
I booted into stock recovery and followed this guide to try updating manually using stock recovery. Of course the update fails.
Maybe I can just flash the full dump here. I factory reset, then flashed the full dump. Now it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually gives me the same results as flashing TWRP did earlier. So now, I can neither flash stock recovery nor TWRP to install any OxygenOS.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
Click to expand...
Click to collapse
When you try do go in recovery manually(volume up+power) what does it show
mohammedtabish said:
When you try do go in recovery manually(volume up+power) what does it show
Click to expand...
Click to collapse
Well, pressing volume up + power actually takes me to bootloader mode.
Volume down + power, on the other hand, shows the OnePlus logo and the Android logo for a split second. Then the android logo disappears, the OnePlus logo stays, and it freezes there.
In case my post wasn't very clear, the same thing happens even if I don't attempt to boot into recovery (as in, it does the same thing if I just press the power button to boot into the system).
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
That is exactly what I said I did in the OP. I have tried this multiple times.
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I tried the f2fs recovery from blu_spark eng.stk thread just now. I am still getting the remote: dtb not found error.
Still freezing when I boot manually into the recovery.
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's available as a .zip, which means you need a working recovery to install it.
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
[/COLOR]
mechanity said:
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
Click to expand...
Click to collapse
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
mohammedtabish said:
[/COLOR]
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
Click to expand...
Click to collapse
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's okay, thanks for your help.
mechanity said:
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
Click to expand...
Click to collapse
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
mechanity said:
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Click to expand...
Click to collapse
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
joho5 said:
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
Click to expand...
Click to collapse
Originally, I could boot to the stock recovery. However after flashing that full 2.1.3 dump that I linked to, I can't boot to system or recovery. Flashing stock recovery now gives me the same remote:dtb not found error.
i have the same problem
i can't get into adb but can get into fastboot
I had twrp installed and then i flashed cm13
A fews days later i flashed xposed using twrp and after flashing, it said that stock recovery was trying to replace twrp and asked to swipe to disable it.
i swiped it.
now when i try to boot to recovery, its stuck at mi logo
everything else working fine
just i cant boot into recovery now.
i flashed twrp again using fastboot
but still i m unable to boot to recovery.
Any help would be appreciated
Thanks in advanvce
Flash it using miflash tool.
You have tried flashing using miflash before , haven't you?
Then the procedure is the same, only this time you have to rename twrp file into recovery.img then overwrite original recovery.img in the target miflash folder. Don't forget to remove other files you don't want to be flashed to your device I.e system , data , etc , just keep .XML files or other text files .
Then after you think ready just go flash it
Good luck sir
Yokohart said:
Flash it using miflash tool.
You have tried flashing using miflash before , haven't you?
Then the procedure is the same, only this time you have to rename twrp file into recovery.img then overwrite original recovery.img in the target miflash folder. Don't forget to remove other files you don't want to be flashed to your device I.e system , data , etc , just keep .XML files or other text files .
Then after you think ready just go flash it
Good luck sir
Click to expand...
Click to collapse
Thanks for the reply
will try that
hope it works
yashthakur797 said:
Thanks for the reply
will try that
hope it works
Click to expand...
Click to collapse
You're welcome and good luck
Now I realised that there is no problem with twrp
Actually booting to recovery is taking too long
Whenever I boot to recovery, it shows the mi logo for 5-10 mins and then twrp boots up
Any idea what is the reason for it??
yashthakur797 said:
Now I realised that there is no problem with twrp
Actually booting to recovery is taking too long
Whenever I boot to recovery, it shows the mi logo for 5-10 mins and then twrp boots up
Any idea what is the reason for it??
Click to expand...
Click to collapse
Because you're still on stock firmware , maybe?
Yokohart said:
Because you're still on stock firmware , maybe?
Click to expand...
Click to collapse
i have installed the cm13 firmware
that might not be the reason
yashthakur797 said:
i have installed the cm13 firmware
that might not be the reason
Click to expand...
Click to collapse
which cm13 firmware by who?
actually if you have cm13 firmware the boot logo should change to cm13 logo.
cm13 firmware provided by thestrix
in my case i get the mi logo and then cm13 boot animation
the normal boot speed is fine
but when i boot to recovery, it takes a long time
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/honor-7/development/unsupported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
LoRikU said:
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/ho...upported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
Click to expand...
Click to collapse
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
LoRikU said:
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
Click to expand...
Click to collapse
did you tried the offical TWRP of ypur device?
venugopalu007 said:
did you tried the offical TWRP of ypur device?
Click to expand...
Click to collapse
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Grab the stock recovery file for your device. You can flash inside TWRP itself.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Koriki extract the firmware using huaweiupdateextractor
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
Koriki?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Koriki?
Click to expand...
Click to collapse
Loriki is user name of op
Sorry my keyboard auto corrected it to koriki
venugopalu007 said:
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
Click to expand...
Click to collapse
I tried that, read my second post on this thread. It didn't work, I didn't know which version I had to use. I ended up with a bootloop on various versions as mentioned in one of my first posts.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Alright, I will try this. As soon as I get back home since the wifi here sucks.
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
I planned on doing this though I don't know where I can get the firmware for my H7... Could you perhaps provide me a link? It would be very kind of you (+ The wifi here sucks, so I will try downloading firmwares when I get home)
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3Remove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Amazing! Thanks
I can confirm this worked on Android 10/Q. I can't use the canary patch method for magisk because I forgot to remove the modules before upgrading to Android 10. This method works like a charm, it removed the incompatible modules allowed me to by pass the bootloop.
Thank you so much for sharing!
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
wao20 said:
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
Click to expand...
Click to collapse
Second step should be:
fastboot boot image-new.img
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Alxoom33 said:
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No, but you have TWRP. You don't need it.
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Click to expand...
Click to collapse
Only since the update to android 10
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Tulsadiver said:
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Click to expand...
Click to collapse
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've only used fastboot.
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
sliding_billy said:
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
Click to expand...
Click to collapse
got it! thanks this time too!
FcukBloat said:
got it! thanks this time too!
Click to expand...
Click to collapse
No problem. It's good to be a pack rat. I hope it worked.
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Mega link seems to be working. Open with chrome, not mega app.
Edit: I've added a AFH download link.
i tried with chromium based browser (vivaldi) from both phone and pc and link didn't work, probably it was a WiFi problem, thanks for adding alternative link though. and your core mode image worked like a charme! and thanks again also to sliding billy for initial mirror support
Just what I needed. Thank you
How did you create it? I want to make sure I have one of these images on hand in the future when I need to fix things
Simply works, thank you!
Holy cow, thanks man. I can't believe @topjohnwu let this slide through. Without TWRP wtf are you supposed to do, reflash the whole OTA/factory image?!
EDIT: Wait, now I can boot and apparently have root but I can't access any of my rooted apps. It says "waiting for root". Magisk Manager gives me an "app not installed" error but it is installed on the device. When I click it it says "upgrade to full Magisk Manager" and does nothing. How am I supposed to delete the module folder?
EDIT: Can't access terminal, can't do anything. Permission denied via ADB as well.
EDIT: DO NOT DELETE MAGISK MANAGER OR ALTER IT IN ANY WAY WHEN USING CORE MODE. You will be stuck like me. I had to nuke my phone and reflash everything. PIA