Can somebody share their JSN-L21 TWRP Oeminfo zip backup? Many of us are looking to debrand their chinese AL00a to european version but we cannot do anything until we have a dump from JSN-L21. If you have a rooted JSN-L21 with TWRP installed can you please take a moment and upload an oeminfo dump? It will help the community. Thanks in advance!
I send mine to DC, it should come soon on DC tools.
By the way, I rebranded my demo JSN-L21 without the need of an oeminfo.img ... Just with the oeminfo binary.
oslo83 said:
I send mine to DC, it should come soon on DC tools.
By the way, I rebranded my demo JSN-L21 without the need of an oeminfo.img ... Just with the oeminfo binary.
Click to expand...
Click to collapse
Hello, could you please shed more information regarding oeminfo binary method? I read something similar recently here https://www.getdroidtips.com/debrand-the-retail-model-of-huawei-p20-pro/ (P20 Pro debrand), in there this following command caught my attention:
Code:
./oeminfo CLT-L29 C432 hw/eu
It appears to me that oeminfo is an executable, that is, an ARM ELF64 binary file? Up to this point I thought oeminfo is just a partition containing a filesystem with some sort of OEM related files/folders. It is unclear to me where the oeminfo binary can be obtained. Looking forward hearing more from you. How would I get started on Honor 8x?
kylek389 said:
Hello, could you please shed more information regarding oeminfo binary method? I read something similar recently here https://www.getdroidtips.com/debrand-the-retail-model-of-huawei-p20-pro/ (P20 Pro debrand), in there this following command caught my attention:
Code:
./oeminfo CLT-L29 C432 hw/eu
It appears to me that oeminfo is an executable, that is, an ARM ELF64 binary file? Up to this point I thought oeminfo is just a partition containing a filesystem with some sort of OEM related files/folders. It is unclear to me where the oeminfo binary can be obtained. Looking forward hearing more from you. How would I get started on Honor 8x?
Click to expand...
Click to collapse
Check xda's rebrand guides where this info came from.
OEMINFO binary :
https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo
Code:
./oeminfo JSN-L21 C432 hw/eu
oeminfo binary will edit your oeminfo partition.
bricked?
oslo83 said:
Code:
./oeminfo JSN-L21 C432 hw/eu
oeminfo binary will edit your oeminfo partition.
Click to expand...
Click to collapse
Interesting, I tried the above ./oeminfo command and it did rebrand my chinese Honor 8x to JSN-L21, however after a reboot it would bootloop, the phone booted up again after wiping data/caches but the OS was way different now, almost all chinese apps are gone except the 2 "Video - Youku" and "Vmall", also interestingly the build number in Settings now shows "Chipset-miamiC20 8.2.0.001(01Y2).
I ran into an issue, somewhere along the steps I overwrote my TWRP recovery with stock RECOVERY_RAMDIS.IMG because I wanted to try doing wifi restore from eRecovery thinking it would complete the rebrand for me and do a full/proper restore to JSN-L21 now that my Oeminfo has been changed to JSN-L21. eRecovery fails to restore via wifi. My fastboot is showing FRP Lock , I cannot flash TWRP. "Enable OEM unlock" option is greyed out in "Developers options". Previously before running ./oeminfo on my AL00a OEM unlock option wasn't even there. Hi Suite doesn't work. Nothing works, I cannot get past FRP lock.
Code:
fastboot oem unlock xxxxxxxxxxxxxxxxx
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: Command not allowed)
I have tried DC_Phoenix and DC Unlocker but they do not support Honor 8x yet.
Is there a place to purchase FRP unlock key? I might give up on this phone and sell it at loss, maybe someone will buy it for $100 in the state it is now, it has been pain so far, I already wasted money buying expensive bootloader unlock key, I'm coming from Nexus 5, things were so easy back then, OEM unlock and root were supported out of the box, no bullsh*t.
Rebranding your device while keeping the firmware from previous region was asking for troubles...
You should have used the oeminfo binary, while with a nocheck-recovery, and straigh after the oeminfo rebrand, then you should have hwota flashed a firmware from the region you rebranded to...
About your oem-frp option greyed out, staying online for a bit should have un-greyed it in a normal situation.
From there you could:
-use oeminfo binary to rebrand back to original. Then you could do a proper rebrand.
Or
-use a working dload archive for the region you rebranded your device to.
Hey @oslo83, thanks for your input!
I could never get dload method to work, I have tried creating 'dload' folder in root of internal storage and also on the external sd card, I tried it in 2 ways:
/dload/UPDATE.APP
Click to expand...
Click to collapse
and
/dload/update_sd.zip
/dload/JSN-L21_hw_eu/update_sd_JSN-L21_hw_eu.zip
Click to expand...
Click to collapse
I would then hold Vol-down + Vol-up, but I would always get "Software install failed"
HWOTA is a new thing to me, I wasn't aware something like this exists, I will try to research it. Also good to hear that there's a chance for oem-frp to get un-greyed when staying online for some time, do you know if working SIM card is needed or is WiFi connection enough?
Hello! I'm reading through the thread but apparently I'm not as tech-savvy as I thought lol because I'm not understanding.
Could someone PLEASE make a short step-by-step guide on how to rebrand from JSN-AL00a to JSN-L21d? I'm desperate
My phone is bricked, I screwed up (I can't get around FRP Lock even after purchasing FRP Unlock Key)
Rebrand should be easy:
1. Buy bootloader unlock key, reboot to fastboot and issue: fastboot oem unlock XXXXXXXX
2. Flash the TWRP: fastboot flash recovery_ramdisk twrp-kirin.img You will need an OTG USB adapter and mouse, there's no touchpad UI support in kirin TWRP yet
3. Root your phone by flashing Magisk v18.0.zip
4. Follow the HWOTA guide from here: https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283, you will prepare 3 zip JSN-L21 files under /data/update/HWOTA/
and append this to /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
Click to expand...
Click to collapse
5. Rebrand the Oeminfo partition with (download link few post above):
Code:
./oeminfo JSN-L21 C432 hw/eu
6. and hope it flashes.
Code:
adb reboot recovery
Related
Hello! Some day i want to downgrade my Marshmallow to Lollipop. I installed stock ROM to my Honor 5X but in older android - Lollipop 5.1. And I get bricked it. On start on screen i can see first-step logo honor after it i can see second-step honor's logo and here i wait 30 minutes and nothing 45 minutes and nothing. Worse is this I can't back to my stock Marshmallow, when I'm installing my previous ROM - MM i get the same brick on second-step logo. I installed a few more ROMs and nothing. My bootloader is unlocked but when i try to flash cust/system by fastboot appear an error. FAILED (remote: Command not allowed). I think i tried everything, thank for help me.
PS. Sorry for bad English :/
EDIT.1 I tried to use this method from Thread: http://forum.xda-developers.com/honor-5x/help/ive-bricked-honor-5x-t3324225. But the same problem at fastboot.
cust and system won't get flashed on 5X, try force updating it with an UPDATE.APP package for your device.
Put it inside dload folder in root of the Sdcard, and press all three buttons (Vol UP + Vol DOWN + Power) after switching off your phone, to start updating.
Sent from my PLK-L01 using Tapatalk
Thank you. But i tried to get ROM back by UPDATE.APP and when i want to go back to Marshmallow i get second-step honor logo and nothing after it. When i want to get Lollipop i have error "Software can't be installed" - something like that. I heard something about "Transition package" or "Downgrade Package" ? Maybe it can be work. But i can't find those packages for honor 5x KIW-L21.
Bayont said:
Thank you. But i tried to get ROM back by UPDATE.APP and when i want to go back to Marshmallow i get second-step honor logo and nothing after it. When i want to get Lollipop i have error "Software can't be installed" - something like that. I heard something about "Transition package" or "Downgrade Package" ? Maybe it can be work. But i can't find those packages for honor 5x KIW-L21.
Click to expand...
Click to collapse
If the Marshmallow update went through a bit, then you'll need transition package, so take on some pain to find it. It should be out there somewhere.
Sent from my PLK-L01 using Tapatalk
That's maybe becouse i don't remove ROOT and Xposed before installing ROM, how to unroot by TWRP?
Bayont said:
That's maybe becouse i don't remove ROOT and Xposed before installing ROM, how to unroot by TWRP?
Click to expand...
Click to collapse
If you use the this version of TWRP > https://www.androidfilehost.com/?fid=24588212152305793
you can flash system.img and cust.img extracted from your Update.APP with HuaweiUpdateExtractor
fastboot boot twrp.img
then copy the files to the phone
then choose Install / Install Image / system.img or cust.img or recovery.img boot.img ..you choose
Also just saying your have a L21 does not help
is it KIW-L21 C432 or KIW-L21 C185
Now i backed to B130 and i have loop with message Optimizing system... this process going to 100% and phone reboot. And it looping.
Bayont said:
Now i backed to B130 and i have loop with message Optimizing system... this process going to 100% and phone reboot. And it looping.
Click to expand...
Click to collapse
your post tells us nothing about what you did, are we suppose to guess ?
if you successfully flashed System.img - boot .img - cust.img and recovery.img you can now use the dload / Update.app
clsA said:
if you successfully flashed System.img - boot .img - cust.img and recovery.img you can now use the dload / Update.app
Click to expand...
Click to collapse
Done but without any effect, the same problem, stuck at second-step honor logo ;/
Any ideas?
Bayont said:
Any ideas?
Click to expand...
Click to collapse
Well considering I still don't know what you have done. Its hard to guess the next step
Sent from my SM-N920T using Tapatalk
Ok, one more time. When i'm installing any ROM B130 or B330, stock or official doesn't matter, the same problem. After installing rom by UPDATE.APP my phone booting and booting and booting and nothing. When i'm installing rom images by TWRP - boot, cust, system It's the same problem Booting, booting and nothing. When i tried to flash rom by fastboot i have error: FAILED (remote: Command not allowed). I would like to try this: http://forum.xda-developers.com/honor-5x/help/how-restore-cust-partition-t3356769 But i don't know how to access to adb shell: when i type "adb shell" in cmd where i have adb it say to me: error: device '(null)' not found. I don't know what to do more.
How much time honor 5x system is installing?
How i can check my honor is KIW-L21 C432 or KIW-L21 C185?
Bayont said:
How i can check my honor is KIW-L21 C432 or KIW-L21 C185?
Click to expand...
Click to collapse
If you tried to install the wrong Update.app the updater would get to 5% and stop and eventually just reboot. Did you actually watch the update go to 100% and reboot ?
I think i found source of my problem. When i want to downgrade my system was B340.
I read something about downgrade. Without Transition Package I can't downgrade my system I can install only the same (B340) or higher.
This making brick when i'm installing B330 or B140.
Now i'm trying to install OTA B340 and i have another problem,
when i have B330 and installing B340 by small OTA 124MB I have stuck on 5% of installing. It becouse:
EDIT 2 : If you come from B330, don't try to flash the small B340 update as local update has simply been disabled by theHuawei/Honor devs !
Worse, with B340 you won't be able to downgrade to any lower version : at least not easily... INFO FROM: HERE
Click to expand...
Click to collapse
But when i'm installing B130 by TWRP and upgrading to B340 by big upgrade (1,36GB) it's stucking on 0% and i get info: DO NOT UNPLUG....
I think that becouse my version isn't B130 only B140. I'm checking it by DC-UNLOCKER. Output from it:
Code:
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : My Serial
Firmware : KIW-L21C432B140
FB LockState: LOCKED
widevine LockState: UNLOCKED
Bootloader Lock State: UNLOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: Bootloader in UNLOCKED state
Bootloader Version: 001.001.000
Battery state: battery is present
Maybe I should Restore backup from diffrent KIW-L21 by TWRP?
Bayont said:
I think i found source of my problem. When i want to downgrade my system was B340.
I read something about downgrade. Without Transition Package I can't downgrade my system I can install only the same (B340) or higher.
This making brick when i'm installing B330 or B140.
Now i'm trying to install OTA B340 and i have another problem,
when i have B330 and installing B340 by small OTA 124MB I have stuck on 5% of installing. It becouse:
But when i'm installing B130 by TWRP and upgrading to B340 by big upgrade (1,36GB) it's stucking on 0% and i get info: DO NOT UNPLUG....
I think that becouse my version isn't B130 only B140. I'm checking it by DC-UNLOCKER. Output from it:
Code:
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : My Serial
Firmware : KIW-L21C432B140
FB LockState: LOCKED
widevine LockState: UNLOCKED
Bootloader Lock State: UNLOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: Bootloader in UNLOCKED state
Bootloader Version: 001.001.000
Battery state: battery is present
Maybe I should Restore backup from diffrent KIW-L21 by TWRP?
Click to expand...
Click to collapse
Normally restoring a TWRP backup is no different than flashing System.img and boot.img
your bootloop is firmware related ... you need the full B340 package
Yes, you written in Honor 5x Repo:
Waiting for full B340 to appear on Honor support site.
Click to expand...
Click to collapse
At the moment there isn't any full B340 ROM for download. And any OTA B340 doesn't work for me, yes? For example:
B140 -> B340
http://update.hicloud.com:8180/TDS/d...ull/update.zip
changelog
http://update.hicloud.com:8180/TDS/d.../changelog.xml
Click to expand...
Click to collapse
Bayont said:
Yes, you written in Honor 5x Repo:
At the moment there isn't any full B340 ROM for download. And any OTA B340 doesn't work for me, yes? For example:
Click to expand...
Click to collapse
Then you just have to wait
I don't publish the updates I just post them
Sent from my SM-N920T using Tapatalk
I can't back to Stock Lolipop by editing some files or install B340 from B140 by OTA
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
I will try to be brief, I've tried to root my Y6- L22 (2018) Huawei, but I think I flash a bad ROM or got mixup with the TWRP command.
I am now trying to flash the original firmware to have a functional phone. I've tried the method with Huawei Update Extractor and flashing the following:
fastboot flash system SYSTEM.img
fastboot flash ramdisk ramdisk.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
All the process is running smoothly with OKAY everywhere but when I reboot my phone goes to ‘Huawei’(with the lovely and annoying Huawei ring) then it reboot again. I tried different Firmware as I do not have the Built version/regional Number, but none are working.
I've also tried the dload method with the Update.app in the microSD... but getting Software install failed after 5%.
In the meantime I’ve also erase system, and erase cache and install firmware without any success
I would appreciate to have some suggestion or advice from any of you that have faced this issue or know how to get out of this.
Many thanks,
MrKMr said:
I will try to be brief, I've tried to root my Y6- L22 (2018) Huawei, but I think I flash a bad ROM or got mixup with the TWRP command.
I am now trying to flash the original firmware to have a functional phone. I've tried the method with Huawei Update Extractor and flashing the following:
fastboot flash system SYSTEM.img
fastboot flash ramdisk ramdisk.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
All the process is running smoothly with OKAY everywhere but when I reboot my phone goes to ‘Huawei’(with the lovely and annoying Huawei ring) then it reboot again. I tried different Firmware as I do not have the Built version/regional Number, but none are working.
I've also tried the dload method with the Update.app in the microSD... but getting Software install failed after 5%.
In the meantime I’ve also erase system, and erase cache and install firmware without any success
I would appreciate to have some suggestion or advice from any of you that have faced this issue or know how to get out of this.
Many thanks,
Click to expand...
Click to collapse
07/06/19
Hi All, so I've not had any reply, but I keep trying to fix this Y6 phone.
Just answering to myself in case this can help someone; if you happen to lose the Built Number and phone is not working, you can check if retailer are still selling this phone. If yes, it is likely that they have the same built number and regional code. For mine it is ATU-L22 - 8.0.0.140 (C185).
MrKMr said:
07/06/19
Hi All, so I've not had any reply, but I keep trying to fix this Y6 phone.
Just answering to myself in case this can help someone; if you happen to lose the Built Number and phone is not working, you can check if retailer are still selling this phone. If yes, it is likely that they have the same built number and regional code. For mine it is ATU-L22 - 8.0.0.140 (C185).
Click to expand...
Click to collapse
hi. how did you fixed the bootloop?
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
cvpcvp said:
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
Click to expand...
Click to collapse
Hi, look here
If you are running EMUI 9.1, flash C432 oeminfo and use variant with HuRupdater https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538623
https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538725
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
cvpcvp said:
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
Click to expand...
Click to collapse
Can you write down exactly what you did?
What is your version of EMUI?
In fastboot mode run commands:
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
I guess I've stupidly used the wrong command line a number of times to get twrp to run.
fastboot flash system, boot or recovery twrp....
At least it worked with the country ID change ... if only a small consolation for the first
fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.112(C432)
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 8.0.0.112(C432)
cvpcvp said:
ANE-LX1 8.0.0.112(C432)
Click to expand...
Click to collapse
your firmware is incomplete, it must be 8.0.0.143, if I'm not mistaken. Try again Huru method & factory reset in Stock recovery (not in TWRP!).
Or, download Service ROM Link , unpack , there's dload folder in "Software" . Copy dload folder (without unpacking it) to the OTG flash, turn off the phone and press and hold both volume buttons + Power ( this method will lock the BL again).
Thanks for the files. But i get an
Softwaere install failed
Incompatibility with current version.
Please download the correct update package.
EDIT: cant find the firmware version: ANE-L01C185B112 / ANE-LX1 8.0.0.112(C432)
EDIT2: same fail with 8.0.0.178(C432)
cvpcvp said:
Softwaere install failed
Incompatibility with current version
Click to expand...
Click to collapse
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
cvpcvp said:
cant find the firmware version: ANE-L01C185B112
Click to expand...
Click to collapse
Flash only C432 regional variant!
-Alf- said:
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
Click to expand...
Click to collapse
Can you explain me, how i can Boot into twrp without Flash twrp in recovery ramdisk?
cvpcvp said:
without Flash twrp in recovery ramdisk?
Click to expand...
Click to collapse
And what stopping you from doing it?
-Alf- said:
And what stopping you from doing it?
Click to expand...
Click to collapse
Okay, idon't think that's relevant anymore anyway
I found the problem. It was the TWRP version. I took the latest one (twrp-3.5.2_9-0-anne.img) and it couldn't mount the /system partition. Now I took a version from this forum (twrp-3.2.1-0.img), which seems to be specially adapted for the Huawei devices. Unfortunately, it doesn't support OTG, but that wasn't a problem because I moved the files it to the internal memory.
Only with this twrp version could HuRUpdater.zip be executed correctly and all other files just like that. Here, too, I was first asked to press the vol-down button.
After the smartphone finally boots properly, I flash the firmware via dload to lock the bootloader again and do over the Recovery Wipe data / factory reset + cach partition.
Now I'm on version 8.0.0.046(0CXB). Unfortunately the device cannot find a new firmware version and nothing can be updated via HiSuit.
Can you tell me which step I have to take now to get the latest Android version for the device?
Thank you very much so far for your help
cvpcvp said:
Now I'm on version 8.0.0.046(0CXB)
Click to expand...
Click to collapse
Unfortunately, you have incomplete FW there again, I think you're doing something wrong. And until the correct FW is there, you won't be able to receive OTA update or update via dload.
If you have followed instructions to the letter , it must work.
Use this TWRP . ( I don't know why you used TWRP 3.5.2.9, in the guide there is a link to 3.2.1-pretoriano80.). 3.5.2.9 isn't fully compatible with our device.
Try this way out:
- Flash TWRP
- Wipe - format data
- Reboot back to TWRP
- Wipe - Advanced wipe - wipe Dalvik/ART, cache, data, system
- Go back and flash HuRu
Note: the installation of the first file (write radio image...) must take longer, 2-3 minutes, this is proof that the installation is proceeding properly.
Btw, have you tried update via eRecovery & Wi-Fi?
Did it exactly like that. And then the 9.1.0.370 (C432) from the same thread loaded (dload / ANE-L01_hw_eu).
Now i have the firmware: ANE-LGRP2-OVS 9.1.0.370 in the device information.
Unfortunately, there is no further update, but I also don't know whether the current one is already the most recent?
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Can I fix that too? Then everything should be fine as far as possible
cvpcvp said:
ANE-LGRP2-OVS
Click to expand...
Click to collapse
Wrong again .
cvpcvp said:
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Click to expand...
Click to collapse
Oh, it's all clear now
Because this oeminfo is for dual SIM. Oeminfo for single SIM can be found for example here:
https://forum.xda-developers.com/t/c432-single-sim-oeminfo.3873312/
Also update_all_hw.zip file is for ANE-L21, you need ANE-L01, unfortunately, I don't have files for single SIM.
cvpcvp said:
Can I fix that too?
Click to expand...
Click to collapse
Maybe...You have to downgrade to Oreo via HuRupdater using downloaded files, then install TWRP over eRecovery and install stock Recovery.
Download https://androidhost.ru/2zMw and create dload folder .
In TWRP install new oeminfo.img , then go back to the main TWRP's menu, select Reboot > Power off. Use three buttons kombo to flash service ROM.
To be honest, I've never tried a variation like this, so I'm not responsible for this procedure, but it should work. The question is, is it worth it ...
-Alf- said:
Wrong again .
Click to expand...
Click to collapse
Which step is missing now exactly? I followed the steps from you. I also used the files from the other thread that you linked. The single-sim / dual-sim problem is not important either. The main thing is that it works that way too
cvpcvp said:
The single-sim / dual-sim problem is not important either.
Click to expand...
Click to collapse
Are you sure? In my opinion, this is your main problem...
Hello, it's been a while. I sat down again and went through everything. The dual SIM files fold onto a single SIM smartphone. I was finally able to install the update via eRecovery after flashing via TWRP. Then two updates were pulled or installed via Android OS. Now I'm on 9.1.0.132 (C432E5R1P7).