I plan to upgrade my tf300t to cm11. But now i met some problem
my tf300t is using 4.2.1, and bootloader is ww_epad-110.6.1.27.5
first i unlock the device, then i fastboot twrp v2.6.3.0 in it(I tried several versions, twrp or recovery, but all of those couldn't read internal memory or ext sd card. only this version is ok)
then i wipe data and made it factory reset
finally i choose cm11 to install, and then it told that error flashing zip
and now when i boot the device, it won't go to the android system but go to twrp by itself
what should i do now? should i root it before i install cm11? :crying:
CWM
Jason2014 said:
I plan to upgrade my tf300t to cm11. But now i met some problem
my tf300t is using 4.2.1, and bootloader is ww_epad-110.6.1.27.5
first i unlock the device, then i fastboot twrp v2.6.3.0 in it(I tried several versions, twrp or recovery, but all of those couldn't read internal memory or ext sd card. only this version is ok)
then i wipe data and made it factory reset
finally i choose cm11 to install, and then it told that error flashing zip
and now when i boot the device, it won't go to the android system but go to twrp by itself
what should i do now? should i root it before i install cm11? :crying:
Click to expand...
Click to collapse
How did you do a factory reset??? From twrp??
---------- Post added at 02:44 AM ---------- Previous post was at 02:34 AM ----------
I think I see whats going on here.. I need a little more info... So you cant mount anything from twrp... and it just boot into twrp every time??? Can you get to your bootloader screen?? Can your PC see your devices in fastboot... What is the OS of you PC
ok now
lj50036 said:
How did you do a factory reset??? From twrp??
---------- Post added at 02:44 AM ---------- Previous post was at 02:34 AM ----------
I think I see whats going on here.. I need a little more info... So you cant mount anything from twrp... and it just boot into twrp every time??? Can you get to your bootloader screen?? Can your PC see your devices in fastboot... What is the OS of you PC
Click to expand...
Click to collapse
thank you.
it's ok when change a new recovery:good:
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!
Honor 8 - FRD-L09
So, i was on Nougat,
I unlocked my device, then tried rooting. I did factory reset through TWRP (3.0.2), and it bricked.
I tried unbricking through fastboot flash (Boot, Cust, Recovery, System), the 'Cust' never flashed properly, always gives 'partition error'
Tried flashing Nougat, MM, tried custom ROMs, tried eRecovery (fails after 5%).
Now it doesnt seem to pass the initial 'Your device has been unlocked .... Your device is booting now...'
I realized there is TWRP (3.1.1), so I flashed it, tried flashing custom ROMs, but to no avail.
Hisuite doens't work for Honor 8.
I can boot into recovery, fastboot.
Am I right to assume that the device is done.
I went to Huawei, and they won't help me, even if I am willing to pay, because the device is from a different country (bought it used, so I didn't know it was from dubai)
Can you go to TWRP?
If you are able to use dload method to restore or able to get into twrp by any chance?
you properly mounted every partition you want to flash in twrp settings?
Take this twrp ist 3.1.1-1
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------
And flash openkirins linageos
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
Hi guys, I just rebooted my phone after restoring apps and opening some etc after a clean install and it hangs on the bootloader warning screen and then goes to fastboot.
No clue why as it rebooted fine earlier. This happened once before while encrypted and I'm currently decrypted.
Latest OB with just some basic magisk mods which didn't cause an issue on my previous reboot.
Didn't want to start another post, so I'd figured it's better to post here. I'm soft bricked to, I'm stuck on bootloader. After about a thousand different solutions, system managed to boot and I even booted in TWRP, flashed Magisk, and TWRP listed me booted on partition b, the I tried booting part a, and now I'm stuck in a loop. I've tried the debrick tool, and the flash- all fastboot method. I ran fastboot boot twrp. img, and the system booted when I got in the last time. But now that will just hang me on the OnePlus logo.
Sent from my ONEPLUS A5010 using XDA Labs
---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------
DEVILOPS 007 said:
Hi guys, I just rebooted my phone after restoring apps and opening some etc after a clean install and it hangs on the bootloader warning screen and then goes to fastboot.
No clue why as it rebooted fine earlier. This happened once before while encrypted and I'm currently decrypted.
Latest OB with just some basic magisk mods which didn't cause an issue on my previous reboot.
Click to expand...
Click to collapse
I was at that point, and I ran fastboot boot /path/to/your/twrp.img, and system booted up, and I didn't leave well enough alone.
Issue solved and rooted now.
Sent from my ONEPLUS A5010 using XDA Labs