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
Related
I experience the same symptoms as this thread, but the proposed solution does not work for me. (the sd_update.log says
Failure: OSBL°æ±¾Æ¥Åäʧ°Ü.
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
Click to expand...
Click to collapse
I rooted the phone, and misread the instructions for altering the recovery.img, which is what caused the problem in the fist place.
I have tried flashing with B925, B927 without luck.
I have also tried to use sudo fastboot boot recovery.img with a local recovery.img, and tried flashing fastboot flash recovery recovery.img - but it says
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
which i presume is because the bootloader is not unlocked.
I also tried fastboot getvar all - but that came out empty.
I also tried http://androidforums.com/huawei-ideos-x5-u8800/593253-unlock-bootloader-huawei-supply-code.html but the model is not listed...
I have an idea that essentially i just have to get in and delete recovery.img and rename recovery.backup.img to recovery.img - but i haven't got a clue about how to do it.
Phone responds to fastboot commands.
I look forward to your input.
Jonas
[SOLVED] patch to enable B919 was the missing link
Solved: www .shadowandy .net/2013/01/huawei-honor-u8860-shendu-rom-flashing-guide.htm the first link (dload_B929rus.rar (MD5 = 7264f7ad3bd7eebd298a8be978823734)) solved the problems, i am now on a B919 chinese rom.
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 Guys,
I have been reading and trying this for two weeks now and Im lost still. Never had an issue where I just couldnt figure it out now i need to ask for some help. I have a Kindle Fire HDX 7 ITS BEEN ROOTED AND USED FOR ABOUT A YEAR NOW WITH NO ISSUES. I decided to upgraade the ROM and installed the wrong version (apollo) how I done that is becide me, anyway now Im stuck in bootloop grey kindlefire screen. I do have ADB working whoever it is in a loop state so I have to be quick to insert commands. My bootloader is locked so im limited. I also am able to get into Fastboot and it works and also verified the device is locked. I have my download size 0x20000000 and I have my manfid 0x000045 and my device serial 0xf0bf7e1d . I just cant get the img created correctly or size correct c
would someone help me with the file creating and flashing procedure in fastboot to get my device working again? Im pure crosseyed at this point and about to use the Kindle as a Target at the range lol.
Thanks to anyone that can help
Which Fire OS version is on your HDX? The wrong Apollo version? Note that bootloader unlock is possible from 3.1.0 to 3.2.3.2 only.
The bootloader unlock procedure ist described here (might require these drivers). Note that you have to install the software mentioned, download the script and use it with your ID and serial to create the .unlock file.
Cl4ncy said:
Which Fire OS version is on your HDX? The wrong Apollo version? Note that bootloader unlock is possible from 3.1.0 to 3.2.3.2 only.
The bootloader unlock procedure ist described here (might require these drivers). Note that you have to install the software mentioned, download the script and use it with your ID and serial to create the .unlock file.
Click to expand...
Click to collapse
is there a commant in ADB or Fastboot that will tell me the OS Version?
iv got the product THOR
getvar version 0.5
Kernal 1K
getvar production 1
getvar serialno D0FBA0A03464QM7Q
GETVAR MAX DOWNLOAD 0X20000000
bowman1966 said:
is there a commant in ADB or Fastboot that will tell me the OS Version?
iv got the product THOR
getvar version 0.5
Kernal 1K
getvar production 1
getvar serialno D0FBA0A03464QM7Q
GETVAR MAX DOWNLOAD 0X20000000
Click to expand...
Click to collapse
I don't know, I'd hoped you'd still have the Apollo update file you flashed - it should have the version number right there in its file name.
Cl4ncy said:
I don't know, I'd hoped you'd still have the Apollo update file you flashed - it should have the version number right there in its file name.
Click to expand...
Click to collapse
ill check for the file but my issue now is the steps in Python27 for creating a file , i created but wrong size wrong number that kind of issue. Was hoping I could get someone to do a step by step in order using the cuberHDX.py
bowman1966 said:
ill check for the file but my issue now is the steps in Python27 for creating a file , i created but wrong size wrong number that kind of issue. Was hoping I could get someone to do a step by step in order using the cuberHDX.py
Click to expand...
Click to collapse
Well, if you don't have 3.1.0 - 3.2.3.2 it doesn't make any sense anyway, but ...
it's easier than you think.
You open a DOS box, change dir to your ADB directory (enter cd\adb) then enter the following commands:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
Cl4ncy said:
Well, if you don't have 3.1.0 - 3.2.3.2 it doesn't make any sense anyway, but ...
it's easier than you think.
You open a DOS box, change dir to your ADB directory (enter cd\adb) then enter the following commands:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands).
Click to expand...
Click to collapse
thanks for the help, Well I guess I have been doing this correctly the whole time. Still getting Unload code not correct in fastboot, so apparently I have the noncapadible bootloader.
is there anything I can do with it besides taking it to the range for target practice?
bowman1966 said:
thanks for the help, Well I guess I have been doing this correctly the whole time. Still getting Unload code not correct in fastboot, so apparently I have the noncapadible bootloader.
is there anything I can do with it besides taking it to the range for target practice?
Click to expand...
Click to collapse
Difficult to say, but it doesn't look good.
Did you figure out which Apollo update you flashed? Did you have Safestrap installed (probably not)?
Cl4ncy said:
Difficult to say, but it doesn't look good.
Did you figure out which Apollo update you flashed? Did you have Safestrap installed (probably not)?
Click to expand...
Click to collapse
apollo-nexus-rom-v2.0.5.zip yep the apollo version and it clearly says not to install with safstrap its a target now i just hate the fact that I have access to the bootloader but cant do anything with it
bowman1966 said:
apollo-nexus-rom-v2.0.5.zip yep the apollo version and it clearly says not to install with safstrap its a target now i just hate the fact that I have access to the bootloader but cant do anything with it
Click to expand...
Click to collapse
¡Ay caramba!
It says not for Safestrap, because it says "This is for users with TWRP installed." in the introduction. Do you have TWRP installed? That would help of course. How did you flash the Apollo ROM anyway?
Cl4ncy said:
¡Ay caramba!
It says not for Safestrap, because it says "This is for users with TWRP installed." in the introduction. Do you have TWRP installed? That would help of course. How did you flash the Apollo ROM anyway?
Click to expand...
Click to collapse
yes I do have TWRP installed,I used it to install the zip file
bowman1966 said:
yes I do have TWRP installed,I used it to install the zip file
Click to expand...
Click to collapse
Then start TWRP (press and hold Volume up and Power On, release when the Kindle Fire logo appears on the screen), connect the HDX to your PC, download the Thor ROM, copy it to the HDX, and flash it in TWRP.
Kinda weird though you can not unlock the bootloader. You sure you have the real TWRP installed?
Cl4ncy said:
Then start TWRP (press and hold Volume up and Power On, release when the Kindle Fire logo appears on the screen), connect the HDX to your PC, download the Thor ROM, copy it to the HDX, and flash it in TWRP.
Kinda weird though you can not unlock the bootloader. You sure you have the real TWRP installed?
Click to expand...
Click to collapse
I sure wish I could start TWRP ,the unit is in a bootloot grey kindle fire screen.Just reboots
bowman1966 said:
I sure wish I could start TWRP ,the unit is in a bootloot grey kindle fire screen.Just reboots
Click to expand...
Click to collapse
Tried to re-flash TWRP via adb? Dunno if flashing Apollo Nexus ROM could destroy TWRP. Do you know which Fire OS you were running when you installed TWRP, and before you flashed the Apollo Nexus ROM?
Cl4ncy said:
Tried to re-flash TWRP via adb? Dunno if flashing Apollo Nexus ROM could destroy TWRP. Do you know which Fire OS you were running when you installed TWRP, and before you flashed the Apollo Nexus ROM?
Click to expand...
Click to collapse
Man its been about a year or so since I rooted , I know I had to roll the update back before I could load the twrp rom.etc. I think it was the first Nex rom that was stable with kdx7
Cl4ncy said:
¡Ay caramba!
It says not for Safestrap, because it says "This is for users with TWRP installed." in the introduction. Do you have TWRP installed? That would help of course. How did you flash the Apollo ROM anyway?
Click to expand...
Click to collapse
thats right I did have TWRP , I used it to install the file.
remote unlock code is not correct, would that mean my bootloader is updated and not repairable at this time? my date size is 0x20000000 i keep sending 536870912 to it, this is the problem correct?
When i create the unlock .img file and flash the device goes through the motion of loading but fails saying the the unlock code is not correct. The file size is 536870912 and the kindle fastboot says its 0x20000000. Is this the problem? Am I using the wrong cuberHDX file or what any help would be greatly appreciated.
bowman1966 said:
When i create the unlock .img file and flash the device goes through the motion of loading but fails saying the the unlock code is not correct. The file size is 536870912 and the kindle fastboot says its 0x20000000. Is this the problem? Am I using the wrong cuberHDX file or what any help would be greatly appreciated.
Click to expand...
Click to collapse
What do you mean the file size is 536870912? The file size of the .unlock file should be 256 bytes.
Did you install all software mentioned in the unlock thread, i.e. Python 2.7 and GMPY2 for Python 2.7?
Yes and Yes, I DID exactly like thread said and I get that file size...... 536870912 doesnt matter what T F I D....either.....I dont understand whats happening here but I guess its just my luck...... Been doing this for about 3 years now I guess Its time for me to BRICK ONE lol......................
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
LouisJ444 said:
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
Click to expand...
Click to collapse
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
LouisJ444 said:
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
Click to expand...
Click to collapse
Remove the verification on the settings, check pic enclosed.
Mannuok said:
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
Click to expand...
Click to collapse
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
kilroystyx said:
Remove the verification on the settings, check pic enclosed.
Click to expand...
Click to collapse
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
LouisJ444 said:
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
Click to expand...
Click to collapse
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
kilroystyx said:
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
Click to expand...
Click to collapse
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
LouisJ444 said:
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
Click to expand...
Click to collapse
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
kilroystyx said:
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
Thanks, that seemed to work!
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
Where I get the original romes of Huawei???
Mannuok said:
Where I get the original romes of Huawei???
Click to expand...
Click to collapse
web version:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
android version:
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
some tips:
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
ANE LX3 no funciona asi,
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
what do you mean by that?
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
ars_chelsea said:
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Click to expand...
Click to collapse
You are right, first post was on the August 20th, at that time I didn't knew that was possible lock bootloader, only after Merlin_99 create that thread on September 12th.
Hi, I'm having a problem with a Mi A3: while executing this command
Code:
fastboot boot twrp.img
I get:
Code:
remote: unknown command
.
I tried also to flash it but I get something like
Code:
recovery_a: not found
.
Any thought on how I can fix it?
bab4 said:
Hi, I'm having a problem with a Mi A3: while executing this command I get: .
I tried also to flash it but I get something like .
Any thought on how I can fix it?
Click to expand...
Click to collapse
fastboot flash boot recovery.img
bab4 said:
Hi, I'm having a problem with a Mi A3: while executing this command
...
Any thought on how I can fix it?
Click to expand...
Click to collapse
1) there is no recovery partition. Boot partition contains kernel and recovery.
2) Mi A3 has broken bootloader and command "fastboot boot image.img" doesn't work. You have to flash the boot image if you want to use it (and then flash previous image back if you don't want permanent custom kernel/recovery).
Thanks to both of you! `fastboot flash boot <image.img>` worked!
bab4 said:
Hi, I'm having a problem with a Mi A3: while executing this command I get: .
I tried also to flash it but I get something like .
Any thought on how I can fix it?
Click to expand...
Click to collapse
Fastboot flash boot recovery.img