few days ago i messed up my H60L04..it won't boot up..just stuck in honor logo. tried to fix it using minimal adb but it can't see my device when i typed in adb devices..tried multi tools, and it's just the same.. and i can't see my device in device manager also.. can anyone help me please..
current recovery on my H60L04 is cwm..before this bootloop, my H60L04 running emui 2.3 B118.. kinda weird, try to google but never seen H60L04 emui 2.3 with build number B118.
how to setup adb to fix this 'no device' issue so that i can flash stock recovery and rom to get my device alive back.
bedipokya said:
few days ago i messed up my H60L04..it won't boot up..just stuck in honor logo. tried to fix it using minimal adb but it can't see my device when i typed in adb devices..tried multi tools, and it's just the same.. and i can't see my device in device manager also.. can anyone help me please..
current recovery on my H60L04 is cwm..before this bootloop, my H60L04 running emui 2.3 B118.. kinda weird, try to google but never seen H60L04 emui 2.3 with build number B118.
how to setup adb to fix this 'no device' issue so that i can flash stock recovery and rom to get my device alive back.
Click to expand...
Click to collapse
I'm not expert in Honor but I think that adb problem is caused by drivers. Do you have last drivers installed?
Sent from my HUAWEI P6-U06 using XDA mobile app
AdnanCG said:
I'm not expert in Honor but I think that adb problem is caused by drivers. Do you have last drivers installed?
Sent from my HUAWEI P6-U06 using XDA mobile app
Click to expand...
Click to collapse
i'm afraid it's the latest driver coz i try to update it online and it shows it's the latest..if it's the latest driver and i'm still have this adb issue, is there any other way to fix this?
EDIT: Ok i've fixed the adb/fastboot issue..adb/fastboot now can see my device.. the problem now is when i try to command ''fastboot flash recovery recovery.img'' it gives me:-
target reported max download size of 471859200 bytes
sending 'recovery' (9600 KB)...
OKAY [ 1.010s ]
writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. total time: 1.020s
what is the problem now?
bedipokya said:
i'm afraid it's the latest driver coz i try to update it online and it shows it's the latest..if it's the latest driver and i'm still have this adb issue, is there any other way to fix this?
Click to expand...
Click to collapse
I don't think there is another solution for adb problem. You can now download some custom rom and put it on your sd card and install it. After that your phone should boot up and try reinstalling your adb drivers. Than you can flash stock recovery and go back to stock rom.
Sent from my HUAWEI P6-U06 using XDA mobile app
AdnanCG said:
I don't think there is another solution for adb problem. You can now download some custom rom and put it on your sd card and install it. After that your phone should boot up and try reinstalling your adb drivers. Than you can flash stock recovery and go back to stock rom.
Sent from my HUAWEI P6-U06 using XDA mobile app
Click to expand...
Click to collapse
adb/fastboot can see my device now.. i try flash recovery but failed remote command not allowed..
and i already try to flash custom rom via cwm recovery, cm11 and pacman..none of them succeed..it gives me something like this ''this is for H60L04, this device hwH60'' bla bla bla aborted.hmm
what shall i do next my fren?
bedipokya said:
adb/fastboot can see my device now.. i try flash recovery but failed remote command not allowed..
and i already try to flash custom rom via cwm recovery, cm11 and pacman..none of them succeed..it gives me something like this ''this is for H60L04, this device hwH60'' bla bla bla aborted.hmm
what shall i do next my fren?
Click to expand...
Click to collapse
You also tried factory reset?
Sent from my HUAWEI P6-U06 using XDA mobile app
AdnanCG said:
You also tried factory reset?
Sent from my HUAWEI P6-U06 using XDA mobile app
Click to expand...
Click to collapse
yup..i do factory reset
bedipokya said:
yup..i do factory reset
Click to expand...
Click to collapse
Sorry my mate I don't know anything else to help you. Just try every custom rom maybe some will work.
Sent from my HUAWEI P6-U06 using XDA mobile app
AdnanCG said:
Sorry my mate I don't know anything else to help you. Just try every custom rom maybe some will work.
Sent from my HUAWEI P6-U06 using XDA mobile app
Click to expand...
Click to collapse
thanx man...really appreciate your response and help..i think that's the only way for me either, try every custom available for H6
.
hi bro.. u may try using latest multitool that support both honor 7 and honor 6.
from huawei extractor application, extract update.app file and select files 1). boot.img 2). cust.img 3). fastboot.img 4). recovery.img 5). system.img 6). userdata.img . copy all of those files and paste into folder multitool -> rec, unbrick and user folder. then try to recovery back your device. i also facing the same issue. stuck at honor logo.
Same problem here service center ask 4200 for replacing motherboard for boot loop i tried adb method but recieving same mesage
Related
Hey..
I have tried almost everything now. What can be done when i cannot restore my nexus s to original unrooted state. I have pinpointed problem to boot.img file that just refuses to flash.
C:\android-sdk-windows\tools>fastboot.exe flash boot boot.img
sending 'boot' (7936 KB)... OKAY [ 1.673s]
writing 'boot'... FAILED (remote: Write Fail)
finished. total time: 1.682s
Nandroid restore won't work either.
Is your bootloader unlocked? If so follow download Odin from the dev section.
Sent from my Nexus S using XDA App
peeturr said:
Is your bootloader unlocked? If so follow download Odin from the dev section.
Click to expand...
Click to collapse
Thanks. Do you know what driver that download mode in nexus s should use? I've downloaded new pc suite from samsung and still with no luck.
I'm using windows 7 64bit home premium.
inkogn said:
Thanks. Do you know what driver that download mode in nexus s should use? I've downloaded new pc suite from samsung and still with no luck.
I'm using windows 7 64bit home premium.
Click to expand...
Click to collapse
Download the Google USB drivers from the SDK.
Pretty sure that's all you need.
Serious_Beans said:
Download the Google USB drivers from the SDK.
Pretty sure that's all you need.
Click to expand...
Click to collapse
No, i've already tried all three drivers. Bootloader, ADB and ADB Composite driver.. All seem to install correctly but phone won't come visible in Odin
inkogn said:
No, i've already tried all three drivers. Bootloader, ADB and ADB Composite driver.. All seem to install correctly but phone won't come visible in Odin
Click to expand...
Click to collapse
It will only show up in Odin if you're in download mode. Are you in download mode?
Sent from my Nexus S using XDA App
peeturr said:
It will only show up in Odin if you're in download mode. Are you in download mode?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yes. Phone appears in device manager as "Gadget Serial"
FYI
I managed to reset my phone with Odin.. Needed driver was same as in galaxy
and i obtained it from here
http://www.mediafire.com/?3dh4d6up72me9re
Hi all,
I'm trying for days to get my Umi X2 running again.
Momentarily I see the Umi screen, followed bij the start screen where it says android.
Then I see for a few seconds the menu where you can select the language and then reboots.
I tried using Shuame, SP Flash tool and MTK Droid Tools. Nothing seems to work.
Via ADB sideload I can push a package but this gets always aborted.
I used Shuame to push the CWM 6.0.3 recovery to the phone. It states that it worked, but when I reboot to Recovery I can only get to the Factory recovery. Here you can only update software instead of installaing complete zip images.
I read about a guy who had the somewaht same issue. He said that he fumbled around with Shuame and suddenly had a recovery menu of Shuame on his Device.
ADB shell works, but I can;t get to my SDCARD as it says no device found. When I run ADB Devices nothing returns.
I already tried adding my USB device to the ini-file of ADB, to no avail.
Can someone help me get my device running again.
Chucho72 said:
Hi all,
I'm trying for days to get my Umi X2 running again.
Momentarily I see the Umi screen, followed bij the start screen where it says android.
Then I see for a few seconds the menu where you can select the language and then reboots.
I tried using Shuame, SP Flash tool and MTK Droid Tools. Nothing seems to work.
Via ADB sideload I can push a package but this gets always aborted.
I used Shuame to push the CWM 6.0.3 recovery to the phone. It states that it worked, but when I reboot to Recovery I can only get to the Factory recovery. Here you can only update software instead of installaing complete zip images.
I read about a guy who had the somewaht same issue. He said that he fumbled around with Shuame and suddenly had a recovery menu of Shuame on his Device.
ADB shell works, but I can;t get to my SDCARD as it says no device found. When I run ADB Devices nothing returns.
I already tried adding my USB device to the ini-file of ADB, to no avail.
Can someone help me get my device running again.
Click to expand...
Click to collapse
Got it running.
If someone needs instructions, let me know.
err... did u reflash the partion part ?
Sent from my GT-S5360 using xda app-developers app
Ryanrioz said:
err... did u reflash the partion part ?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I used SP Flash Tool to reflash the recovery.img
More Details
I need more details on how did you use the flash tool to solve your problem? I have the same problem here. I need to know how to show (in sp flash tool) where is my downloaded .IMG file. Step by step
Chucho72 said:
Yeah, I used SP Flash Tool to reflash the recovery.img
Click to expand...
Click to collapse
Me Too
toninhocs said:
I need more details on how did you use the flash tool to solve your problem? I have the same problem here. I need to know how to show (in sp flash tool) where is my downloaded .IMG file. Step by step
Click to expand...
Click to collapse
Hi, I have the same problem (silly me), where did you get that recovery.img?
Any hints would be helpful
Thanks
TOM
In case you ever want to claim warranty.
Instructions:
Download ADB and recovery.zip.
Extract both to same folder.
Power down device.
Reboot into fastboot by pressing the 'Volume up + Power' buttons.
Connect phone to PC using USB cable
Open Command Prompt and CD to the ADB directory.
Type the command below
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot
Downloads:
ADB and Fastboot courtesy @ankur850 from here https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Stock recovery from here: http://www.mediafire.com/download/j7h4u4x2nfnm676/recovery.zip
Hit Thanks :good: if this thread is helpful.
Refer this link for commonly asked questions before posting your doubts.
stuck at waiting for device
hi , i am trying to restore my xolo play to stock odexed rom provided at http://forum.xda-developers.com/showthread.php?p=44264063
. when i connected my phone , its saying waiting for the device. I know i am missing some drivers . Can you explain the procedure to install the drivers.
Thanks.
deepaktom said:
In case you ever want to claim warranty.
Instructions:
Download ADB and recovery.zip.
Extract both to same folder.
Power down device.
Reboot into fastboot by pressing the 'Volume up + Power' buttons.
Connect phone to PC using USB cable
Open Command Prompt and CD to the ADB directory.
Type the command below
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot
Downloads:
ADB and Fastboot courtesy @ankur850 from here https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Stock recovery from here: http://www.mediafire.com/download/j7h4u4x2nfnm676/recovery.zip
Hit Thanks :good: if this thread is helpful.
Click to expand...
Click to collapse
sreekar said:
hi , i am trying to restore my xolo play to stock odexed rom provided at http://forum.xda-developers.com/showthread.php?p=44264063
. when i connected my phone , its saying waiting for the device. I know i am missing some drivers . Can you explain the procedure to install the drivers.
Thanks.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=43981028
installed drivers: but returns Failed
Hi i was able to install drivers. after lot of searching.
now when i sent command "astboot oem get_identifier_token" it is aying Failed.
when i searched , i found out that bootloader needs to be unlocked. can you explain in steps how to do this? and will i loose warrenty if i do this?
currently :
i did an ota update. its resulting in improper video playback. so i want to flash recovery rom.
thanks.
deepaktom said:
Try this
http://forum.xda-developers.com/showthread.php?p=43981028
Click to expand...
Click to collapse
sreekar said:
Hi i was able to install drivers. after lot of searching.
now when i sent command "astboot oem get_identifier_token" it is aying Failed.
when i searched , i found out that bootloader needs to be unlocked. can you explain in steps how to do this? and will i loose warrenty if i do this?
currently :
i did an ota update. its resulting in improper video playback. so i want to flash recovery rom.
thanks.
Click to expand...
Click to collapse
This one is not like other phones man. Boot loader is already unlocked
Sent from my XOLO Play using Tapatalk 2
sreekar said:
Hi i was able to install drivers. after lot of searching.
now when i sent command "astboot oem get_identifier_token" it is aying Failed.
when i searched , i found out that bootloader needs to be unlocked. can you explain in steps how to do this? and will i loose warrenty if i do this?
currently :
i did an ota update. its resulting in improper video playback. so i want to flash recovery rom.
thanks.
Click to expand...
Click to collapse
The bootloader is already unlocked & to flash recovery ,use instruction given by deepak or use app flashify from play store
Flashing with a custom rom.
har****181 said:
The bootloader is already unlocked & to flash recovery ,use instruction given by deepak or use app flashify from play store
Click to expand...
Click to collapse
hi,
from the link,
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
i don't have custom recovery installed.
and i don't have a memory card.
what i need to do if i want to install odexed rom install.
does custom recovery installation involves rooting phone?
is it not possible to flash unrooted phones?
update:
i did
fastboot flash boot boot.img
from the boot.img file from odexed rom zip.
Is my warranty still intact?
what i did by flashing the boot partition?
boot.img is only 8 MB what is the other content present in the rom zip file and how its used?
thanks,
sreekar
sreekar said:
hi,
from the link,
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
i don't have custom recovery installed.
and i don't have a memory card.
what i need to do if i want to install odexed rom install.
does custom recovery installation involves rooting phone?
is it not possible to flash unrooted phones?
update:
i did
fastboot flash boot boot.img
from the boot.img file from odexed rom zip.
Is my warranty still intact?
what i did by flashing the boot partition?
boot.img is only 8 MB what is the other content present in the rom zip file and how its used?
thanks,
sreekar
Click to expand...
Click to collapse
OK I'll spend some time here so you can understand. Warranty can be checked in most phones with locked bootloaders . ours is not locked. Bootloader locked means no change can be made unofficially by us.
The only way they can find warranty on our phone is if you use official root method.
For this purpose we have unofficial root method.
Now about partitions. /boot is the kernel. Its like drivers for your hardware.
/system is the os. It is either rooted or unrooted like in windows having admin account or normal account.
You can either use an OS which has already admin account by using a rooted ROM or you can use a limited unrooted ROM and then root it thereby making it an admin account.
Now recovery is a mini OS which will help you to recover your OS in case something is wrong. Stock recovery has limited options and allows only official updates. Custom recovery has more options and allows unofficial updates like our prerooted already admin OS/ROM.
Finally fast boot is like your Intel BIOS. Whatever happens as long as it is working you're saved. All other things like recovery, boot, system can be modified from here.
Now you flashed boot.img using fast boot and if you got a success message you're good. Use a recovery image in one of the xolo play threads and flash it using the instructions provided there.
This is required for you to install ROM.
Finally, don't worry about warranty. In case you ever need warranty, follow instructions in my ROM post about warranty. Where you can flash the ROM and recovery that came with the phone. So no worries and good luck.
Edit: for you, since you're so worried, simply install cwm recovery, then install stock odexed ROM, install build.prop.zip then reinstall stock recovery and you're like how u purchased the phone.
Sent from my XOLO Play using Tapatalk 4
i m having this problem .. after typing command it keeps displaying waiting for device .. nothing happens after that .. wat am i doing wrong . ( i tired instaling drivers but it says -windows has determined software is up to date) what shud i do .. cant install ny rom too
mkr17 said:
i m having this problem .. after typing command it keeps displaying waiting for device .. nothing happens after that .. wat am i doing wrong . ( i tired instaling drivers but it says -windows has determined software is up to date) what shud i do .. cant install ny rom too
Click to expand...
Click to collapse
right click the device under device manager and select uninstall. then replug device and browse and select the driver
http://support.moulnisky.com/index.php?dir=Xolo/Xolo Play/
Here factory firmware and instructions
BR
Alex
http://forum.xda-developers.com/showpost.php?p=47122148&postcount=881
Posted the same here
btw, There is an S018 fw out too. Those linked above are outdated.
Free Radical said:
http://forum.xda-developers.com/showpost.php?p=47122148&postcount=881
Posted the same here
btw, There is an S018 fw out too. Those linked above are outdated.
Click to expand...
Click to collapse
Yes,
Already added it in the support area
BR
Alex
mr moulinsky i have karbonn A8 device i flash software but now device is show fizzy and white display with china sound no karbonn logo please help me how to flash karbonn A8 with right flash files
Sent from my Micromax A76 using XDA Premium 4 mobile app
HELP!!
kkbs4u said:
mr moulinsky i have karbonn a8 device i flash software but now device is show fizzy and white display with china sound no karbonn logo please help me how to flash karbonn a8 with right flash files
sent from my micromax a76 using xda premium 4 mobile app
Click to expand...
Click to collapse
my xolo play t1000 is locked due to too many pattern locks. Now it is asking for gmail id & password but my data is off. Now i got struck as my xolo secure is on i cannot wipe data/factory reset the phone. What should i do to unlock also i dont want to loose my warranty.i also cannot visit the service center as it will cost me a flight fare of 6000 bucks. Help me!!!!
Thanks in advance..
morning.revz08 said:
my xolo play t1000 is locked due to too many pattern locks. Now it is asking for gmail id & password but my data is off. Now i got struck as my xolo secure is on i cannot wipe data/factory reset the phone. What should i do to unlock also i dont want to loose my warranty.i also cannot visit the service center as it will cost me a flight fare of 6000 bucks. Help me!!!!
Thanks in advance..
Click to expand...
Click to collapse
try booting into recovery and factory resetting the device...press vol down+power button to boot into recovery and then wipe data/factory reset
I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.
icemann1908 said:
I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.
Click to expand...
Click to collapse
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Sent from my Nexus 6P using XDA-Developers mobile app
Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse
ebbytay said:
Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse
Rashad83 said:
ebbytay said:
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse
ebbytay said:
Rashad83 said:
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse
Rashad83 said:
ebbytay said:
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse
ebbytay said:
Rashad83 said:
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse
You're welcome. Good luck.
Click to expand...
Click to collapse
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson