Hello there !
I have an issue where I want to go back to Windows from fastboot as explained in this post :https://forum.xda-developers.com/no...nt/restore-windows-phone-8-installed-t3608223 .
I have my TZ.bin and other necessary files, but when trying to flash them with the command "fastboot flash partition TZ.bin", I get this error message:
{
"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"
}
Is there someone here smarter than me who knows how to solve that ?
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
TBM 13 said:
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
Click to expand...
Click to collapse
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
r0mDU19 said:
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
Click to expand...
Click to collapse
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
TBM 13 said:
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
Click to expand...
Click to collapse
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
r0mDU19 said:
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
Click to expand...
Click to collapse
Sorry, but i don't remember.
TBM 13 said:
Sorry, but i don't remember.
Click to expand...
Click to collapse
No problem, thanks again for the advices ! :good:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
r0mDU19 said:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
Click to expand...
Click to collapse
Same problem than today, replace partition with the partition name (TZ in this case).
Related
Haret photon 7227 is not possible to open the file...?
rui_sandra said:
Haret photon 7227 is not possible to open the file...?
Click to expand...
Click to collapse
try with a hammer...
or read [TUTORIAL] Install Android on HTC HD Mini
I followed this tutorial but from this error ...?
Thanks.
If you want Android on your phone HTC HD Mini, Download the Cotulla's Android 2.1 and you extract the files.. these files will are together and you bring them to the root of SD card and format with FAT32 before bringing files, And when you want to start android tap on named HaRET, That is it, and if you see doesn't work it's because if SD is not enough fast or bad SD.
This files isn't about open file or something else, it's only boots to Android Operation System
Please everyone before asking, see the page, you see it, just ask about haven't asked yet....
iPlasm said:
Please everyone before asking, see the page, you see it, just ask about haven't asked yet....
Click to expand...
Click to collapse
Before I ask any questions I have read and did everything in this tutorial but it's always error opening the photon Haret 7227.
You must be the most intelligent of the forum, you should know everything.
Thanks.
Well then, Well done if you did read all of it.
We will like to know all the problems of this android, but not always same, and explain full your question, I mean.... for example what do you mean error of this?? you mean when you tap on HaRET shows you error or something?, so here you must say i have bring files to SD also to know us what have you did.. As the page of Android mini... you see some questions are same...
I think i have the same problem , after i had clicked on HARET there comes the sentences : HaRET: Booting Linux. and this is on my screen and then i must take my phone off
This is my problem.
Thanks.
{
"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"
}
rui_sandra said:
This is my problem.
Thanks.
Click to expand...
Click to collapse
lol .......
Because your SD Card is not signed with a trusted certificate & So it's fails to load. so maybe you formatted by Computer's Format Tool.
And There're two ways to fix this, just do one of them: number one is easier, but number two can be formatted with PC's anytime without this stupid certificate;
Number 1' Format your SD by the Windows Mobile Default one; (Start>Tools>Format SD) Done!
Number 2' Read this http://forum.xda-developers.com/showthread.php?t=720782 After these reading and doing steps you are ready to run HaRET.
And here will be Answered your Question! beside this question has been asked in the Cotulla's Android Page, but no problem... and You're Welcome
bye
Solved my problem.
Thanks.
You know where I can find solution to get ip address by wirelless (wi-fi)?
Thanks.
Right, this is very weird...
I made a Nandroid backup (compressed) on TWRP for this first time, it completed successfully and then I powered off and turned the Nexus 4 back on. However to my surprise, I could not find the backup on my SD card. I checked everywhere (data/media...TWRP folder...etc). I even checked the entire phone (with root explorer enabled), nothing. However the backup was successful because my Available Space has fallen by roughly 1gb, the size of my backup. Does anyone know whats going on here?
Thanks in advance, really appreciate your support.
esskayy said:
Right, this is very weird...
I made a Nandroid backup (compressed) on TWRP for this first time, it completed successfully and then I powered off and turned the Nexus 4 back on. However to my surprise, I could not find the backup on my SD card. I checked everywhere (data/media...TWRP folder...etc). I even checked the entire phone (with root explorer enabled), nothing. However the backup was successful because my Available Space has fallen by roughly 1gb, the size of my backup. Does anyone know whats going on here?
Thanks in advance, really appreciate your support.
Click to expand...
Click to collapse
it should be in the twrp folder, backups..
{
"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"
}
Hmm, unfortunately I don't get that. This is what I see.
Could it be because I am using a theme on my TWRP (the Holo one btw, which no one else has reported a problem on)...
Edit: Okay, I think I solved it...I went onto the root of the phone again this time, searched the data folder and was able to find Media -> Backups (see below). Why is that it appears here rather on the SD card data folder?
esskayy said:
Hmm, unfortunately I don't get that. This is what I see.
Could it be because I am using a theme on my TWRP (the Holo one btw, which no one else has reported a problem on)...
Edit: Okay, I think I solved it...I went onto the root of the phone again this time, searched the data folder and was able to find Media -> Backups (see below). Why is that it appears here rather on the SD card data folder?
Click to expand...
Click to collapse
maybe because you compressed it? i dont compress mine.
Thanks for the help Simms, but after digging around on XDA forums, I found the cause and the solution (posted here):
jasonwc said:
There was a weird bug with TWRP that put the FIRST backup in /data/media/TWRP/backups (read: wrong). After rebooting the recovery, all future backups will go into /mnt/sdcard/TWRP/backups, which is where you want them.
Here's what I think happened:
1) Your first backup was stored in /data/media/TWRP which is not where TWRP looks for backups. So, TWRP showed no backups.
2) You ran a second backup which showed up correctly in TWRP, and was stored in /mnt/sdcard/TWRP/backups.
3) You renamed the most recent backup, and then checked /mnt/sdcard/TWRP/backups, and assumed the renaming actually moved the folder. I don't think it did.
Click to expand...
Click to collapse
Hi,
I'm very desperate and I know I should've backed up everything but now I'm in a situation where I'm wondering if there's any way to mount the block and recover my photos. Please let me know. I would really appreciate it.
I'm on stock Lollipop with root.
Thanks in advance.
I've tried this but I can't tell what I'm doing wrong; I know I'm getting warmer: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
taney said:
Hi,
I'm very desperate and I know I should've backed up everything but now I'm in a situation where I'm wondering if there's any way to mount the block and recover my photos. Please let me know. I would really appreciate it.
I'm on stock Lollipop with root.
Thanks in advance.
I've tried this but I can't tell what I'm doing wrong; I know I'm getting warmer: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
Click to expand...
Click to collapse
{
"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"
}
I got pretty far but still aren't able to recovery anything from DCIM. Is that separate from userdata partition? Does anyone know?
Trying new route via:
http://www.df.lth.se/~jokke/androidfilerecovery/
Well, you could try some "deleted files recovery app" from google play.
The photos might still be there somewhere. If not overwritten by some other file that needed that space.
GDReaper said:
Well, you could try some "deleted files recovery app" from google play.
The photos might still be there somewhere. If not overwritten by some other file that needed that space.
Click to expand...
Click to collapse
Right now, it appears that DCIM is not on the same partition as "userdata". On my i9505G, the userdata partition is mmcblk0p28. I was able to restore other photos on the /sdcard but none of the DCIM files. I feel like these files might be stored on a different partition but unable to find any reference online. Anyone have ideas?
All I know is that the s4 uses its internal storage to emulate an sdcard.
And this causes problems with some apps, like apps2sd. Maybe it also causes your issue.
Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
legitscoper said:
Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
Click to expand...
Click to collapse
It's in param partition.
It is empty ;(
It is in dev/block/bootdevice/by-name/param
I have made dd if=/dev/block/bootdevice/by-name/param of=/sdcard/param
I opened it in hexview and it has almost only 00 everywhere
and has 10mb
It's because you have a raw image of that whole 10MB partition while maybe only 1MB is used.
It'll send you it
I can take a look at it when I get home in a few hours.
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
{
"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"
}
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
legitscoper said:
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
Click to expand...
Click to collapse
I guess Odin would never allow the modified bootloader to flash. May be possible with the modified version of odin, I don't know..
I assume by the pictures I found that the background will be black by defauld no matter what.
There's no whole bootlogo, only the "Samsung galaxy A5" and "Powered by android" logos as small images.
Here I have extracted the "powered by android" logo from aboot. Only problem is I don't know what the file is named inside aboot.
If I name the new image something else than it should be and overwrite the old one, it would probably become bricked.
At best there would still be download mode.
Even if I did know the filename I would have to be precise in everything. Same resolution(304x81), same dpi(96dpi), same bytesize(6157 b), etc. and insert/overwrite at the exact same place. One faulty byte anywhere and chances are that the phone may never boot again unless you can get a jtag and reflash it.
It feels a bit risky just to change those two small images, and still be limited to only black background with new text at the same places as the original.
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
legitscoper said:
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
Click to expand...
Click to collapse
I would not try to change size or dpi in bootloader. I've made mistakes before when I modded param partition on another phone and it ends in no boot to system or recovery, or loop, and only download mode available. Param is like an image cache for bootloader, but here the images are inside bootloader which means that if something goes wrong it probably won't boot at all.
I think 00033.jpg was just what the program i used named it when it extracted the images.
That image was the second I found by searching for ffd8 which always is the beginning of a .jpg in hex, then make a search downwards for ffd9, which is the end of a .jpg. The first I found was the 5. It's a bit of trial end error when working in hex without knowing which image is what
The aboot I used was extracted from firmware.
And I will be unable to go to download mode it that "faulty byte" will occur?
I think thread is to close, I don't want to have that level of risk and with that limitations
tys0n said:
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
View attachment 4094675
Click to expand...
Click to collapse
Program name?
Hello
I am trying to flash the global ROM on my K20/Mi 9T, but I am getting a weird error message saying 'antirollback check error'.
I know what anti-rollback is and I can check the ARB value with fastboot, and it was nice and clean 1.
I have seen a xda thread that someone succesfully flashed a rom with anti val = 0 to a device with anti val = 1.
{
"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"
}
I don't get why the error message is showing up, and I am really frustrated with it
Please help!
Install MiFlash at C:\MiFlash and try again. I got this error once and it was due to the fact that MiFlash has problems with paths containing spaces.
Yup, flashing from C:\ is what fixes this. Horrible programming, had to mess around for a whole day back when I encountered this error.
epraes said:
Install MiFlash at C:\MiFlash and try again. I got this error once and it was due to the fact that MiFlash has problems with paths containing spaces.
Click to expand...
Click to collapse
Man I installed MiFlash in C:\ as u said. But still I'm getting this error. I also tried flashing all the files in 'images' folder manually using fastboot and then flashing the file using miflash. Still the antirollback check error persists. Any solution?
I really don't know what advice to give you. Maybe use a different version of MiFlash?
epraes said:
I really don't know what advice to give you. Maybe use a different version of MiFlash?
Click to expand...
Click to collapse
Still wont work.
HEY! put miflash and the tgz file in desktop, create a foler inside miflash named "log"; change the tgz file to a shorter one and try again! worked for me!
Edit .bat/.sh file
Well, I just fixed the same issue and solved it by editing the flash_all.bat or sh file ( windows or Linux). Just comment out initial lines without [ fastboot ] word. These lines are typically a version check.
Aashish_B_95 said:
Well, I just fixed the same issue and solved it by editing the flash_all.bat or sh file ( windows or Linux). Just comment out initial lines without [ fastboot ] word. These lines are typically a version check.
Click to expand...
Click to collapse
please help,i have same issue...
try a different usb slot
just saying, u CAN'T flash a 0 to 1 rom .. if u happy it only will stick to 1 , if u unlucky you get a ARB brick
epraes said:
Install MiFlash at C:\MiFlash and try again. I got this error once and it was due to the fact that MiFlash has problems with paths containing spaces.
Click to expand...
Click to collapse
Tried just to copy only MiFlash folder, error still happens. After copy the firmware into the MiFlash folder, it works fine!
To fix this 1-most flash from C:\MiFlash
2-The firmware folder name most be without spacing like :
(Redmi k30 pro) this is wrong ×
(Redmi_k30_pro) this is right √