yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] pndwal:
You may have used

EFS Backup

or

Partitions Backup & Restore

.

Partitions Backup & Restore is on playstore. Info following. Xda here:

https://xdaforums.com/android/apps-games/app-partitions-backup-t3003599

He says "This is an improved and more generic implementation of EFS Backup.

This application was made to be a generic solution for all Android devices, it does NOT use any static/hardcoded block numbers."

Hope it's useful. PW.

☆Root required☆

Partitions backup detects all your device partitions, including Bootloader, Kernel (Boot) and any sensitive partitions like the EFS (IMEI) and Modem partition, and let you easily make a backup of them.

Partitions restoration is also supported, but recommended only for small partitions (Boot, Recovery, EFS, Modems...)

Features:

☆ Backup to SdCard or External SdCard

☆ Restore raw partition images

☆ Highlight all related IMEI/EFS partitions

☆ Support 3 backup formats :

☆☆☆ Raw partition image (Can be restored through the application)

☆☆☆ Tar archived image

☆☆☆ Compressed GZ image

Notes:

☆ The backups are saved on /Sdcard/PartitionsBackups.

☆ Do NOT leave the EFS/Modems backups on your Sdcard, make sure you keep them on a safe place

☆ It supports stock and custom Roms (CM, Omni...)

☆ Do NOT use the restoration feature for tests purposes, it is recommended to use it for small partitions only (Boot, Recovery, EFS, Modems...),

you can restore other partitions backups with Fastboot, adb dd, Odin or any other flashing tool

depending on which device you are using.

☆ Partial support for Mediatek devices: some partitions are not displayed because they do NOT have a specific block number for device mapping.

Bugs reports::

http://xdaforums.com/android/apps-games/app-partitions-backup-t3003599
[Android Q&A, Help & Troubleshooting] kyosuke83:
[MENTION=4479868]desalesouche[/MENTION]

Sorry for delay about my reply.

I've set the value as fluence.

