Related
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
tomolewis said:
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
Click to expand...
Click to collapse
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
chronic8000 said:
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
Click to expand...
Click to collapse
look this
http://www.forum-generationmobiles.net/f447-one-touch-idol-s
Any news on this?
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
chronic8000 said:
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
Click to expand...
Click to collapse
reflash
pmarkov said:
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
Click to expand...
Click to collapse
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
gabcs said:
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
Click to expand...
Click to collapse
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Root Alcatel
Hello everyone, Esque quelqun could tell me when will esqu'on rooter The alcatel one touch idol 2 mini S android 4.3 please
zlamar said:
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Click to expand...
Click to collapse
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
gabcs said:
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
Click to expand...
Click to collapse
pmarkov said:
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
Click to expand...
Click to collapse
Try this: shared.com/7dwx96a1yy?s=l
This is from the french forum - I already tried exactly this image with no success.
gabcs said:
Try this: shared.com/7dwx96a1yy?s=l
Click to expand...
Click to collapse
pmarkov said:
This is from the french forum - I already tried exactly this image with no success.
Click to expand...
Click to collapse
your phone is 6034 or 6035? i tried on 2 phones (6034r) and the custpack is work. one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
gabcs said:
one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
Click to expand...
Click to collapse
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
zlamar said:
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
Click to expand...
Click to collapse
Sorry, but my english is bad. But yeah, i know, i spent 3 days (0-24) to fix this phone. For me the reflash custpack, boot and system img worked from my first post. From mediafire folder need just the 2 roms. the first 70mb is only the system. The orange rom i think the full rom. Yes, every two are cwm flashable. Try to flash the img-s in bootloader mode after flash the 70mb rom with cwm. If dont work make a factory reset with cwm and flash the 233mb orange rom. This phone's software like a nightmare. No source code, everything is different like in other phones and nobody knows the different between the 6034 and 6035. I better like my OT-991 with MTK soc...
@gabcs
Unfortunatelly, after no success in searching for solution (couldn't find the ROM), two weeks ago, I gave up and sent my phone to service center and I hope that they will resolve the problem. Big and frustrating issue was that I couldn't get to bootloader any more, so the phone couldn't recieve adb commands, only thing that worked was CWM...
Service center will resolve that for 20 euros, and I will resolve my nerves
Anyway, thank you for your time and your help.
@zlamar,
what happened with your phone? Did you managed to have it repaired/restored? My phone is still bricked and It seems the problem is to find the appropriate custpack image as the french versions don't work for other countries.
Still nothing.... Service center where I gave it for repair isn't authorised and they didn't resolve the issue.
Does anybody have a full CWM backup image, and is willing to share it and upload it somewhere?
It has nothing to do with authorization, they just don't have alcatel service access.
There is special alcatel service flasher, that works online, and is intended for Qualcomm platform.
I played with it, and re-flashed my 6016x (MSM8210 - Qualcomm Snapdragon 200).
If you were somewhere closer, I would repair it for 20€ very fast and effiecent
@pmarkov ... I have original files but they are useless, because no any flasher to use them.
b.r.
ALex
Hi Alex,
Thanks for the clarification. Obviously this magic flashing tool is only internaly available for authorized service providers. Today I contacted the official local partner of Alcatel and they were positive they can handle the reflashing for approx. 20 EUR. Let's hope they really will fix it.
BR
Hi,
First of all sorry for crappy links, but as a new user I cannot post them.
I have got a chinese phone called Haier W858 (imei.info/phonedatabase/15302-haier-w858/). Few days ago I found out that it is similar to Smartfren Andromax I3S and managed to modify stock ROM by fastboot without any problems (current ROM: needrom.com/download/smartfren-andromax-ad682h/). After that when I tried to turn on fastboot mode I got information that bootloader is locked and I need verify.zip file on sdcard to unlock it. Few searches later I found correct verify.zip file and put it on sdcard. Everything should be great, because now when I try to run fastboot mode I get information that verify.zip file is correct and phone turns into some kind of fastboot mode, but I cannot write anything to it.
For example, I get messages like:
Code:
> fastboot flash modem modem\NON-HLOS.bin
sending 'modem' (31985 KB)... OKAY
writing 'modem'... [B]FAILED (remote: can't flash Partition)[/B]
When I check if bootloader is unlocked by fastboot oem device-info I get:
Code:
>fastboot oem device-info
... INFO Device tampered: true
[B]INFO Device unlocked: true[/B]
INFO Charger screen enabled: true
OKAY
so it looks like everything should be alright.
Whatsmore, I can write any ROM by doing it like so:
- turn into that weird fastboot mode,
- boot up into TWRP or CWM by writing: fastboot boot recovery.img (because of this problem I cannot flash it permanently so I boot it up),
- install ROM from recovery.
What my question is - is it possible to flash previous fastboot mode where I could write anything to phone without problems and without checking any verify.zip file?
I do not know if it could help in anything but this is shot made when I did not have correct verify.zip file: postimg.org/image/u7thz6tq7/. Now it says that it is OK and boots up into that weird fastboot mode.
Thanks in advance.
Are you trying to flash a modem from a Samsung phone? Haven't seen NON-HLOS.bin files used in other phones before. That would explain why it wouldn't flash through fastboot...
es0tericcha0s said:
Are you trying to flash a modem from a Samsung phone? Haven't seen NON-HLOS.bin files used in other phones before. That would explain why it wouldn't flash through fastboot...
Click to expand...
Click to collapse
Hard to say if it is modem from Samsung phone, because all of ROMs for this kind of phone got that file. Maybe it is based on Samsung soft... I did not have any problems with flashing this and other files once with fastboot (first flash that I made was with ROM from this site: needrom.com/download/smartfren-andromax-ad682h/) and it was successful, but after that I get messages that I wrote in 1st post.
Any advices?
Is there a fastboot command to reflash OEMINFO??
RobertHarkness said:
Is there a fastboot command to reflash OEMINFO??
Click to expand...
Click to collapse
Don't know about the fastboot command but you can do that manually inside twrp. And twrp you can flash using fastboot.
I've fixed this now, Apologies for wasting a thread
RobertHarkness said:
I've fixed this now, Apologies for wasting a thread
Click to expand...
Click to collapse
Edit the title of the thread (through desktop browser) with SOLVED
Could you please tell us how you fixed it? I have the exact same problem, I cant rebrand my China phone cus the oeminfo.bin file wont flash.
hennos said:
Could you please tell us how you fixed it? I have the exact same problem, I cant rebrand my China phone cus the oeminfo.bin file wont flash.
Click to expand...
Click to collapse
What's the error message?
The error message is:
dd: can't open '/tmp/oeminfo': No such file or directory
I' m trying to rebrand a STF-AL00 to EU version. I've managed to unlock the phone, flash other firmware but the model number won't change...
hennos said:
The error message is:
dd: can't open '/tmp/oeminfo': No such file or directory
I' m trying to rebrand a STF-AL00 to EU version. I've managed to unlock the phone, flash other firmware but the model number won't change...
Click to expand...
Click to collapse
Boot into TWRP and execute this (name your oeminfo file "oeminfo)":
Code:
ADB push oeminfo /tmp/oeminfo
ADB shell "dd if=/tmp/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
ADB reboot bootloader
ADB kill-server
If it still doesn't work add those two commands at the beginning.
Code:
ADB shell "rm -fr /tmp > /dev/null 2>&1"
ADB shell "mkdir /tmp > /dev/null 2>&1"
Thanks a lot for the detailed explanation, I'll try it later this week when I get back home again.
oeminfo file
Hey, I flashed an EU version on my STF-AL00 honor 9. I encountered the same problem as hennos. (dd: can't open '/tmp/oeminfo': No such file or directory)
I followed this tutorial :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
Could anyone provide the oeminfo file of the EU version, I can't find it in the zip file provided in the tutorial ?
Thanks in advance !
Benjamin
benj31lsr said:
Hey, I flashed an EU version on my STF-AL00 honor 9. I encountered the same problem as hennos. (dd: can't open '/tmp/oeminfo': No such file or directory)
I followed this tutorial :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
Could anyone provide the oeminfo file of the EU version, I can't find it in the zip file provided in the tutorial ?
Thanks in advance !
Benjamin
Click to expand...
Click to collapse
Did you find a solution?
Same problem here and nothing yet :/
FelipeRsN said:
Did you find a solution?
Same problem here and nothing yet :/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74536823&postcount=107
Hi! I have same problem, somebody has fixed it? Thanks!
owusko said:
Hi! I have same problem, somebody has fixed it? Thanks!
Click to expand...
Click to collapse
What problem you have??
hassanjavaid8181 said:
What problem you have??
Click to expand...
Click to collapse
Hi! when I'm rebranding Chinese Honor 9 to EU I can pass from:
dd: can't open '/tmp/oeminfo': No such file or directory
Thanks!
Cannot boot after flashing (dd) oeminfo. Have backup but cannot flash.
Hi.
I needed to change the boot logo on a few tablets and so i dumped the oeminfo partition and changed the logo data to all zeroes. This the modded oeminfo worked well on the first tablet, but when I flashed it to the second tablet it stopped booting. In retrospect I can see how this is a bad idea as the oeminfo supposedly contains device specific information such as IMEI etc.
I did make a backup of the original oeminfo partition with dd before flashing the modified one. The problem now is that fastboot does not allow me to flash the original oeminfo partition. I get:
Code:
$ sudo fastboot flash oeminfo oeminfo.img
target reported max download size of 531628032 bytes
sending 'oeminfo' (65536 KB)...
OKAY [ 2.091s]
writing 'oeminfo'...
FAILED (remote: Command not allowed)
finished. total time: 2.097s
I cannot seem to boot into recovery as the boot process gets stuck before this (Tried with key-combo and through fastboot boot).
Device is a: HUAWEI MediaPad M3 Lite 10
Phone and FRP unlocked.
As far as I can see there is no custom recovery available for this device yet (and it would properly not be usable as I cannot access original recovery)
Do you guys have any clue on how to flash the original oeminfo partition? I can make changes to the boot partition and was thinking about if there could be a way to enable adb in a recovery mode during boot by changing the init.rc / build.prop etc?
Any ideas on how to solve this or for a more suitable thread would be deeply appreciated.
Thanks
RobertHarkness said:
I've fixed this now, Apologies for wasting a thread
Click to expand...
Click to collapse
Worst members at any possible forum that say "i solve problem" then end.
Is so hard to share with others ? At last dont write at all , really cheap stuff
Hello, I have bricked my phone when I was trying to go back to stock firmware from RR.
TWRP does not work for me, internal storage can not be read (even though I've tried all images I've found for this phone..) so I had to do it through fastboot and hwota.
Somehow it bricked the phone and I get
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 7 (teeos image)
Error NO: 1 (security verify failed!)
If I extract TEEOS.img from UPDATE.app (8.0.0.145(C432)) and try
fastboot flash teeos TEEOS.img
I get
FAILED (remote: command not allowed)
I've tried to flash
SYSTEM.img
RECOVERY_RAMDIS.img
RAMDISK.img
If anyone know what I can do to fix this please enlighten me..
monsterkaka said:
Hello, I have bricked my phone when I was trying to go back to stock firmware from RR.
TWRP does not work for me, internal storage can not be read (even though I've tried all images I've found for this phone..) so I had to do it through fastboot and hwota.
Somehow it bricked the phone and I get
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 7 (teeos image)
Error NO: 1 (security verify failed!)
If I extract TEEOS.img from UPDATE.app (8.0.0.145(C432)) and try
fastboot flash teeos TEEOS.img
I get
FAILED (remote: command not allowed)
I've tried to flash
SYSTEM.img
RECOVERY_RAMDIS.img
RAMDISK.img
If anyone know what I can do to fix this please enlighten me..
Click to expand...
Click to collapse
Can you still get a bootloader mode?
If you still get bootloader enough to fix it.
This job must be solved on DC Phoenix Only
I'm sucess with this link
https://www.******.com/recover-huawei-bricked-devices-dc-phoenix/
I accomplished these images. ..good luck..
My device : huawei nova 2i [RNE-L22]
You can try this:
https://forum.xda-developers.com/showpost.php?p=74853704&postcount=91
Im not sure why is was removed from first post...?
taddzio said:
You can try this:
https://forum.xda-developers.com/showpost.php?p=74853704&postcount=91
Im not sure why is was removed from first post...?
Click to expand...
Click to collapse
I payed for funkyhuawei... it fixed the recovery. I now have a working eRecovery and recovery but failed to download OS. I will try hwota method. Does it work with 8.0.0.145(c432)??
Just download the official files and run?
The download link seem to be removed
monsterkaka said:
I payed for funkyhuawei... it fixed the recovery. I now have a working eRecovery and recovery but failed to download OS. I will try hwota method. Does it work with 8.0.0.145(c432)??
Just download the official files and run?
Click to expand...
Click to collapse
Can you fix it?? Please let me know how you do it?? I´m in the same situation
ï have the same problem please add me on discord if you can help i will reward you Moose#9703
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Hi, thanks for your fast answer!
fastboot oem get-build-number
Code:
(bootloader) :System 8.0.0.046(09B8)
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem get-product-model
Code:
(bootloader) ANE-LX1
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot getvar vendorcountry
Code:
vendorcountry: ti/it
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
Code:
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.019s
fastboot oem oeminforead-SYSTEM_VERSION
Code:
(bootloader) :ANE-LX1 8.0.0.151(C55)
OKAY [ 0.013s]
finished. total time: 0.014s
I don't know why but the CUSTOM_VERSION reading failed...
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
-Alf- said:
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
Click to expand...
Click to collapse
I think it's C55 , correct me if I'm wrong...
-Alf- said:
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
Click to expand...
Click to collapse
I tried, but doesn't work at all...
-Alf- said:
I think it's C55 , correct me if I'm wrong...
Click to expand...
Click to collapse
Yeah, it is C55. I don't know what to do anymore
andreasaracino said:
I tried, but doesn't work at all...
Yeah, it is C55. I don't know what to do anymore
Click to expand...
Click to collapse
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
I did this once to my kiwi (5x) then it went totally blank when i tried flashing an Huawei related system flashing tool. Do not try that.
-Alf- said:
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
Click to expand...
Click to collapse
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
andreasaracino said:
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
Click to expand...
Click to collapse
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
-Alf- said:
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
Click to expand...
Click to collapse
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
andreasaracino said:
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Click to expand...
Click to collapse
andreasaracino said:
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
Click to expand...
Click to collapse
then it is not FULLOTA-MF but Service ROM, bro ...okay, it doesn't matter now.