Hello,
I was rooted my device with magisk, after I have install Android 10 OTA the root deleted!
I'm used to flash the patched boot img from this thread and my device now won't open and it stopped on the android one screen :crying:
What can I do to solve this problem!
He doesn't even say which version it is. You should only flash the patched boot of the ROM version you have installed. E.g. V10.0.17.0 or V11.0.5.0. Check your ROM build number in phone details and search for a patched boot that matches that version.
Or patch the boot yourself, it's not that difficult.
People should learn how to patch boot themselves so they're sure about the version, instead of relying on other people. Too many errors happen, resulting in lots of bootloops.
---------- Post added at 09:33 AM ---------- Previous post was at 09:29 AM ----------
Sorry, forgot to add a word on a possible solution.
Please try to get to fastboot or EDL and flash stock ROM again, then root and patch again with correct version.
Related
Hello,
Yesterday I was trying to root my phone and install a newer Rom. Rooting my phone was no problem (I used the KingUser Desktop app), but after that my phone restarted and kept loading the Huawei Logo...
I desperately tried to use this guide: http://forum.xda-developers.com/ascend-p7/help/huawei-p7-bootloop-t2904049 And followed the steps of the user "Wekii", but it didn't work at all...
I got to step 13, but then when "android system recovery 3e" tries to verify the file it gets stuck.
I used this Rom: http://www.carbontesla.com/2014/09/...t-firmware-ascend-p7-l10-v100r001c00b133sp01/
Can somebody point me in the right direction?
Kind regards,
Hi,
Firmware/emui version before root?
Firmware/emui Version you have flashed after root?
I have the same problem. I was on this ROM:
http://forum.xda-developers.com/ascend-p7/development/rom-myrom-v1-0-emui-2-3-4-4-2-b135-t2948887
I wanted to go to stock, so I downloaded an official UPDATE.app and flashed stock recovery.img and boot.img.
I downloaded Sophia-L10_V100R001C00B621_Firmware_West European Region_Others_Android 4.4.2_EMUI 3.0_05012HCE.zip from http://consumer.huawei.com/nl/support/downloads/
I flashed stock 621 boot.img and recovery.img.
Now it is in a bootloop. I can't enter recovery or fastboot. All I see is the Huawei logo boot loop, no matter what I do.
You have to go back via transition pack. Then it works fine
I formatted the SD card, copied the transitional UPDATE.APP from the official site, yet it's still doing the same. Just the logo, nothing else. I started it while holding all three buttons.
After trying to force load the transitional package, now the phone boots up with the logo, but at least it isn't rebooting. It does turn off by itself after some time. I tried to update the second package and the logo just stays on indefinitely.
You have to follow the rollback instructions. Dont easy flash the pack.
This instructions are right. Think that in your versions.
View attachment 3492003
I'm sorry, but I cannot follow the instructions as they tell me to do this through the phone menu. Unfortunately I no longer have a phone menu since I cannot boot up my phone. I thought the alternative would be to try force update with both volume buttons and power.
---------- Post added at 10:12 PM ---------- Previous post was at 09:45 PM ----------
Okay, I managed to get into fastboot & rescue mode. White screen. I will see what I can do from here.
---------- Post added at 10:57 PM ---------- Previous post was at 10:12 PM ----------
I couldn't get any update.app to be installed. I flashed My-RoM v1.2 / EMUI 2.3 again. (http://forum.xda-developers.com/ascend-p7/development/rom-myrom-v1-0-emui-2-3-4-4-2-b135-t2948887)
It is functional, but I don't know how to go back. I am on EMUI 2.3, but I think I need a stock recovery/boot.img and UPDATE.APP. But which one will work?
I don't care which version I will be on. I just want to be on stock.
Looking for an answer I have not been able to find as to recovering a used N6.
What I have is a used N6, with TWRP 6.8.7.1 (newest version I believe) no recovery files and does not appear to have a working system on it. The bootloader has been relocked (won't allow unlocking or reflashing of stock firmware). What I am guessing is some one unlocked it, modified it, and relocked it then somehow messed up and wiped the system ... Guessing.
It has the older 71.10 bootloader on it now, not sure if it updated beyond 5.11 or not.
Just thinking (as I write this) would it be possible to make an image of another N6 put it on a OTG thumb drive and restore that or if possible push recovery files through Fastboot or possibly ADB in recovery?
Or am I out luck?
Any know fixes?
My recommendation would be to push files through fastboot. Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
As a note, I recently had to go through this process and the FLASH ALL file was failing to flash the system file. The answer was to manually flash each file myself (directions provided in the same post). It was fairly easy once I realized the issues with FLASH ALL.
As soon as you get android booting, go back and unlocked the bootloader. I don't get all these people locking their bootloaders... ESPECIALLY with a rom and custom recovery!
The above is almost the right advice, but IIRC it wont work with a locked bootloader.
Fortunately you have TWRP installed. Don't mess with your recovery partition until you get this sorted.
Just go download a rom, any will probably work... I would stick with an AOSP one and maybe download the 5.1.1
You may be able to just mount the phone as an MTP device, I think that may be supported by TWRP at this time? Or sideload/push.
Gimme a sec, I'll post some links
---------- Post added at 01:29 PM ---------- Previous post was at 01:14 PM ----------
As I said most roms will probably be OK, But to be specific I would just grab a 5.1.1 version of pure nexus... say the last 5.1.1 version
https://www.androidfilehost.com/?w=files&flid=34545
Download page for pure nexus (this does not include gapps)
Specifically I would download this one, as I said its the last 5.1.1 version. I say this because the bootloader should be fine with it whether its updated or not (I couldn't find a list of what bootloader is what version)
https://www.androidfilehost.com/?fid=24052804347817485
Boot to recovery, and see if your phone shows up under my computer. MTP transfer should be enabled by default in TWRP and is supported by TWRP version > 2.8
If you can't get it to show up as an MTP device, you should be able to see it with ADB while booted into TWRP. Use either the push command
http://stackoverflow.com/questions/...mand-to-push-a-file-on-device-without-sd-card (discussion on push)
push maybe to /sdcard if the directory exists.
I'd probably just use sideload though,
https://twrp.me/faq/ADBSideload.html
One of these should work
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
I'll leave it to you to find gapps for 5.1.1
I don't think you would need them though as android should still load and work fine with out them. I would simply start up the phone with the rom installed, turn on allow oem unlock, boot immediately back into bootloader and unlock the boot loader. If something happens to that recovery partition the phone is a paperweight with the bootloader locked... really not worth keeping it locked.
Once you get the bootloader unlocked, update to something current and worry about gapps then?
Thank you so much guys!! Will give this run as soon as I have a chance and update the post(may take a day or so been pretty busy at work and such)
UPDATE : @scryan Hey just want to say that did the trick, had to use a thumb drive and OTG cable to load the ROM. But was in and out with an now unlocked bootloader in under 30 minutes.
Thanks again guys!!
I have the single sim version, i unlock the bootloader and install trwp, after i boot to trwp and allow sistem read, i canot boot any more the phone enters in a bootloop, i need some help, to get it back, and install trwp and get it working.
riper2510 said:
I have the single sim version, i unlock the bootloader and install trwp, after i boot to trwp and allow sistem read, i canot boot any more the phone enters in a bootloop, i need some help, to get it back, and install trwp and get it working.
Click to expand...
Click to collapse
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
[email protected] said:
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
Click to expand...
Click to collapse
Check this thread for more information & help: Link
[email protected] said:
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
Check this thread for more information & help: Link
Click to expand...
Click to collapse
Thanks i done it yesterday what i do?
flash stock flashtool with all wipe selection.
rebuild the kernel with drm off and patched.
test the kernel
flash the kernel with fastboot
flash trwp with fastboot
form there flash the lastest version of supersu
and voila that is
[email protected] said:
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
Check this thread for more information & help: Link
Click to expand...
Click to collapse
Do you know if i can install ota ?
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.
you mean magisk not working with this build?
mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs
avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!
Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV
avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.
jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems
gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?
jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again
I am new and I don't have much experience in custom rom, recovery, kernel etc. and I think I was wrong in some procedure.
I have a problem with my Moto E5 XT1944-3, I wanted to install the TWRP by following these steps:
https://forum.xda-developers.com/moto-e5/development/recovery-twrp-3-2-3-x-moto-e5-plus-t3912189
(I have the bootloader unlocked)
The inconvenience came when I restarted in recovery mode and the touch did not work (only in recovery mode), which led me to flash again twrp-x.x.x.x.img but still the same. What I ventured on the Internet to find solutions and simplifying, I ended up flashing the recovery img as follows: fastboot flash boot twrp-x.x.x.x.img (I guess the problems started there)
*The E5 did not turn on with the logo and did not start the OS, I tried to use the Lenovo tool to restore the E5 and it says that it is not compatible (maybe because of the unlocked bootloader) although it allowed you the option to search for it within the "compatible" smartphones . I tried from the fastboot tool to try to revive the E5 but it does not start the system. Nor does he let me use: fastboot erase system / data / recovery; to try to make a clean installation.
* The last thing I try is to reinstall the TWRP and try to use the USB-OTG with the mause, but, although it has electricity, the mause does not appear and if the screen is turned off and then on again it remains blank forcing me to a forced restart.
* Oh and download an AOSPEXTENDED ROM and install the img with fastboot and it didn't load the logo but the boot animation but it was just a loop
* Any idea what to do?
* I think that if the recovery worked correctly, I could solve this.
Greetings from Argentina using the google translator :dedos cruzados:
Did you flash the correct recovery? Your phone is the Moto E5 Nora variant
---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------
And the command is like this:. fastboot flash recovery xxxxxc.bin
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dont use fastboot flash boot or you will overwrite the bootloader
loco72 said:
Dont use fastboot flash boot or you will overwrite the bootloader
Click to expand...
Click to collapse
And fastboot flash bootloader... did you forgot? And remember, NEVER EVER use fastboot erase bootloader, as it will brick your device.