How to read Userdata.bin - Android Q&A, Help & Troubleshooting

hey there.
so here i am, after purchasing a box/dongle of sort , which allowed me to read and backup the partition that i had on the phone i received while not booting.
the phone is an MTK xiaomi redmi note 4 .
i did backup all the partitions before flashing it.
the phone was constant boot looping , was not solved by flashing it (not cn dev firmware or any other firmware) it did not even went to fastboot.
i have heard that after android 5? the userdata.bin were encrypted .
1, im not to sure if the rumors are true.
2, how its possible to decrypt it ?
3, if i flash the same partition to a working phone, would i be able to read the data out of it ? (note that the answer to that question was yes after asking some one, however it seems difficult to understand how, i mean if there is a key to decrypt the partition shouldnt be in the phone itself who encrypt it ?) hope u guys can clarify if its possible to so , or its just BS.
now if the keys are somewhere can i extract them some how and decrypt the partition so i can get the data out ?
i did try to open it with 7z , ftk imager ..
nothing could open this up.
this is how it looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alot of the partitions are fill with
Code:
G..Â.ªÕ.E)ÎJØÁõV
Code:
470305C290AAD5154529CE4AD8C1F556
i mean i can clearly see that its encoded and see the partern .
i did try to flash twrp, but that did not work (because fastboot does not comes up.)
anyhow , this is it.
thanks for the help in advanced .
(in short how can i save the data of this phone, cheers)

@doesitburn
I think a convenient way to remove the encryption from your Android phone is
Go to Settings-->Security
Then under "Credential Storages" click on "Clear all credentials"

jwoegerbauer said:
@doesitburn
I think a convenient way to remove the encryption from your Android phone is
Go to Settings-->Security
Then under "Credential Storages" click on "Clear all credentials"
Click to expand...
Click to collapse
im not sure u read my post ;D
its boot looping and wont turn on properly so cant do that .

doesitburn said:
im not sure u read my post ;D
its boot looping and wont turn on properly so cant do that .
Click to expand...
Click to collapse
It was just a hint for everyone how to avoid the mistake you made. :laugh:
It is the whole point of disk encryption to prevent unauthorized booting. A once encrypted disk/img can't get decrypted by external means as you are trying to do now. May be FBI has the appropriate tools ... That's probably also the reason why Google will, as announced in spring 2019, in the end, remove adb backup/restore from Android.
IMHO you have no chance.

what about flashing the backup into a new phone tho ?
will this help me ?

??

@doesitburn
Propably not
Sent from my Willeyfox Swift using Taptalk

Related

Moto e hangs and Recovery not working

I don't know its a virus or what but suddenly my phone was not responding. I had a doubt that it was a virus so I decided to wipe everything but my recovery also stopped working.
How can I solve this ?
What ROM are you using?I suggest flashing a new ROM This time wipe everything except SDcard if it fails then wipe SDcard too.
nothing is working :/ i tried adb and tried to mount the system but it is failing. tried to wipe through twrp nothing working.
update twrp to 3.0.0 but still same
Now I have done "fastboot erase system" now my os is not starting and i am unable to flash another through adb
Please Any suggestion ?
anyone ?
if u erased system partition then os wont start as u have erased os files. Now the best thing to do is wipe all partitions from twrp. download a new custom rom and flash it through twrp. if u were using stock rom and want it u may get that from forums too. if u have a working nandroid backup ( which i feel u dont have) of previous rom u may try that
i can't format or wipe or do anything from my twrp.
EDIT: you can see it in the video
Don't keep creating new threads for this issue... and don't create threads with profanities in the title and text.
Whether the filter edits your profanities or not, your intention to swear is clear and unacceptable here.
Your other thread has been deleted.
Keep posting your issues within this thread and hopefully someone will help you.
We don't need multiple threads for every issue you progressively find yourself in.
It also makes it harder for someone to help you, if you're constantly creating a new thread for each new issue.
sulfie said:
i can't format or wipe or do anything from my twrp.
EDIT: you can see it in the video
Click to expand...
Click to collapse
Your video is not working...
sorry for that :/ I was frustrated.
look at these pics
adb shell dmesg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Flashed over boot by mistake and cant boot phone. Help!

I was really dumb and wanted to unroot so i decided to flash a stock_recovery.img to my Huawei LYO-L01. When prompted where to i selected boot without looking it up first :crying: Now when i open my phone i get a black screen that says
Android system recovery <3e>
LYO-L21C479B102
Reboot system now
apply update from ADB etc. etc.
I can still boot into TWRP and have a folder with some recovery files from when i rooted my phone.
How can i get my phone back into a bootable state?
I imagine i can just get a fresh boot img form extracting this update.app i see everyone taking about but i dont know where to get an update.app. Can someone point me towards a download?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nafekop said:
I was really dumb and wanted to unroot so i decided to flash a stock_recovery.img to my Huawei LYO-L01. When prompted where to i selected boot without looking it up first :crying: Now when i open my phone i get a black screen that says
Android system recovery <3e>
LYO-L21C479B102
Reboot system now
apply update from ADB etc. etc.
I can still boot into TWRP and have a folder with some recovery files from when i rooted my phone.
How can i get my phone back into a bootable state?
I imagine i can just get a fresh boot img form extracting this update.app i see everyone taking about but i dont know where to get an update.app. Can someone point me towards a download?
Click to expand...
Click to collapse
Its complicated
Sent from my KIW-L21 using Tapatalk
Al Fareed GSM said:
Its complicated
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
I'm kinda desperate to get my phone working agian so any help is appreciated
Can you tell me what makes this problem complicated?
On a side note, what is the intended use of stock_recovery.img and stock.img and where am I meant to flash them?
ok i now see i WAS meant to run "flash recovery stock_revovery.img" or something to that effectin the console but i guess i have bigger fish to fry right now
oh wait i had a backup PANIC AVERTED

