Related
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Omg i forgot that the bootloader might be locked.. Ill try to find the comand to put my unlock code in and get back to this thread.. Thanks so much for suggestions.. Though ive had tkbdeal with it nougat is FANTASTIC
UPDATE: So far nothing is working. Tried the rollback packages and im still on nougat. I have an actual firmware version now. But its Russian firmware? Trying the dload method with L29185 firmwares like 200 and 320 and nothing works. Tried many things and now i cannot even install twrp. The install process would work it just wouldnt do anything when i tried to boot to twrp but now when i try to flash twrp over the recovery it just completely fails. no error code it just says it cannot find a file by that name or it cannot read it. adb says the bootloader is unlocked. Am i just completely stuck here on a buggy nougat installation? Is there any way to force a twrp backup to load outside of twrp?
gm007 said:
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Click to expand...
Click to collapse
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
OcazPrime said:
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Click to expand...
Click to collapse
That twrp is for mate 9 and will not work for mate 8 you need to fastboot another twrp. You need to flash another twrp you can try the twrp for the honor 8 which will work on mate 8
http://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
You will be to get into this twrp but not all functions are working.
---------- Post added at 02:03 AM ---------- Previous post was at 01:59 AM ----------
OcazPrime said:
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
Click to expand...
Click to collapse
As long as you can get into fastboot mode, you can recover. Try to flash the nougat stock recovery then use the rollback package (try all three to see which one work) then you can dload back to your previous rom.
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Icchan said:
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Click to expand...
Click to collapse
Did you try it and it works for you? I flashed this twrp and my phone just get stuck at the screen "your phone is booting" and I have to flash another twrp.
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
OcazPrime said:
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
Click to expand...
Click to collapse
If you are back to C636B180 firmware, you need to unlock the phone, flash twrp, which is fully working in emui 4, root the phone then use SRK to change to the software region you want:
http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Can i just download a superuser zip and flash it with twrp to root? Havemt rooted this phone in forever cuz i never did much with it since my first and only rooting
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
LastStandingDroid said:
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
Click to expand...
Click to collapse
What?
The previous twrp version doesn't work on nougat due to kernel.
I guess it's selected by bootloader or the new teecd
You can download twrp as mentioned here
http://forum.xda-developers.com/showthread.php?p=70126187
Also @tknguyencsu what works in that version for your mate 8?
Does MTP work and adb?
Data won't work unless you use encrypted version.
Sent from my FRD-L09 using Tapatalk
OcazPrime said:
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
Click to expand...
Click to collapse
Budy I have same problem Pls note me when u find somethıng :=)) ıf I then ı will let u know.
TWRP Recovery 3.0.3
Download TWRP Recovery 3.0.3
http://sillanwali.com/downloads/twp-3.0.3.img
Hello friends i need some help! Today i did one big mistake! I restored from twrp an old backup of my old frd-l09 to my frd-l19.... Waa... It did not fail and now when i try to do wipes from twrp it shows me these results for every partition: failed to mount "partition" (invalid argument). It is a matter of fact that when i try to switch on the phone it goes to bootloop!Please need help... How can i do? I have not a backup of original vendor.... Can someone provide me the download for original partition that i need to restore? Please tell me i'm really displeased, i need to give the honor to a friend and in this conditions i can not!
I realized that i restored right backup... But why now i'm at this point? Please help
try this guide it
https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
also helps to restore your device
I restored by flashing from twrp original b381 full-firmware. First i flashed update.zip and after the second .zip file. After this will be installed original recovery, so then i did factory reset from original recovery and with this i fixed all partitions... Anyway thanks venugopalu for your answer. The post can be closed.
does anyone have the same process but for FRD-l14 model? US 64 gig model.
Dilan49 said:
I restored by flashing from twrp original b381 full-firmware. First i flashed update.zip and after the second .zip file. After this will be installed original recovery, so then i did factory reset from original recovery and with this i fixed all partitions... Anyway thanks venugopalu for your answer. The post can be closed.
Click to expand...
Click to collapse
glad to hear enjoy
---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------
DHSoccer4 said:
does anyone have the same process but for FRD-l14 model? US 64 gig model.
Click to expand...
Click to collapse
can you tell me what is the problem
venugopalu007 said:
glad to hear enjoy
---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------
can you tell me what is the problem
Click to expand...
Click to collapse
I ended up getting this phone the other day and decided to rush myself unlocking/rooting and flashing . Ended up to the point where I was stuck in boot loop and only able to see twrp recovery and the erecovery. Tried a factory reset / flashed a custom Rom and still got the same error. Decided to try the erecovery and that failed when updating so I tried relooking boot loader and doing he erecovery. That failed and now I am stuck there lol
DHSoccer4 said:
I ended up getting this phone the other day and decided to rush myself unlocking/rooting and flashing . Ended up to the point where I was stuck in boot loop and only able to see twrp recovery and the erecovery. Tried a factory reset / flashed a custom Rom and still got the same error. Decided to try the erecovery and that failed when updating so I tried relooking boot loader and doing he erecovery. That failed and now I am stuck there lol
Click to expand...
Click to collapse
do rollback bro
DHSoccer4 said:
I ended up getting this phone the other day and decided to rush myself unlocking/rooting and flashing . Ended up to the point where I was stuck in boot loop and only able to see twrp recovery and the erecovery. Tried a factory reset / flashed a custom Rom and still got the same error. Decided to try the erecovery and that failed when updating so I tried relooking boot loader and doing he erecovery. That failed and now I am stuck there lol
Click to expand...
Click to collapse
Try to follow the steps that i wrote . In my case flashing b381 from twrp fixed all partitions. You must to download right firmware for your model, also i advice you to download "firmware finder" in your computer for find firmwares. Pay attention to download right firmware, check if your version is branded or not!
Hello, today while trying to get back to stock i wierdly bircked my honor 8
I flashed the stock recovery and stock boot img
Then i flashed a rollback package and a marshmallow package which i used for this same thing before.
Now the phone didnt start for a solid 30 minutes and ive decided to reflash the rollback and marshmallow package, but after i flashed the rollback got stuck at the boot logo, not even the stock bootanimation showing up.
The phone doesnt reboot neither in any of the recoveries nor in bootloader.
Any help would be appreciated.
Stephen
Okay so after all of this i managed to reboot to bootloader and get my hands on one of my previous unlock codes. So now ive got an unlocked bootoader, but after fashing twrp the phone is stuck at the 'your device is booting now' when im trying to get in it
I thing you have flashed the wrong TWRP, check for the latest version or at least the one for your build
uh well, hello there again.
i've tried to do the dload method which failed(i used lots of versions tho none worked)
and i've tried flashing marshmallow twrp, which at the moment, well, it cannot mount anything. no partition can get mounted.
Does any of you guys have an idea of what i could try?
thanks in advance
Does it mean that you have access to TWRP ? if TWRP cannot mount a partition, go into mount section, tick system, data, boot, vendor and then reboot to TWRP again. Then try your previous operation. If it cannot mount data, go into wipe, advanced wipe, and click on format data, then restart TWRP and try again
seems like i somehow broke the partition table, cause it shows every storage as 0 mb and mounting isn't available, cant tick the option. Looks like i will have to find some service center to repair it by my own cost, by the end of the month. Though im giving it around the 25th so i got some more time till then, so maybe i find some solution to this problem.
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
ØG_SQUAÐ said:
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
Click to expand...
Click to collapse
You tried only once? Maybe you should now try to flash TWRP recovery and restore a backup made by TWRP. I can provide you one but for FRD-L09, not another. Another method would be to flash the rollback package and then retry flashing an EMUI 4.X ROM (dload method for both), hope you'll figure it out
I think i expressed myself wrong.
That was how i got the phone to work.
Oh lol I misunderstood because of the "it failed at 99%" and I thought the phone wasn't rebooting , no matter I'm glad you succeeded
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: http://pro-teammt.ru/firmware-database/ Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
you can enter in recovery mode true?
try rebrand your device to stock and download the stock rom to flash via HwOTA or dload.
Can boot only to stock recovery, dload and fastboot. As I said, I rebranded to C432 and did it successfully and installed ROM for this version. I tried flashing both Nougat I used to rebrand and Oreo, both crash at 5% when flashing via dload, HwOTA doesn't work as it flashes TWRP you have to boot into, and I can't enter TWRP because I get Func NO 11 and 2 (recovery image load failed!). I tried 2 different TWRPs, this one from HwOTA and Azan Mughal's version. Neither of them works. Nougat versions don't even flash properly, which is normal because I "have" Oreo
Well, I might just say that this is the toughest phone I have ever been modding. I have just noticed that plugging the phone to charger also makes it enter ERROR MODE, which is also normal in this situation as boot image fails to load.
Just thinking... Might it be that recovery and boot partitions are somehow unformatted? I have no other idea why would recovery boot fail when installed. But on the other hand if it was unformatted it would either format it properly or not install at all, right?
EDIT: Tried to erase recovery but "Command not allowed".
I've got the exact same problem except dload because I don't know how to do that.
dload works with emui 4.x
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
One click away from pushing all the files from UPDATE.APP from stock Oreo through Fastboot, is it safe enough? I mean, what if, for example, fastboot.iso fails to write or is corrupted, completely bricked phone?
Never been so scared modifying a phone, this one is so tough to mod and soft at once...
Can't boot to system, recovery, installing through dload crashes at 5%
i am in same problem plz developers do some work on these issues of this device to get back our devices thanks.
i have tried many mehods (dload, update. app, update. zip etc...... 1 different problem i got is when fladhing boot. img or recovery. img using cmd fastboot flash boot boot. img
failed remote; partition get size error.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
SevenUp9 said:
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
Click to expand...
Click to collapse
keep searchig
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
SevenUp9 said:
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
Click to expand...
Click to collapse
yes oreo.... i am still trying twrps of azan mughal and other twrp for my device but now when i install custom recovery {fastboot flash recovery_ramdisk recovery. img}
it shows ok but when i reboot device in recovery mode there is no twrp recovery....... only stock recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------
SevenUp9 said:
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
Click to expand...
Click to collapse
great bro....
plz share info here how to reflash kernal
@BaBa Yoga, I posted simple walkthrough in the first post, if you ever need explanation just ask here, I'll try to be more detailic then. Good luck unbricking your phone bro :victory:
SevenUp9 said:
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
Click to expand...
Click to collapse
bro i did not find firmware for my region i. e RNE L21 C185..... I FOUND DOME FIRMWARES on other sites one of thek i extract update. app using huawei updates extractor but there is no kernal.img file..... i found i. gs of boot, system, recovery, cust etc but no kernal. img what i do.....
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
http://pro-teammt.ru/firmware-database/?firmware_model=rne-l21c185B3 - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
SevenUp9 said:
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
[m/?firmware_model=rne-l21c185B3[/url] - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
Click to expand...
Click to collapse
should i download OTA-MF or FULLOTA-MF?
I Hope i could find kernal file now....
i am downloading FULLOTA-MF thanks to provide me firmware list of my region
thanks sevenup9 for getting back my device out of that problem i flash the kernel successfully wnd get back my twrp as well now what next..???????? thanks again
---------- Post added at 06:54 AM ---------- Previous post was at 06:01 AM ----------
i flashed kernel. img, cust. img, system. img and then reboot now i have twrp but still in bootloop what next
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
SevenUp9 said:
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
Click to expand...
Click to collapse
i did usb mathed as well but when flash update. zip via twrp error 9 shows
---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------
then usi g fastboot i flash recovery_ramdisk kernel cust system ramdisk all these images..... now reboot and i lost twrp and it replaced with stock recovery.... in stock recovery i wiped cache... done... wipe data and factory reset..... stuck at 0% after 10 minutes... plz bro
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
i didn't lock bootloader yet... i keep it still unlock
I used previous Oneplus devices like 5t and 6t. And did root and used for almost 2 years. And I loved that feel.
Recently I brought op7pro 12gb variant.
After one day, I thought to root and install Havoc OS.
So, I followed root method for op7pro. After fastboot boot <image>
I wiped all the partitions like, system, vendor, data, internal etc...,
After the reboot. I am unable to boot my phone.
Not even I can go to fastboot to install stock ROM. Anyhelp?
I made mistake by wiping system partition.
Anyhelp how to recover ?
aswathsaru said:
I made mistake by wiping system partition.
Anyhelp how to recover ?
Click to expand...
Click to collapse
Then you have to use msm tool to recover and it locks your bootloader.
---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------
https://androidfilehost.com/?fid=6006931924117884115
Download this file
Follow this thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I tried the steps. But unable to detect in the msmtool.
Tried several times
Fixed
Thanks Folks, I tried global Recovery via MSMtool but not sure why it doesnt worked.
Then Tried with European rom and then it worked.