So when i was rooting my phone by using patching the boot.img but after flashing the img it ended up in a bootloop . I tried again and the result is the same.
Please help
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
I think i already did that when trying to unbrick my phone. Sorry, im new to rooting . Does factory resetting my phone helps?
A Factory Reset wipes all user-data included installed 3-rd-party apps, resets all system apps to their initially installed version, it does NOT bring back phone's bootloader to its original state.
jwoegerbauer said:
A Factory Reset wipes all user-data included installed 3-rd-party apps, resets all system apps to their initially installed version, it does NOT bring back phone's bootloader to its original state.
Click to expand...
Click to collapse
So you mean that i have to flash the stock boot.img even though i flashed it already to unbrick my phone?
Might be helpful.
jwoegerbauer said:
Might be helpful.
Click to expand...
Click to collapse
Alright , i'll update if i need help
jwoegerbauer said:
Might be helpful.
Click to expand...
Click to collapse
Update : i tried re-flashing stock rom and flashing the patched one. The result is the same. Ends in a bootloop.
I checked magisk if my device have ramdisk and i do, so i know I'm doing the right thing but ends up in a bootloop
jwoegerbauer said:
Might be helpful.
Click to expand...
Click to collapse
Someone told me that i have to downgrade to miui 10.2.5 and the fact that my phone is a newer model that came out on August (Redmi 10 / Redmi 10 prime) . How am i going to find the img file for that version
Remember I told you
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
and I have nothing to change.
FYI: I no longer participate this thread.
Related
I tried to get rid of root by going into the supersu app and clicking the uninstall option. It then rebooted, but it went into a bootloop. I already wiped multiple times but nothing happened.
Could it be because of xposed being installed?
Thanks.
Was stock recovery used to perform the factory reset?
audit13 said:
Was stock recovery used to perform the factory reset?
Click to expand...
Click to collapse
No, I used TWRP to do it. v2.8.7.0 I think.
Try with stock recovery.
audit13 said:
Try with stock recovery.
Click to expand...
Click to collapse
How would I uninstall TWRP recovery?
Flash the recovery.img file that is included with the stock rom. Fastboot flash recovery recovery.img.
audit13 said:
Flash the recovery.img file that is included with the stock rom. Fastboot flash recovery recovery.img.
Click to expand...
Click to collapse
Hmm, still boot loops. Am I forced to just reflash the fctory image?
Since it still bootloops, I recommend flashing back to a completely stock ROM to make sure the phone still functions properly.
audit13 said:
Since it still bootloops, I recommend flashing back to a completely stock ROM to make sure the phone still functions properly.
Click to expand...
Click to collapse
Dang. I wish I wouldn't have to wipe my files, but there aren't That many important stuff. Thanks.
audit13 said:
Since it still bootloops, I recommend flashing back to a completely stock ROM to make sure the phone still functions properly.
Click to expand...
Click to collapse
Sorry for this, but could you also help me install nonsystemless root? systemless causes trouble with layers so it would be very nice if you could help.
Thanks
Which rom is on the phone? For stock LP, flash supersu from twrp. Many custom mm ROMs are prerooted.
audit13 said:
Which rom is on the phone? For stock LP, flash supersu from twrp. Many custom mm ROMs are prerooted.
Click to expand...
Click to collapse
Wait the nonsystemless root is gotten by just flashing it? I always thought it was the other way.
Thanks so so so much for your help!
it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.
Hi. I have an Indian variant Motorola turbo. I am on a custom ROM(forgot the name acually) and thougt everything was working till my phone rebooted suddenly and went into recovery mode. Since then I have been trying to resurrect the phone but failing. Could someone here can help me to resurrect my phone back? I would reward you for your help..
Note : Tried all possible ways to get my phone back but its staying only in bootloader No matter what i do.
Update August 2020 : While taking out my things, I found my moto maxx, and after looking at it i wanted to give a try once again. If someone can help in bringing my mobile back to life. Attacing the images of the logs on the screen. Only bootloader is seen always. Please help me. I can pay more to someone who could help me.
was this on a fresh install? was this working for like a week or longer and then **** the bed? is it charged fully? can you reinstall the ROM fresh and have it boot? might have to brush up on mfastboot commands and getting access to push files to the memory so you can flash the ROM again.......
Did you somehow get your bootloader from unlocked state to relocked?
linuxsociety said:
Did you somehow get your bootloader from unlocked state to relocked?
Click to expand...
Click to collapse
Dont know. How to check it when in fastboot mode? Any command?
Is the issue resolved?If not I can help you
gauthamkithu said:
Is the issue resolved?If not I can help you
Click to expand...
Click to collapse
If you could help me, I will be really happy
krishna13 said:
If you could help me, I will be really happy
Click to expand...
Click to collapse
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
gauthamkithu said:
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
Click to expand...
Click to collapse
Thanks for your reply bro. I will DM my number or you DM yours. I will give you a call and will explain things.
gauthamkithu said:
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
Click to expand...
Click to collapse
Bro. I have messaged you my number. Please text your number too so that I could explain the issue clearly. But If you dont want to help me out, just say me so that I could find other way for help. Its been more than 5 days since i sent a message to you but i have not received any response from you.
gauthamkithu said:
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
Click to expand...
Click to collapse
Can someone tell me what is the name of the script file(2nd point) , where can I find in the firmware package and what lines should I need to edit?
I have seen a few people still in need of the stock boot.img 11.2.2.2. for t-mobile Oneplus 9 (LE2117) So I have attached it for those in need!
Here is the stock boot.img for 11.2.3.3 Oneplus 9 T-Mobile
Jg1234 said:
I have seen a few people still in need of the stock boot.img 11.2.2.2. for t-mobile Oneplus 9 (LE2117) So I have attached it for those in need!
Click to expand...
Click to collapse
Alright so I've been sitting on this file for a few days. Willl I be able to flash this to my LE2117 on 11.2.2.2 and relock bootloader and be back to stock? Or will my system still be corrupt if I relock? G just wait for a non pro msm tool?
hiryupd said:
Alright so I've been sitting on this file for a few days. Willl I be able to flash this to my LE2117 on 11.2.2.2 and relock bootloader and be back to stock? Or will my system still be corrupt if I relock? G just wait for a non pro msm tool?
Click to expand...
Click to collapse
I'm not sure how you went about rooting it originally, but if you have only flashed boot.img and nothing else. Then yes that is how I would go about doing it on my phone, if I was wanting to go back to locked bootloader. I don't see any issue with doing that after you install the stock boot.img.
Jg1234 said:
I'm not sure how you went about rooting it originally, but if you have only flashed boot.img and nothing else. Then yes that is how I would go about doing it on my phone, if I was wanting to go back to locked bootloader. I don't see any issue with doing that after you install the stock boot.img.
Click to expand...
Click to collapse
So I took magisk and downloaded the global OP and took boot.img from that magisk patched it and installed it then unlocked so I had the backup of THAT boot, not the Tmo one.
hiryupd said:
So I took magisk and downloaded the global OP and took boot.img from that magisk patched it and installed it then unlocked so I had the backup of THAT boot, not the Tmo one.
Click to expand...
Click to collapse
Yes That sucks but we all learn from are mistakes.. Fastboot Flash this stock boot.img and then either lock bootloader or if you want to have root? have magisk patch same stock boot.img and reinstall.
P.s. I also have been able to update over ota by just restoring stock boot.img in magisk.
Incase you wanted to keep rolling out with root. If you need help.i will try to make a step by step way I did it.
Jg1234 said:
Yes That sucks but we all learn from are mistakes.. Fastboot Flash this stock boot.img and then either lock bootloader or if you want to have root? have magisk patch same stock boot.img and reinstall.
P.s. I also have been able to update over ota by just restoring stock boot.img in magisk.
Incase you wanted to keep rolling out with root. If you need help.i will try to make a step by step way I did it.
Click to expand...
Click to collapse
Went ahead and reflashed that boot.img. Worked fine. Now I can relock with no other steps at this point correct?
Correct.
Thank you my friend. This is most helpful. I was reluctant to root without a good way to return to stock for updates.
Jg1234 said:
I have seen a few people still in need of the stock boot.img 11.2.2.2. for t-mobile Oneplus 9 (LE2117) So I have attached it for those in need!
Click to expand...
Click to collapse
safetynet api error ？ How to do？
Magisk 22.1 has a safety net error. Download this app and it will show it passes. Also widevine is L1 https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
Jg1234 said:
Magisk 22.1 has a safety net error. Download this app and it will show it passes. Also widevine is L1 https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
Click to expand...
Click to collapse
Thank you! But I broke the system. Now that the update downloads more than half of the time, an error will occur. Do you have a backup of the system firmware or all system images？
This is maybe a stupid question but how do I flash this stock.img using Magisk?
iSkyJIE said:
Thank you! But I broke the system. Now that the update downloads more than half of the time, an error will occur. Do you have a backup of the system firmware or all system images？
Click to expand...
Click to collapse
I don't.. I would try factory reset or at least clear cache a few times consecutively. Sounds like there is a cache causing a issue with update.
inspron said:
This is maybe a stupid question but how do I flash this stock.img using Magisk?
Click to expand...
Click to collapse
Well you would fastboot the stock boot.img. but if you have never tampered with your original? And wanted root? you would have magisk patch the stock boot.img and then fastboot your.img. if you search how to root with boot.img you will find how to do it with the files above
Jg1234 said:
I don't.. I would try factory reset or at least clear cache a few times consecutively. Sounds like there is a cache causing a issue with update.
Click to expand...
Click to collapse
I have tried to clear the cache and format, but the update is still halfway through the download and an error occurs
iSkyJIE said:
I have tried to clear the cache and format, but the update is still halfway through the download and an error occurs
Click to expand...
Click to collapse
I know it sounds stupid but check Google play updates. Since you reset the phone. Just a thought have heard it cause issue with ota . Sorry Bud!
Jg1234 said:
I know it sounds stupid but check Google play updates. Since you reset the phone. Just a thought have heard it cause issue with ota . Sorry Bud!
Click to expand...
Click to collapse
Thank you. Convert TMO to Global, EU, or other variant I flashed my phone to the international version based on this article, and then updated it to EU 11.2.3.3, everything worked normally
iSkyJIE said:
Thank you. Convert TMO to Global, EU, or other variant I flashed my phone to the international version based on this article, and then updated it to EU 11.2.3.3, everything worked normally
Click to expand...
Click to collapse
Would you be able to share which file did you use to convert to global? I just got my unlock bootloader token from oneplus right now.
infamousvincci said:
Would you be able to share which file did you use to convert to global? I just got my unlock bootloader token from oneplus right now.
Click to expand...
Click to collapse
In the top thread, you can download the global and European firmware Rom. you only need to replace your own modem file
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
Click to expand...
Click to collapse
There is no TWRP for this device. To get back to stock and re-lock your bootloader you can try Android Flash Tool or Pixel Flasher.
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock?
Click to expand...
Click to collapse
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Did you erase the GrapheneOS Android Verified Boot key before you went back to stock?
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
At the bottom of the articel is described how to erase the key.
WoKoschekk said:
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Click to expand...
Click to collapse
I starts to boot, then it goes to white Google screen and stays there until I force it to reboot.
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
LankiCat said:
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
Click to expand...
Click to collapse
It's described on that page. Just do what the say and all is fine.
It's just one fastboot command. Thereis no reason to find a workaround or sth.
WoKoschekk said:
It's described on that page. Just do what the say and all is fine.
Click to expand...
Click to collapse
I really appreaciate the help, but, the page says: Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it. Since I have already flashed the factory stock image I want to be sure that will work and not cause more problems. It takes a really long time to flash stock with all the setup, updates, restore, and re-loading apps to get back where i need to be. Thanks again for you input.
LankiCat said:
Since I have already flashed the factory stock image
Click to expand...
Click to collapse
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
WoKoschekk said:
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
Click to expand...
Click to collapse
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
LankiCat said:
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
Click to expand...
Click to collapse
Then run fastboot flashing lock
WoKoschekk said:
Then run fastboot flashing lock
Click to expand...
Click to collapse
yeah, tried that too. I'm going to have to wait until this weekend when I can afford some downtime on my phone.