Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...-unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
MrKnight230 said:
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
Click to expand...
Click to collapse
No problem mate, Community is Here to help!
The matter is, ROMs built after 18/8/2016 requires that you upgrade to Marshmallow stock ROM that means EMUI 4.0.
then you can flash the custom ROMs without problems.
If you're on bootloop, can you boot to fastboot or TWRP manually?
MrKnight230 said:
Hi,
so, I got my Honor 5x rooted and CM 13 installed a few months ago from this thread: http://forum.xda-developers.com/hon...unofficial-cyanogenmod-13-0-nightly-t3344499.
Last week or so some apps just didn't exist any more on my phone. Also I wasn't able to download any kinds of things, like apps, documents, pictures or whatever. After some time I figured out, that it was because of my SD-card being dead. When I removed it, all was fine again.
Another problem, that I got from the beginnning of having this ROM installed, I wasn't able to do updates, still don't know why exactly.
So I decided to wipe my phone and reinstall a newer version of CM in hope, that all would be fine again.
After performing backups and so on, I downloaded the latest build of CM from the official website (the one from 1st october) and GApps with ARM64, pushed it on my device and tried to install it with TWRP 3.0.2. I did a full wipe before, also deleting internal storage and System.
Error 7 occured and after some Internet research I read about this "assert" line. Figured out, that I got 2 oft them in this file and deleted the second telling something about the TB number, because it was also named in the error of TWRP.
Then pushed it on the device again and tried to install it. There was no error while installing, but after optimizing the apps, I got bootloops. Tried flashing other ROMs, including the one I got two days before, but it still got the same problem.
Also this huawei eRecovery thingy couldn't help me.
Now I don't know how to get an OS on my phone again, it would be very nice if someone could help me.
I also don't know whether there is a thread, that already deals with this topic, but I didn't know how to search for this.
If there is anything left unclear I'm very sorry, it's my first time posting, please excuse.
Thank you!
Click to expand...
Click to collapse
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
mumith3 said:
No problem mate, Community is Here to help!
The matter is, ROMs built after 18/8/2016 requires that you upgrade to Marshmallow stock ROM that means EMUI 4.0.
then you can flash the custom ROMs without problems.
If you're on bootloop, can you boot to fastboot or TWRP manually?
Click to expand...
Click to collapse
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
MrKnight230 said:
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
Click to expand...
Click to collapse
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
MrKnight230 said:
Thanks for the fast reply!
Just got a softbrick, can still enter fastboot and so on.
I already found a stock version, but didn't know how to install it 'cause it wasn't a zip... :3
Click to expand...
Click to collapse
Is it an update.app file?
Then you have to force update. Refer to @clsA 's thread.
Cheers.
clsA said:
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
Click to expand...
Click to collapse
mumith3 said:
Is it an update.app file?
Then you have to force update. Refer to @clsA 's thread.
Cheers.
Click to expand...
Click to collapse
muradulislam said:
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Got it from this page for KIW-L21: stech guide.com/honor-5x-stock-marshmallow-firmware/ (I'm not allowed to post links yet because I'm new.. You just need to delete the space, should work then)
Sadly I got the file deleted and have to download it again, but right now my Internet is slow af.. Gonna need at least 5 hours to go...
MrKnight230 said:
Got it from this page for KIW-L21: stech guide.com/honor-5x-stock-marshmallow-firmware/ (I'm not allowed to post links yet because I'm new.. You just need to delete the space, should work then)
Sadly I got the file deleted and have to download it again, but right now my Internet is slow af.. Gonna need at least 5 hours to go...
Click to expand...
Click to collapse
Well, Wait, Honor 5x has many variants. So download only your device variant
Search this thread >>> http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
Hope it helps.:highfive:
Cheers! :good:
mumith3 said:
Well, Wait, Honor 5x has many variants. So download only your device variant
Search this thread >>> http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
Hope it helps.:highfive:
Cheers! :good:
Click to expand...
Click to collapse
got the right one now, download worked faster than expected.
Is there any possibility to install the dload file without using a sd-card?
MrKnight230 said:
got the right one now, download worked faster than expected.
Is there any possibility to install the dload file without using a sd-card?
Click to expand...
Click to collapse
No mate, You'll need a SD card.!!!
mumith3 said:
No mate, You'll need a SD card.!!!
Click to expand...
Click to collapse
clsA said:
What file did you get (link) ?
theirs no need to use the HuaweiUpdateExtractor, unless you need the stock recovery from it.
all you need is Stock recovery (installed) and the Update.app for your current version
Update.app goes in a folder named dload on the sdcard, now simply shut the phone off and restart it while holding power + volup + voldown
after 5 seconds let go of the power button and continuing holding the vol buttons till you see the update begin (around 25 seconds)
Click to expand...
Click to collapse
muradulislam said:
Try to get back to stock firmware, to do that download the latest firmware, extract to get dload folder containing UPDATE.APP, use Huawei update extractor to extract recovery, Cust, boot and system images.
Flash them to your phone using fastboot, put dload folder in the root of an SD, insert it in your phone and press and hold vol up + vol down + power until the phone boots up to force an update.
Have you already tried this? If not, do this please.
If yes, please elaborate "erecovery could not help me*...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Phone works again now! I love all of you!!!
MrKnight230 said:
Phone works again now! I love all of you!!!
Click to expand...
Click to collapse
Enjoy and do come back
Just kidding...
Sent from my PLK-L01 using XDA Labs
Related
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
Somebody suggested installing Xposed Framework manually, which put me in a bootloop. Uninstall seemed to work, but then after restarting to clear the cache, the phone now constantly goes into a loop again.
I have tried installing stock firmware in a dload folder on the SDCard, but that gives me a 'software install' failed error after around 10%
Obviously my next option was to flash the stock firmware in fastboot mode, but when I extract the update.app there's no proper filenames and the Huawei Finder application doesn't seem to work with the H7 firmware.
Pretty much completely out of ideas, so any suggestions would go a long way.
Fixed it now by formatting my SD card and downloading the L01 rom from the Huawei site.
Did you get xposed to work or is it a NO GO? I really wanna try Xposed, but my guts tells me that it's not gonna work because of the EMUI..
mamboboy said:
Fixed it now by formatting my SD card and downloading the L01 rom from the Huawei site.
Click to expand...
Click to collapse
do you have a link to the L01 european rom...Thanks
kjettern said:
Did you get xposed to work or is it a NO GO? I really wanna try Xposed, but my guts tells me that it's not gonna work because of the EMUI..
Click to expand...
Click to collapse
No go unfortunately. Flashing it in TWRP puts you in an endless bootloop, I fixed it by running the uninstaller, but the phone felt laggy after that. So I went back to TWRP and cleared the cache which was when the bootloop came back. Whether that's to do with the botched Xposed installation or a bug in TWRP, I don't know!
sheridan2000 said:
do you have a link to the L01 european rom...Thanks
Click to expand...
Click to collapse
It is here:
http://www.hihonor.com/es/pages/support#?view=downloads
The top one, 'PLK-L01C432B100 Upgrade Software UK'
I didn't download it initially and was trying ones from NEEDROM (which seemingly won't work on EU phones) because it says it's for the Honor 4X in the description, but turns out that's just a typo. Worked first time using the dload/UPDATE.app and volume up + down while plugging USB cable in method
So i had a hardricked phone(i thought) but than it worked again. So i flashed pacrom and it went in a hardbrick like state again (using twrp btw)I flashed it with nano gaps and the b330 package so you could get the fingerprint scanner. Than after an hour or so it worked again. Than i started running my battery low on purpose so i knew if it was just stuck or if it was something else. When my phone dies it will reboot again and work. And then i flashed rr with the nano gapps and the b330 package and it did this again, I thought it might have something to do with the b330 package so i flashed it without and it still did this. Then i thought it might have something to do with my twrp because i was still running on version 3.0.0 so i flashed the newer version through fastboot and it did this again!!
I dont know what is going on but my phone is acting really strange.
Does someone know of this problem or has ever heard of it or is my phone just strange?
jimandroidnerd said:
So i had a hardricked phone(i thought) but than it worked again. So i flashed pacrom and it went in a hardbrick like state again (using twrp btw)I flashed it with nano gaps and the b330 package so you could get the fingerprint scanner. Than after an hour or so it worked again. Than i started running my battery low on purpose so i knew if it was just stuck or if it was something else. When my phone dies it will reboot again and work. And then i flashed rr with the nano gapps and the b330 package and it did this again, I thought it might have something to do with the b330 package so i flashed it without and it still did this. Then i thought it might have something to do with my twrp because i was still running on version 3.0.0 so i flashed the newer version through fastboot and it did this again!!
I dont know what is going on but my phone is acting really strange.
Does someone know of this problem or has ever heard of it or is my phone just strange?
Click to expand...
Click to collapse
I have no idea why you keep flashing the firmware b330 it only needs done one time
clsA said:
I have no idea why you keep flashing the firmware b330 it only needs done one time
Click to expand...
Click to collapse
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
jimandroidnerd said:
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
Click to expand...
Click to collapse
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
jimandroidnerd said:
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
Click to expand...
Click to collapse
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
clsA said:
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
Click to expand...
Click to collapse
Demian3112 said:
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
Click to expand...
Click to collapse
I will do that. thanks for the help everyone
clsA said:
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
Click to expand...
Click to collapse
Demian3112 said:
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
Click to expand...
Click to collapse
Ok so i have gone back to stock, everything is working again as far as i can tell. Just done it 10 minutes ago. I will test for a week to see if erverything is working properly. Is it safe to flash custom roms / recovery after i have confirmed everything is working properly? Thank you guys so much for the help btw, i really appreciate it!:good:
jimandroidnerd said:
Ok so i have gone back to stock, everything is working again as far as i can tell. Just done it 10 minutes ago. I will test for a week to see if erverything is working properly. Is it safe to flash custom roms / recovery after i have confirmed everything is working properly? Thank you guys so much for the help btw, i really appreciate it!:good:
Click to expand...
Click to collapse
did you take all the updates to b330 ? if so you can pretty safely go to CM13 + gapps nano without any worries.
use one of the newest versions of TWRP
Do a factory reset and flash only CM13 and gapps
reboot let it fully load .. reboot to recovery / backup your fresh install to ext-sd
boot back to the OS and setup your new device.
Hello,
I had the same problem as the guy on the thread http://forum.xda-developers.com/honor-7/help/bricked-formated-honor-7-rom-t3480339 but when following the help steps, I encountered a problem.
When installing the update, it always gets stuck at 5%. I have tried using just ""RECOVERY.img" and "BOOT.img" as well as inculding "SYSTEM.img" and "CUST.img".
I think the problem might be that I downloaded the wrong software seeing as all I know about the device model is that it is PLK-L01 and I live in the UK.
Can anyone help me please?
2002hon said:
Hello,
I had the same problem as the guy on the thread http://forum.xda-developers.com/honor-7/help/bricked-formated-honor-7-rom-t3480339 but when following the help steps, I encountered a problem.
When installing the update, it always gets stuck at 5%. I have tried using just ""RECOVERY.img" and "BOOT.img" as well as inculding "SYSTEM.img" and "CUST.img".
I think the problem might be that I downloaded the wrong software seeing as all I know about the device model is that it is PLK-L01 and I live in the UK.
Can anyone help me please?
Click to expand...
Click to collapse
Download the latest firmware for your phone, should be B380, Extract it to get UPDATE.APP.
Use Huawei update extractor to extract stock recovery, Cust, system and boot images and flash them using fastboot.
And then see if the system boots up in android.
If it does not, copy the UPDATE.APP to a folder named dload in your SD card and press power + vol up + vol down until your phone boots. Let go of power but keep other two pressed for five, six sec more.
If the forced update gets stuck ( at 5% or any other), wait around 20 minutes for it to resolve itself. If that does not happen, do the power + vol up + vol down combo again.
If the problem is not solved after 3,4 tries, please report back.
Hope this is detailed, if you need information, please specify the step which is problematic.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
2002hon said:
Hello,
I had the same problem as the guy on the thread http://forum.xda-developers.com/honor-7/help/bricked-formated-honor-7-rom-t3480339 but when following the help steps, I encountered a problem.
When installing the update, it always gets stuck at 5%. I have tried using just ""RECOVERY.img" and "BOOT.img" as well as inculding "SYSTEM.img" and "CUST.img".
I think the problem might be that I downloaded the wrong software seeing as all I know about the device model is that it is PLK-L01 and I live in the UK.
Can anyone help me please?
Click to expand...
Click to collapse
Another way to solve is to restore your twrp backup, after it is successfully restored, don't boot to Android, just enter fastboot mode and flash the boot and system files of the Android version that twrp backup was using.
muradulislam said:
Download the latest firmware for your phone, should be B380, Extract it to get UPDATE.APP.
Use Huawei update extractor to extract stock recovery, Cust, system and boot images and flash them using fastboot.
And then see if the system boots up in android.
If it does not, copy the UPDATE.APP to a folder named dload in your SD card and press power + vol up + vol down until your phone boots. Let go of power but keep other two pressed for five, six sec more.
If the forced update gets stuck ( at 5% or any other), wait around 20 minutes for it to resolve itself. If that does not happen, do the power + vol up + vol down combo again.
If the problem is not solved after 3,4 tries, please report back.
Hope this is detailed, if you need information, please specify the step which is problematic.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Another way to solve is to restore your twrp backup, after it is successfully restored, don't boot to Android, just enter fastboot mode and flash the boot and system files of the Android version that twrp backup was using.
Click to expand...
Click to collapse
dude thank you so much you're a lifesaver!
2002hon said:
dude thank you so much you're a lifesaver!
Click to expand...
Click to collapse
Sometimes it feels really good to be appreciated
Thanks.
The first method was the exact same thing I said in the other thread but anyways, which one you used? First or second? Is your phone working now. Just making sure
muradulislam said:
Sometimes it feels really good to be appreciated
Thanks.
The first method was the exact same thing I said in the other thread but anyways, which one you used? First or second? Is your phone working now. Just making sure
Click to expand...
Click to collapse
yes it is working, the problem was I told it to update after flashing the CUST etc when all I had to do was boot it up. I cannot thank you enough if you ever need anything just ask I owe u one :victory::good:
2002hon said:
yes it is working, the problem was I told it to update after flashing the CUST etc when all I had to do was boot it up. I cannot thank you enough if you ever need anything just ask I owe u one :victory::good:
Click to expand...
Click to collapse
Thanks buddy... You already contributed by pressing the like button to the post which helped you. Just do this to all the posts in future (to the ones which are actually helpful and to all the contributors) as it helps us a lot.
Enjoy your phone and always keep tinkering with your phone but keep a working twrp backup before doing anything.
Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error