After flashing some custom roms and playing around with the phone, and booting to the Android Recovery, I've noticed at the bottom of the window this message;
Supprted API: 3
E:Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
I flashed back Nougat to test the Recovery and there were no messages. So I'm wondering why flashing a custom rom it's messing something up?
Thanks
bump...
Does anyone know anything about this?
Thanks
Try to reflash stock firmware via EDL mode.
darkzero1125 said:
Try to reflash stock firmware via EDL mode.
Click to expand...
Click to collapse
Doing a normal flash of Stock works, if it didn't, I'm assuming I'd see this message in the recovery and I don't.
I only see this message in the recovery on custom roms, not sure if it was all of them I tested, but it seemed like it was, last I remember...
Anyone please?
I can't figure out why this is appearing in the custom roms I flash, but not Stock Oreo.
Thanks
Got same problem :/
beam2546 said:
Got same problem :/
Click to expand...
Click to collapse
I'm not sure it's the way it is when using custom roms or something screwed up...
Hmm
DoR3M3 said:
I'm not sure it's the way it is when using custom roms or something screwed up...
Hmm
Click to expand...
Click to collapse
Will install stock rom solve problem? I don't know now what should I do:crying:
beam2546 said:
Got same problem :/
Click to expand...
Click to collapse
beam2546 said:
Will install stock rom solve problem? I don't know now what should I do:crying:
Click to expand...
Click to collapse
Yes it goes away on Stock, because you are putting back the recovery...
DoR3M3 said:
Yes it goes away on Stock, because you are putting back the recovery...
Click to expand...
Click to collapse
same problem with me. did u resolved it?? could u install custom rom??
nitinlakra said:
same problem with me. did u resolved it?? could u install custom rom??
Click to expand...
Click to collapse
Look at my Signature, I moved on, oops time to unsubscribe from this post...
Cheers
Related
i updated to official gingerbread to be able to use aurora, but couldn't root it because i had done a re-partition.
then i went back to 2.2 and installed the default partition zip but the phone messed up, always got stuck at the huawei logo.
now, when i try to install a stock rom, it says update failed at the end of the installing process.
what can i do about this?
no help?
Experiences said:
no help?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=1971266. It helped me when I messed partitions on my phone. But don't forget that you'll have someone's else IMEI so you will need to change it using some of this forum's methods.
Experiences said:
i updated to official gingerbread to be able to use aurora, but couldn't root it because i had done a re-partition.
then i went back to 2.2 and installed the default partition zip but the phone messed up, always got stuck at the huawei logo.
now, when i try to install a stock rom, it says update failed at the end of the installing process.
what can i do about this?
Click to expand...
Click to collapse
Did you try to restore the stock partition and install the official rom again ?
nagato.fm said:
Try this: http://forum.xda-developers.com/showthread.php?t=1971266. It helped me when I messed partitions on my phone. But don't forget that you'll have someone's else IMEI so you will need to change it using some of this forum's methods.
Click to expand...
Click to collapse
thank you. i guess i need to download ubuntu now.
hung.ngomanh said:
Did you try to restore the stock partition and install the official rom again ?
Click to expand...
Click to collapse
i installed default partition first. i guess that's what you mean.
Hi guys, I flashed a jamal's 4.3 rom coming from omega's google edition rom and i did the usual stuff like I always have factory reset etc.. and i reboot the system and fix permissions as usual and my phone is now stuck on the omega's spinning boot up animation with the phone vibrating.
HELP!!!
Re-download the rom, could be a bad download. Did you check the md5sum?
jd1639 said:
Re-download the rom, could be a bad download. Did you check the md5sum?
Click to expand...
Click to collapse
what's a md5sum? :L i can't since my phone doesn't show up on my computer
sbouzyk said:
what's a md5sum? :L i can't since my phone doesn't show up on my computer
Click to expand...
Click to collapse
It's a long alpha-numeric number that is associated with the file. Next time you download a rom look for it on the download page. When you down load a file the md5sum should match the original indicating a good download. There are apps that check the md5 and most file managers will show it in properties
ok, but how do i get out of the bootloop
sbouzyk said:
ok, but how do i get out of the bootloop
Click to expand...
Click to collapse
If you've done the factory reset and that doesn't get you out I'm guessing the rom you flashed was a bad download. You made a nandroid backup before you flashed the rom, right. Boot back into recovery and restore it. Then re download the rom and try it again
jd1639 said:
If you've done the factory reset and that doesn't get you out I'm guessing the rom you flashed was a bad download. You made a nandroid backup before you flashed the rom, right. Boot back into recovery and restore it. Then re download the rom and try it again
Click to expand...
Click to collapse
i didn't make a nandroid backup...
sbouzyk said:
i didn't make a nandroid backup...
Click to expand...
Click to collapse
Live and learn, I was afraid of that. You're probably going to have to use Odin then which will return you back to stock. And then start everything over again. Have you let the boot loop go for like 5 minutes. Sometimes it can take that long on first boot, but the vibration isn't normal.
jd1639 said:
Live and learn, I was afraid of that. You're probably going to have to use Odin then which will return you back to stock. And then start everything over again. Have you let the boot loop go for like 5 minutes. Sometimes it can take that long on first boot, but the vibration isn't normal.
Click to expand...
Click to collapse
the thing is though, i have flash this download of the rom before, and it was fine. i just got bored of it and downloaded another rom. i then decided to go back to the rom again.
sbouzyk said:
the thing is though, i have flash this download of the rom before, and it was fine. i just got bored of it and downloaded another rom. i then decided to go back to the rom again.
Click to expand...
Click to collapse
Try flashing it again then. Do all the wipes first then flash it and then flash gapps. Did you flash the gapps package? I'm not sure what rom you're trying to flash but it probably requires gapps too.
jd1639 said:
Try flashing it again then. Do all the wipes first then flash it and then flash gapps. Did you flash the gapps package? I'm not sure what rom you're trying to flash but it probably requires gapps too.
Click to expand...
Click to collapse
gapps isn't on my phone so i cant flash it. i've flash it about ten times now and it won't work. it must be a bad download even though i flashed it before. after i flash the rom, it shows the boot animation of the rom i had been using before. werid huh? the only option i have now is to buy a micro sd card and put the rom on that and flash it that way. i really don't want to use odin.
sbouzyk said:
gapps isn't on my phone so i cant flash it. i've flash it about ten times now and it won't work. it must be a bad download even though i flashed it before. after i flash the rom, it shows the boot animation of the rom i had been using before. werid huh? the only option i have now is to buy a micro sd card and put the rom on that and flash it that way. i really don't want to use odin.
Click to expand...
Click to collapse
The sd card is a good idea. You're going to want one anyway.
jd1639 said:
The sd card is a good idea. You're going to want one anyway.
Click to expand...
Click to collapse
thanks for all your help mate. guess I'm going to be a LOT more careful in the future. now im phoneless anyway cheers for the help
sbouzyk said:
thanks for all your help mate. guess I'm going to be a LOT more careful in the future. now im phoneless anyway cheers for the help
Click to expand...
Click to collapse
Np
sbouzyk said:
thanks for all your help mate. guess I'm going to be a LOT more careful in the future. now im phoneless anyway cheers for the help
Click to expand...
Click to collapse
You're just going to give up? Seriously? It's really easy to flash stock fw with Odin. And also easy to root afterwards, to each their own.
norml said:
You're just going to give up? Seriously? It's really easy to flash stock fw with Odin. And also easy to root afterwards, to each their own.
Click to expand...
Click to collapse
What do you mean giving up? I'm going to wait until my microSD card comes and then I will transfer the zip file that way. I don't have time to fiddle with odin. Besides I don't even have a pc, i have bootcamp, which takes a year to boot.
The keyboard doesn't work for enter sim pin after I get to CWM, even if I don't do anything in there.
For example, I get in CWM-do nothing there-reboot system and after that I can't enter sim pin.After 5-6 reboots with the power button pressed for 5sec it's ok
Here is my logcat:
Amathagma said:
The keyboard doesn't work for enter sim pin after I get to CWM, even if I don't do anything in there.
For example, I get in CWM-do nothing there-reboot system and after that I can't enter sim pin.After 5-6 reboots with the power button pressed for 5sec it's ok
Here is my logcat:
Click to expand...
Click to collapse
how you installed CWM and on what rom are you know?
Sabyn said:
how you installed CWM and on what rom are you know?
Click to expand...
Click to collapse
CWM was already in the ALL IN ONE guide i found here: http://forum.xda-developers.com/showthread.php?t=2405357
and the rom is CM 10.1
Amathagma said:
CWM was already in the ALL IN ONE guide i found here: http://forum.xda-developers.com/showthread.php?t=2405357
and the rom is CM 10.1
Click to expand...
Click to collapse
try to reflash the CM, maybe it is only a bug, i know some persons who had this problem, and with a re-flash the problem was solved
Sabyn said:
try to reflash the CM, maybe it is only a bug, i know some persons who had this problem, and with a re-flash the problem was solved
Click to expand...
Click to collapse
Clear data, cache and dalvik and flash again from CWM?Or i need something else?
(if i'm not mistake, i have done it) but ok, i can give a try.
Amathagma said:
Clear data, cache and dalvik and flash again from CWM?Or i need something else?
(if i'm not mistake, i have done it) but ok, i can give a try.
Click to expand...
Click to collapse
wipe data, cache and dalvik, after flash the cm10.1 or what you have
Sabyn said:
wipe data, cache and dalvik, after flash the cm10.1 or what you have
Click to expand...
Click to collapse
Ooh i forgot to mention that phone is e610v, not just e610.I don't know if that is problem...
Edit: no luck with re-flash CM.
Amathagma said:
Ooh i forgot to mention that phone is e610v, not just e610.I don't know if that is problem...
Edit: no luck with re-flash CM.
Click to expand...
Click to collapse
aaa, just a question, your phone is rooted right?
Sabyn said:
aaa, just a question, your phone is rooted right?
Click to expand...
Click to collapse
Yes, through the ALL IN ONE guide i posted before.
Amathagma said:
Yes, through the ALL IN ONE guide i posted before.
Click to expand...
Click to collapse
ok, because i know i had problems with E610V, i couldn`t root or flash on it, so i installed firmware for E610 , and after root, cwm and installed CM without any problems
Sabyn said:
ok, because i know i had problems with E610V, i couldn`t root or flash on it, so i installed firmware for E610 , and after root, cwm and installed CM without any problems
Click to expand...
Click to collapse
The guide that i used, had already 20d Baltic version.That means that the phone upgraded to e610, not e610v version.
I attached and a screenshot with the firmware version.It's in Greek but you can see which version is.
Can I reflash only CWM?And how?
Amathagma said:
Can I reflash only CWM?And how?
Click to expand...
Click to collapse
this is the software you have or the cm? i mean, how are you on settings if you couldn`t type the sim code
Sabyn said:
this is the software you have or the cm? i mean, how are you on settings if you couldn`t type the sim code
Click to expand...
Click to collapse
This screenshot is from my rom, CM 10.1 and I wrote in the beginning that I can enter pin after 5-6 reboots with the power key pressed for 5sec.
Edit:Updated to CM 10.2 with clean install and fixed.Thanks...
I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!
asadabbas95 said:
I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!
Click to expand...
Click to collapse
Not trying to say you're lying but are you sure you flashed everything? Are you using the flash all script or are you doing each image manually?
Mainly you need to flash boot, system, vendor, and userdata. Userdata just wipes that partition.
The N bootloader and radio should be compatible with the latest marshmallow release.
My best guess is if you used the flash all it didn't work, because it never works.
If not that then maybe you got a corrupted file? Try redownloading it and try again.
Sent from my Nexus 6P using Tapatalk
Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong
I am having the SAME EXACT issue. Found this on a search. Any solutions?
asadabbas95 said:
Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong
Click to expand...
Click to collapse
Try this command first: "fastboot format userdata" - then flash all images, exept "userdata.img".
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
I'm.at work or else I would try that method can anyone try it and see what happens . I'm trying to go back to mm also
Sent from my Nexus 6P using Tapatalk
ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Sent from my Nexus 6P using Tapatalk
Okay so I'm not the only one who's having this problem. Did the sideloading method format the sd card?
havy15 said:
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Click to expand...
Click to collapse
Download the file and rename it whatever you want. I changed it to update.zip.
Go to stock recovery and then select update from adb.
Then type ---> adb sideload "name of zip".
You will then be downgraded to stock MM with everything working.
Well at least that's what worked for me. Because I was on Android N Preview 3. It was too buggy so I tried to manually flash 6.0.1. but kept getting stuck on the white Google logo. The above method worked for me.
Are you rooted still? Someone told me if I'm going to pure rom all I need to do is wipe like normal like when you u flash a ROM and with gaps and I'll be fine with the vender image . Or do I have to do it your way . Did you go back to stock mm or a rom ?
Sent from my Nexus 6P using Tapatalk
ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
This didn't work for me either. I tried sideloading and it was sending the file, but it stopped at .02% and it gave me an error 7 and the download failed...This is really starting to annoy me because so many apps are really buggy for me on N
Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! ?? Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk
havy15 said:
Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out
asadabbas95 said:
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out
Click to expand...
Click to collapse
are you trying to back to stock or another mm rom
havy15 said:
are you trying to back to stock or another mm rom
Click to expand...
Click to collapse
I tried both..neither worked
asadabbas95 said:
I tried both..neither worked
Click to expand...
Click to collapse
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid
havy15 said:
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid
Click to expand...
Click to collapse
nah i tried that and was stuck on the google logo
asadabbas95 said:
nah i tried that and was stuck on the google logo
Click to expand...
Click to collapse
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?
havy15 said:
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?
Click to expand...
Click to collapse
yup flashed everything correctly. Try flashing and tell me if it works for you
Today and after deciding to simply restart my Nexus 6P, it booted into TWRP menu, I tried to reboot again, but no luck. can someone please help?
is there a way to get off the TWRP menu and boot my phone normally?
Note: The root used to simply work fine for about a month now.
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Gytole said:
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Click to expand...
Click to collapse
Rooted my phone, and it was working fine for about a month, I done nothing unusual, All i did is restart my phone and it went to the TWRP menu, thats all. Im stuck there now.
I don't recall doing an update or whatever. Im using "BETA-SuperSU-v2.67-20160121175247.zip"
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
MahmoudEMH said:
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
Click to expand...
Click to collapse
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Heisenberg said:
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Click to expand...
Click to collapse
Yes to each one of those questions.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
I will have to call you out here buddy. If you have indeed tried to flash all factory images, you won't even have TWRP in the first place.
Go to this wonderful guide by the wonderful @Heisenberg, and scroll down to "10. How To Flash The Factory Images (And Return To Stock)". You will find very clear instruction on how to return your phone to its factory stock state. This will most likely get rid of the problems you're facing.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
If you had flashed the full factory images I don't see how it's possible at all to be in your current situation. Explain how you flashed them, and exactly what you flashed please.