Now speakerphone works but other people who call y550's owner can listen his voice (echo effect):(
[Android Q&A, Help & Troubleshooting] mehdi554:
i wonder why is it so hard to share the file i need :(
[Android Q&A, Help & Troubleshooting] pndwal:
Probably people are worried about sensitive info on oeminfo partition / "file", as I am. Apparently IMEI & SN numbers unique to your phone are stored there, so prospect of another phone sharing ones id is a worry. And if regions/ carrier info/ other unique settings are stored here, LO2 file may be no good on LO1 etc. (So before messing with anything likely to change partitions not normally altered by ROM or Recovery, unique backups should be made.) Found the following info for example:

"OEMINFO partition is partition 5, it is what we used to called IMEI partition. That partition also stores your SN (the one you find on the back of the phone when you remove the battery). The unlock code depends on both, your imei number and your SN, so if they don't match it won't work..."

"Anyway, read some where that the OEMInfo pretty much is a data storage partition, that it stores different regions/carrier info/settings of the phone. So, how many unique info is stored here, I am not sure, maybe IMEI is not here, but if other MT2L03 image is not same as mine, I am not comfortable to share mine. Sorry."
[Android Q&A, Help & Troubleshooting] mehdi554:
Yes. I read about it of course before I post here. Here on xda.

In huawei phones oeminfo contains region information. It doesn't have imei or sn in it. It's about which rom you can dload. There are several threads on xda that people share their oeminfo for those who can not find the rom suitable for dload or those who want to rebrand some carrier phones. It certainly doesn't have sensitive information.

https://xdaforums.com/huawei-p9lite/help/guide-to-changing-oeminfo-t3537434

https://xdaforums.com/mediapad-m3/help/oeminfo-collection-t3518535
[Android Q&A, Help & Troubleshooting] pndwal:
So are you trying to dload for LO1, 2, or 3? And did you flash back to stock recovery for dload?
[Android Q&A, Help & Troubleshooting] mehdi554:
I'm trying to dload L01. Yes I flashed stock recovery. I even flashed stock system, boot, userdata images from fastboot.

I tried every stock rom here: https://files.fm/u/gdmxigp

And every other stock rom I could find over Internet. And they all end up with error update.app is invalid package

So I'm sure now that it has something to do with my phone region settings which are stored in oeminfo and I need to change it to something else. Preferably eu region.
[Android Q&A, Help & Troubleshooting] pndwal:
You're probably right re. sensitive info.

I recall when I previously tried dload it failed with errors to, and I gave up. I put it down to peculiarities with LO2. (May have been trying with update.app for LO1, custom recovery, or other oversight.)

Did you edit /update /change /hack or alter oeminfo partition (or IMEI, or other partitions) in any way? If not, I can't see why it would be corrupted / why this would be the cause of errors . . .

Not sure oeminfo for LO2 won't cause more problems for you though. (Region would certainly be wrong.) Probably better off getting oeminfo for LO1 from another user. Let me know if you still want mine. PW.
[Android Q&A, Help & Troubleshooting] mehdi554:
i didn't edit anything . my phone was not behaving well after 2 years of use so i decided to dload. which was unsuccessful. then i unlocked bootloader and installed custom roms. which all of them even stock ones worked well for a week or 2 then stuck at boot logo . so i thought maybe dload would be only option to fix it if it's not hardware. you can send me your oeminfo to try. i tried an oeminfo file from honor 4c earlier ! which didn't work but my imei and sn are still there.
[Android Q&A, Help & Troubleshooting] pndwal:
Please PM me email address and I'll send it. Interested to know if it works. PW.
[Android Q&A, Help & Troubleshooting] pndwal:
Oeminfo sent in Email. Zipped as 64MB uncompressed.

As I mentioned, "when I previously tried dload it failed with errors to, and I gave up. I put it down to peculiarities with LO2. (May have been trying with update.app for LO1, custom recovery, or other oversight.)" Never tried again, so never had success with dload. I may have same problem you have with phone. (May be a common one.) No problem with normal flashing though.

Let us know how you go with it. PW
[Android Q&A, Help & Troubleshooting] mehdi554:
well i just realized copying the oeminfo file doesn't work . you have to dump the partition using adb shell while in recovery.

adb shell

dd if=/dev/block/mmcblk0p16 of=/sdcard/oeminfo.img

to really get it. i mounted the dumped image of mine and there were some logs in it that i attached. but according to that log my region is CUSTC185D001 and i have tried that rom yet it doesn't dload. also copy and pasting the oeminfo file didn't replace it. there should be a way to flash it with twrp since in the fastboot it gives command not allowed error.

i think once i can flash that partition with another dumped image that can dload, this problem gets fixed. :(:(:(
[Android Q&A, Help & Troubleshooting] mehdi554:
hard bricked phone :( now it says Qualcomm HS-USB QDLoader 9008 in device manager.

I could unbrick it with QFIL , but we don't have the right firmware as it needs some xml files written for y550 . :(

can't do anything about it now i guess.

edit: used this method : https://xdaforums.com/showpost.php?p=70525449&postcount=4560

now the phone turns on and goes to fastboot but it says phone locked and can't do anything

anybody knows what to do ? :(
[Android Q&A, Help & Troubleshooting] Mateox7:
Big thanks [MENTION=4479868]desalesouche[/MENTION] for your work :)

-sounds videorecording work perfect now

-sound in voicecall also work very good

-safetynet work

-wifi signal is good now

-unfortunately when mobile data on, phone won't stop restarting

I'm waiting for next update :D
[Android Q&A, Help & Troubleshooting] brius56:
Here are some logs for the mobile data issue:

View attachment 4262513

View attachment 4262514
[Android Q&A, Help & Troubleshooting] desalesouche:
please use older boot.img in last rom to fix reboot
[Android Q&A, Help & Troubleshooting] pndwal:
Personally, I'd go back to post #5643 and give DC Phoenix a go if NV and OEM info secure zones were not damaged earlier.

(Repairs Huawei firmware problems (Bricked, Bootloop, stuck on Fastboot mode etc.)

Can write firmware by fastboot with locked bootloader and locked FRP!

Huawei Firmware UPDATE.APP file direct writing in fastboot

Full erase and write full factory images in fastboot (DC Unlocker factory images in format DGTKS)

Any rom writing in fastboot without signature and compatibility checking! . . ."

You'll need to fork out 15 'credits' (=15 EUR) with PayPal etc to do this, but may be otherwise pain free.

(I've used DC Unlocker sim unlock and generate bootloader code (when Huawei club bootloader generator wasn't working) (both 4 credits /EUR) as their charges were far more reasonable than others, and had no problems. Never tried DC Phoenix, but has good reputation)

If your phone is missing IMEI/SN or NV / OEM info damaged, repair and restore them with HCU client. Need to spend 8 credits (8 EUR) for this.

Just a suggestion. PW.
[Android Q&A, Help & Troubleshooting] mehdi554:
Well unfortunately due to sanctions can't spend money on it (living in Iran). So I have to give up on this it seems.
[Android Q&A, Help & Troubleshooting] Mateox7:
Thank you, everything working now :D
[Android Q&A, Help & Troubleshooting] YouSaid:
Hi, I ave just jumped into this with an old phone I had lying around.

Thanks for the builds and work - much appreciated and it has given me a newfound respect for this phone.

For me with the older boot.img (0824) touchscreen does not work and the newer boot.img (0826) it keeps restarting.
[Android Q&A, Help & Troubleshooting] brius56:
Try it with this one: https://xdaforums.com/showpost.php?p=73533452&postcount=5608 :good:
[Android Q&A, Help & Troubleshooting] YouSaid:
Thanks!

That worked a charm
[Android Q&A, Help & Troubleshooting] kyosuke83:
[MENTION=4479868]desalesouche[/MENTION]

Any idea? Thanks
[Android Q&A, Help & Troubleshooting] desalesouche:
not for the moment....excepted updating audio in kernel. but not easy.
[Android Q&A, Help & Troubleshooting] pndwal:
That's a shame.

Are you able to unlock bootloader again?
[Android Q&A, Help & Troubleshooting] mehdi554:
no it says invalid key. i think i should unlock with the code of the person who made the emmc dump.
[Android Q&A, Help & Troubleshooting] pndwal:
Originally Posted by mehdi554

Hard bricked phone - now it says Qualcomm HS-USB QDLoader 9008 in device manager.

Can't do anything about it now i guess.

. . . used this method :

https://xdaforums.com/showpost.php?p=70525449&postcount=4560

Now the phone turns on and goes to fastboot but it says phone locked and can't do anything.

Anybody knows what to do ?

Are you able to unlock bootloader again?

No it says invalid key. i think i should unlock with the code of the person who made the emmc dump.

Looks like he's flashed your emmc file from post #4546. Does he now need your bootloader code to unlock bootloader? (Any suggestions re. how to unbrick / fix corrupted partitions?) PW.

---------- Post added at 02:18 PM ---------- Previous post was at 01:52 PM ----------

I'm assuming you flashed [MENTION=4479868]desalesouche[/MENTION]s emmc file from post #4546. Did you backup any partitions this overwrites, or backup your SN / IMEI information?

Clue:

[MENTION=4479868]desalesouche[/MENTION] wrote:

i think people should begin to make back up of their imei....

i think also that full emmc.img will be really usefull to save many y550 from brick.

but it will needed to have an imei backup to restore it otherwise many device will have same imei..... lol

Seems this is not full emmc.

You probably now have different IMEI and/or SN.
[Android Q&A, Help & Troubleshooting] mehdi554:
But this is only on sd card not on my phone, because if I remove the sd card phone doesn't turn on.

Am I right?
[Android Q&A, Help & Troubleshooting] pndwal:
I had a quick read regarding the Fastboot using emmc image method here:

https://xdaforums.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112

I'm now understanding you didn't flash this image (phone just accesses data from SD in order to boot), but please can you clarify:

What you did flash (and which partitions)

when you entered Fastboot this way.

Also,

was bootloader locked

when you first did this?

And previously,

what did you flash

(and which partitions)

or do that corrupted your phone's native emmc data

in the first place.

Thanks, PW
[Android Q&A, Help & Troubleshooting] mehdi554:
i just flashed boot.img and system.img of stock rom in fastboot . then the phone didn't boot . and when i turned it off , it didn't turn on again. i had my bootloader unlocked before this. so i tried this emmc image file and phone turned on. but says phone locked and i couldn't unlock it with my own unlock code.

there are 2 possibilities the way i see it either phone's hardware is ok but bootloader partition is messed up . or that the phone's emmc is down completely.
[Android Q&A, Help & Troubleshooting] pndwal:
Assuming bootloader was unlocked when you first entered Fastboot using emmc SD image method, I guess you flashed other image / images containing IMEI or bootloader info,

so may need bootloader or IMEI compatible with these,

not with emmc data.

I'm also assuming the only way to boot anything is now with emmc on SD. Correct? PW

---------- Post added at 11:53 PM ---------- Previous post was at 11:27 PM ----------

I see, so never was unlocked in Fastboot using SD emmc method, and nothing flashed using this method, or since, correct?

You may be right re. 2 possibilities.

Perhaps bootloader lock is associated with emmc image when booting this way. Guess a different emmc dump may help, or you may need unlock code to suit this. I don't know. Hopefully someone else knows more. (No other way of booting works?) PW

---------- Post added 06-09-2017 at 12:18 AM ---------- Previous post was 05-09-2017 at 11:53 PM ----------

As I mentioned, DC Phoenix claims:

"Repairs Huawei firmware problems (Bricked, Bootloop, stuck on Fastboot mode etc.)

Can write firmware by fastboot with locked bootloader and locked FRP!

Huawei Firmware UPDATE.APP file direct writing in fastboot

Full erase and write full factory images in fastboot (DC Unlocker factory images in format DGTKS)

Any rom writing in fastboot without signature and compatibility checking! . . ."

This would indicate at least some flashing still possible with locked bootloader (assuming knowledge of correct protocols). Might also be worth persuing. PW
[Android Q&A, Help & Troubleshooting] mehdi554:
Yes a different emmc might help. Maybe a full dump!

I'm trying to ask some friends to help with dc Phoenix account.

Maybe I can give it a go
[Android Q&A, Help & Troubleshooting] pndwal:
Good. May also be possible to flash with locked bootloader some other way if DC can do it.

Otherwise someone could set up DC account for you using your email, apply credits, send you login details and you're good to go.

Of course, if your phone is missing IMEI/SN or NV / OEM info damaged, you'll also need to repair and restore them with 3rd party software like HCU client, but with HCU you can use DC credits also.

Let me know if any problems and I'll help. I'm interested to know how these softwares work on Y550. PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
thanks for donation

hi all, i would like to thanks crazy donator [MENTION=6178818]SoulInfernoDE[/MENTION] for donation. :good:

regards.^^
[Android Q&A, Help & Troubleshooting] sharrymz:
Y550-L01 emergency data Problem

Internal storage damaged and show two options which is not working.

My phone not going in fastboot mode. when click on vol- and power it goes in diagnostic mode 9006

is there any solution.

Where is Y550 emmc image download link.

i want to try sd card method.
[Android Q&A, Help & Troubleshooting] pndwal:
1) If storage really damaged, I doubt it.

2) [MENTION=4479868]desalesouche[/MENTION]s emmc file is @ post #4546 (mentioned on last page). But [MENTION=6090336]mehdi554[/MENTION] has been having problems with locked bootloader since using it. Be careful! (Read related posts in last few pages here.) PW.
[Android Q&A, Help & Troubleshooting] mehdi554:
dc phoenix didn't work.
[Android Q&A, Help & Troubleshooting] Saint_13:
[MENTION=4479868]desalesouche[/MENTION]

battery consumption is very high , i'm using Lineage OS 14.1-20170819, phone is always awake ! look at screenshot. what should i do ?
[Android Q&A, Help & Troubleshooting] Saint_13:
Ok , I found the problem . app2sd was the problem
[Android Q&A, Help & Troubleshooting] felix-development:
hi

just have one question.

where i can find sources for y550 to compile roms ?

Gesendet von meinem BLN-L21 mit Tapatalk
[Android Q&A, Help & Troubleshooting] pndwal:
That's a shame. What happened? Did you get any error messages/ clues re. problems? (Also, any indication if your suspicion phone's emmc may be 'down completely' could be correct?) PW
[Android Q&A, Help & Troubleshooting] mehdi554:
it said about something like "can't get fblock" or something like that. to me it seemed it was trying to write on the sd card not on the phone since it detected the SN of a phone that didn't match mine. it was from emmc image i guess

---------- Post added at 05:57 PM ---------- Previous post was at 05:41 PM ----------

i think i might need a full emmc image to maybe boot the phone and realize whats wrong
[Android Q&A, Help & Troubleshooting] fwiep:
Thank you very much.

The new(est) ROM with the older BOOT.IMG is the perfect combination.

My Y550-L01 is stable. Calls, audio, wifi, bluetooth, camera, rooting - it all works.

Most of all, the august security patches are in there. Well done.

Hope to see them coming every month :)

FWieP
[Android Q&A, Help & Troubleshooting] kekkkko:
Is there a new twrp for my y550 -L01? Are there rom with android 8?
[Android Q&A, Help & Troubleshooting] blairfancy:
I use also apps2SD but no battery drain issue (apps2SD version is 13)
[Android Q&A, Help & Troubleshooting] kekkkko:
why when I format sd with App2SD , sd card became protected by writig?
[Android Q&A, Help & Troubleshooting] blairfancy:
Had also some issue with apps2sd formating tools but with ubuntu gparted tool no issue
[Android Q&A, Help & Troubleshooting] Saint_13:
it's really confusing , i have disable keep awake options but phone is always awake , i hadn't issue before ! app2sd was not the problem ! i'm still searching why phone never goes to sleep mode. :rolleyes:

maybe installing new rom will help, but i'm really tired of changing roms. :crying:
[Android Q&A, Help & Troubleshooting] pndwal:
That may be right. Guess phoenix has problems when encounters problems with SN, IMEI etc.

Not sure how IMEI/SN (NV / OEM info) repair and restore works in HCU client. (Might be worth investigating as you can use DC credits, and you have account access now).

Sorry, I'm out of new ideas. Hope you can sort it with full emmc or other. PW
[Android Q&A, Help & Troubleshooting] pndwal:
I've just changed to latest ROM (with older boot.img). Battery life improved (especially hi drain with wifi hotspot on -gone now), camera good (panorama no longer freezes phone), WiFi good, bug-free so far!

I no longer use App2SD since N. Format SD as internal, migrate data (frees up phone memory for system and system apps only basically), moveable apps automatically go to SD. Problems with this in M gone. If Dev hasn't enabled 'move apps to SD', can 'Force allow apps on external' in Developer Options (Makes any app eligible to be written to external storage, regardless of manifest values). Seems perfect out-of-the-box solution for low memory phone! PW.
[Android Q&A, Help & Troubleshooting] blairfancy:
Thanks for information about adoptable storage, probably i ll try on next release. Just one question about apps on this storage when you load new rom, reinstall is required or not?
[Android Q&A, Help & Troubleshooting] kekkkko:
I format sd as internal memory of my phone,if I install a different rom will I lose everythings?
[Android Q&A, Help & Troubleshooting] pndwal:
With Oct-N weekly updates retained all settings incl. accounts settings and adopted storage encryption key so SD data was retained.

I'm not 100% sure if this will work with any ROM due to secure encryption used to protect users data on SD (which basically becomes phone's encrypted internal memory when formatted as adoptive storage, so in lost / stolen pin protected phone, SD data is inaccessible without pin, and lost forever without phone)

