Related
hello everyone,
I am trying to fix an ellipsis 7. My cousin had it requesting a system update but he kept on postponing it. when he did decide to update it there was a glitch I assume and android was somehow wiped from the tablet. I have managed to get into factory mode but there is no way to do a factory reset. In factory mode all I see is reboot, auto test, manual test, item test, tet report, debug test, clear emmc, safe mode, and version. I have tried both clear emmc and safe mode, but nothing happens there. I have checked version and like I said it shows no android version on it which I assume means no android on the device. Is there some way of making a bootable sd card to get the software back on it?
So I've been running into problems every step of my rooting process. First I couldn't get fastboot to recognize my device [solved], then I couldn't boot into TWRP [solved], then I couldn't use my phone as a storage device in windows [solved]. Now that I've finally installed SuperSu from TWRP, I soft bricked my device. Booting just hangs on the Honor logo. What can I do to fix this? I don't have a micro sd card, so I can't put another rom on my device AFAIK. I can still boot into TWRP, but wiping didn't fix anything and I'm out of ideas.
When my phone was last working it said it was GEM-703L B211
EDIT: So I've taken some extra steps. I went out and bought an SD card. I've tried installing KangVIP Slim B211, B112 Rooted With GAPPS (1.3gb), and B112 Rooted Debloated With GAPPS (968mb), respectively. Obviously I did a factory reset before each attempt, but I'm still hanging on boot. After installing KangVIP, it switched to the fancy Huawei logo, but still hung. Then when going back to the other roms, it switched back to Honor, but it still hangs. After a few boot loops now, it goes straight into TWRP.
I've been at this all night now. I just wanted to get rid of all the Chinese characters on my phone, and now I have no phone. Any help would be super appreciated. :/
Have you waited up to 50 minutes, after wipe dalvic? It takes about 40 minutes on honor screen on my device on first boot.
My device: 701->703 B211 xposed 86
audioralf said:
Have you waited up to 50 minutes, after wipe dalvic? It takes about 40 minutes on honor screen on my device on first boot.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
It goes straight to TWRP after about 1 minute of looping. I'm going to try the back to stockrom recovery guide and come back with my results.
EDIT: It worked! I got back to the stock firmware.
Bearses said:
So I've been running into problems every step of my rooting process. First I couldn't get fastboot to recognize my device [solved], then I couldn't boot into TWRP [solved], then I couldn't use my phone as a storage device in windows [solved]. Now that I've finally installed SuperSu from TWRP, I soft bricked my device. Booting just hangs on the Honor logo. What can I do to fix this? I don't have a micro sd card, so I can't put another rom on my device AFAIK. I can still boot into TWRP, but wiping didn't fix anything and I'm out of ideas.
When my phone was last working it said it was GEM-703L B211
EDIT: So I've taken some extra steps. I went out and bought an SD card. I've tried installing KangVIP Slim B211, B112 Rooted With GAPPS (1.3gb), and B112 Rooted Debloated With GAPPS (968mb), respectively. Obviously I did a factory reset before each attempt, but I'm still hanging on boot. After installing KangVIP, it switched to the fancy Huawei logo, but still hung. Then when going back to the other roms, it switched back to Honor, but it still hangs. After a few boot loops now, it goes straight into TWRP.
I've been at this all night now. I just wanted to get rid of all the Chinese characters on my phone, and now I have no phone. Any help would be super appreciated. :/
Click to expand...
Click to collapse
>> then I couldn't use my phone as a storage device in windows [solved].
would you point me to your solution?
Thanks
Wolfgang
woschirmer said:
>> then I couldn't use my phone as a storage device in windows [solved].
would you point me to your solution?
Thanks
Wolfgang
Click to expand...
Click to collapse
When you plug your phone into your pc, slide the notifications slider down and note the "usb connection" there. You have to tap files to enable mass storage on your pc. I don't know why it's set up that way, but it fixed it for me.
Bearses said:
When you plug your phone into your pc, slide the notifications slider down and note the "usb connection" there. You have to tap files to enable mass storage on your pc. I don't know why it's set up that way, but it fixed it for me.
Click to expand...
Click to collapse
Thanks!!!
Hi guys.
Im hoping someone has a clever fix to my problem.
Version: FLD-L09C432B131, rooted and with TWRP.
Issue:
I took a plunge into the updating sea and installed B360. Never thought it would go through since I didnt unroot first. Well, it actually worked and the phone booted fine. The "About" part listed the new version but I was still on decembers security patch. So I ran Firmware Finder and started with the small file, 230MB or something. Unpacked it and moved to dload via the menu in FF.
Now the problems began. Phone booted and ran the update without any noticable issue....until it was time for a reboot.
It now only boots into Huawei eRecovery with the options to:
"Download latest version and recovery" - Which fails after connecting to wifi and trying to download from huawei.
"Reboot" - Just returns to eRecovery.
"Shutdown" - self-explanatory.
The devices does show up for a few seconds in ADB when it reboots and is connected to my PC. But not for long.
I was hoping to be able to flash TWRP with ADB but its kinda hard when it doesnt stay connected.
Anyone wise out there with some input?
Much obliged.
/nort
Ok update.
I managed to get adb to work finally by timing the seconds the phone was actually visible to the computer. A reset back to B131 and now im on B360. Not sure if i have the latest version with the battery fix but I guess that will be obvious soon enough.
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
abbassbhai said:
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
Click to expand...
Click to collapse
Have you tried to flash custom ROMs or TWRP?
overcustom said:
Have you tried to flash custom ROMs or TWRP?
Click to expand...
Click to collapse
i was trying to dload mm firmware. The firmware dloaded fine but after factory reset and reboot, the fone is jus staying on honor screen after 3d text. i tried to go in erecovery but cannot, fone jus vibrates twice and then after 3d honor text, it stays on blue honor screen forever.
i tried to boot in fastboot as well as dload.....same thing happend not booting in fastboot or dload.
only 3d text and blue screen.
now fone doesnt even turns on if power button pressed ,but juss vibrates twice and blue screen after 3d text.
Leave your device as it is so that the battery is fully drained and is powered off. Then plug your device to charger for 5 minutes. Unplug it and now try to boot to recovery.
Hold the power button and volume up button until you hear the first vibration and screen goes on. Leave both buttons. Now you can go to recovery. Perform a full factory reset. Then power off your device and move the dload package to your external SD card. Repeat the same process but this time hold both volume buttons and power button.
hackslash said:
Leave your device as it is so that the battery is fully drained and is powered off. Then plug your device to charger for 5 minutes. Unplug it and now try to boot to recovery.
Hold the power button and volume up button until you hear the first vibration and screen goes on. Leave both buttons. Now you can go to recovery. Perform a full factory reset. Then power off your device and move the dload package to your external SD card. Repeat the same process but this time hold both volume buttons and power button.
Click to expand...
Click to collapse
thankyou bro for ur suggestion...i already tried all tht but no luck.
the fone turns on everytime whatever i try to do....only 3d text and it is stuck on blue honor screen.
no recovery dload fastboot etc.
Hi. Sorry the revive.
Could you solve this? I'm in the same situation
No unlock, can't enter to recovery, can't enter to erecovery so I can't flash with dload, fastboot is a joke if the phone has locked bootloader so I can't reflash the recoveries.
abbassbhai said:
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
Click to expand...
Click to collapse
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Click to expand...
Click to collapse
A late answer but maybe useful for some
Because the OTA showed up, was not a full OTA file. I guess it was only 1.3 gb something. It was a test build and didnt have any apks inside including the keyboard. And also not a stable one (test build) So it is always better to download FULL package from the menu and flash that one.
Hey,
I need some help with this problem. I have a frd lo4 on nougat. I tried to return to stock from being rooted. The dLoad folder method wasn’t working (returned invalid package) so I unrooted via the SU app, flashed stock recovery, and went into fastboot and relocked the bootloader with the code.
Now it won’t boot or shut off. Just a bootloop showing the blue screen. I could use to access fastboot before but now my pc doesn’t detect my phone. I’ve tried different ports and pc’s. I can’t access recovery either.
Any help is appreciated
EDIT: I let the battery die, then tried going into fastboot mode and it worked. I flashed the stock recovery 1 and 2. I then used the correct rollback package and put it on my sd card then flashed. I then downloaded the full 6.0 firmware and did the same. Now I’m unrooted, locked bootloader, and stock.
Hope this helps someone.
Excatly the same thing happened to me 1 week ago.. My phone was going on bott loop in recovery mode.. I tried Dload method and recovery but nothing happened.. atlast i let the battery die. After the battery is completly dead i connexted the charger and hola the adb is working now. Then i flashed correct recovery and rom. Ecerything is working fine now.
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
did u solve this bro. Same here happened, no recover no erecovery but just fastboot mode working. I let the battery died but cant charge it now, charging light is just blinking.. I have unlocked bootloader..