MI A3 question concerning TWRP

Hello
I am complete new to the "custom ROM for mobile phones" business.
But i am familiar with Linux based Satellite Receivers where you
also can flash custom ROMS to enhance the functionality.
Or in other words - i know what bricked means.
Anyway what i have done so far:
I have an unlocked Bootloader on my Mi A3.
1st time (non permanent) flash of TWRP-3.3.1-2 into recovery for
a full backup of my phone to Sd-Card.
An encounter with Bootloop made
Now i want to make TWRP permament on both partitions.
But, after flashing TWRP into recovery again, i recognizing that
the "Unmodified System Partition" screen is not apearing anymore.
After my 1st twrp flash, twrp showed me a screen where something
about "Keep System Read only" was explained.
With a slider "Swipe to Allow Modifications".
This screen is not more apearing anymore.
Is this mandatory to go on ?
My goal is to have twrp, magisk and lineageos on my phone.
Last but not least i want to say:
A fantastic source of informations here but overwhelming btw. *g*
* Edit *
32 Views but no answers this could mean that my concern is not clear ?
After entering to twrp on my phone for the first time i saw this screen here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As i explained above, i only wanted to make a backup from my phone
as a fallback if something goes wrong afterwards.
Due to this i pressed ´Keep Read Only´
Don´t know if the ´Never show this...´ was flaged
My thoughts was:
Keep Read Only is okay for now/backup.
And if necessary i can Swipe for modification next time.
My concern is the screen will not showing again.
In case of i HAVE to swipe to make modifications for the next steps,
what i have to do now that this screen will show up again
that i can make the f*ckn swipe ? :angel:
Thank you
Open twrp, goto mount, there's an option for mount read-only system.
m.h.mahadi said:
Open twrp, goto mount, there's an option for mount read-only system.
Click to expand...
Click to collapse
Thank you.

Unable to mount storage. And I can't boot in to system.

please help me I have been trying solutions for 2 months but nothing works. I also tried to do
1 go to wipe
2 go to advanced wipe
3 select date
4 repair or change flie system
5 change flile system ext 2
6 then replace ext 4
but it does not work. when i try to boot in to the system it goes into an infinite loading screen. please HELP (I used google translator because my english sucks)
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
I don't know if my answer came to you so I'll rewrite it
jwoegerbauer said:
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
Click to expand...
Click to collapse
could you tell me how to find the Stock ROM. I need help because I'm not very practical in modding
Boyko99 said:
could you tell me how to find the Stock ROM.
Click to expand...
Click to collapse
GIYF ...
i downloaded this now what should i do? and with what program?
jwoegerbauer said:
GIYF ...
Click to expand...
Click to collapse
i downloaded this now what should i do? and with what program?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Boyko99
Because you avoided to name phone's brand/model in this thread's title you can't really get advised.
Anyway:
Assumed these requirements
got fulfilled, the USB-driver suitable to your phone is installed on PC,
then the basic steps to perform are
1) Unlock phone's boot-loader, if not done yet
2) flash the ROM
@jwoegerbauer
I can't start the phone so I don't know how to do it I'm stuck in twrp because if I try to turn it on it goes into a loop
@Boyko99
My POV:
This is the price that people who think they must improve (?) phone's Android, will say put up a better (?) ROM / Recovery than that what gets pre-installed by OEM/Carrier ( in their R&D department there are certainly no idiots sitting around ), pay.
@jwoegerbauer
i have a note 3 its the worts rom of all

Stuck on bootloader, unable to enter recovery

Appreciate anyone who can help! I was tooling around trying to unlock my AT&T locked SD1 but was basically unable to get it working. So I decided to undo everything with a factory reset and relock the bootloader...and that's when I bricked my device.
I am unable to go past the bootloader screen and unable to either Start the device or enter Recovery Mode.
Not sure how else to proceed.
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Renate said:
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Click to expand...
Click to collapse
Unfortunately, no. Adb is no longer recognising the device and I'm stuck in boot select screen unable to even Start or enter Recovery Mode.
Bootloader is currently locked.
Not that it does a lot of good, but you can see fastboot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I see.
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
JimmyRespawn said:
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
Click to expand...
Click to collapse
I was worried you'd say something like that. Down in the dumps.
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Sharkam said:
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Click to expand...
Click to collapse
What in the name of all things holy?! Man, I'm gonna have to look deep into this and figure it out. Problem is, I am not nearly as smart as that guy which is itself gonna be a huge challenge. That said, I do have all the patched imgs on my desktop...so perhaps there is a way back. IF I can figure out the process as laid out here.
Thanks for this pal at least it helps.
im here with you i need bootimg from 2022.823.41 ota went threw now stuck.. im on the duo 2
This is the duo 1 forum.
There is a duo 2 forum, but it is less active.
did u tryed
`fastboot reboot recovery`
yes .. it just falls back to bl .. I need the boot.img from 2022.823.41 update . I tried to capture the link but it flashed before I told it.
this is the duo2 btw
Me too I have the same issue. Did you found how to fix it ?

Categories

Resources