Recently, I've been been doing clean flashes and starting with wiped SD to avoid problems, but previously retained SD data / apps between flashes with OctOs with no problems.

Dirty flash may leave data / apps on adoptive storage accessible (did work with OctOs), but may leave orphaned data there to.

If you want to try leaving apps only, may be best to back up and remove photos etc, migrate data back to internal to clean up SD (ie leave apps only) before flashing new ROM. Of course, this would remove app data.

You may need to restore adopted storage encryption key in order to use SD data / apps from previous ROM, especially if clean flashing. (This will apparently work on same device only, ie data on SD is lost forever if used in different device, even with saved encryption key.) So be sure to save key before flashing. Key in data/misc/vold. Restore to same location if new ROM generates new key.

I posted this info previously (post #5140):

Oct-N utilises adoptive SD storage properly (unlike marshmallow), allowing most downloaded apps to be moved to SD (app developer dependant) in FULL, along with all user data. - No more need for link2sd or apps2sd when running out of space for apps! (This is the best feature for me. Recommend fast SD card for phone-mem-like performance. I use 80MB/s SanDisk Ultra 64GB SDXC. One app not to move: ES file Explorer if you use root explorer [Loses root explorer permission when on SD card].)

. . . updates now retain all settings . . . so no longer need to . . . restore saved adopted storage encryption key in order to use SD data. (I'm still saving this for my peace of mind however. Key in data/misc/vold).

Hope it helps, PW

---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------

Probably not (As I mentioned, Oct-N weekly updates retained all settings (from build, 20170324), so no longer needed to reinstall accounts, or restore saved adopted storage encryption key in order to use SD data. (I still saved this for my peace of mind however. Key in data/misc/vold)), but I would backup photos / important data before flashing.

See reply above to [MENTION=4165581]blairfancy[/MENTION]. PW.
[Android Q&A, Help & Troubleshooting] kekkkko:
I don't understand this expression:eek:ne app not to move: ES file Explorer if you use root explorer [Loses root explorer permission when on SD card].). . . updates now retain all settings . . . so no longer need to . . . restore saved adopted storage encryption key in order to use SD data.

-

what have I to do?