Database Users

[Q] How to unpack boot and recovery images from iconia?

Hello. Anyone knowns how to unpack our tablet boot.img and recovery.img? I tryed many methods, but get errors, I think because its for android phones, not for tegra2 devices. Sorry for bad English.

ive been doing it for a while now, this guide is great
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
some of the tool links are broken, you can find them or similar tools by googling around. ive used both tools and the hex editor.
EDIT: just uploaded the tools im using. on linux just drop your boot imgae in the same folder as the tools and do
Code:
./extract-kernel.pl boot.img
./extract-ramdisk.pl boot.img

does it works for native ubuntu bootloader.img? It seems that netham's recovery.img hasn't ramdisk, when i type ./extract-ramdisk.pl recovery.img then i get:
The boot image does not appear to be a valid gzip file at ./extract-ramdisk.pl line 33.
And when i do like this: # ./unpack-bootimg.pl recovery.img
Then i get: Could not find any embedded ramdisk images. Are you sure this is a full boot image?
But it works as well in boot.img's

Tautvaldas said:
does it works for native ubuntu bootloader.img? It seems that netham's recovery.img hasn't ramdisk, when i type ./extract-ramdisk.pl recovery.img then i get:
The boot image does not appear to be a valid gzip file at ./extract-ramdisk.pl line 33.
And when i do like this: # ./unpack-bootimg.pl recovery.img
Then i get: Could not find any embedded ramdisk images. Are you sure this is a full boot image?
But it works as well in boot.img's
Click to expand...
Click to collapse
hm.. not sure where this bootloader.img is coming form, this method should work on both a standard boot image, and recovery image, i have only personally tested on a boot image, maybe try the hex method? see what happens?

that bootloader.img is netham's recovery.img who boots Linux natively from sdcard/roots.img. I ask because I wand edit where bootimage boots Linux that it can boots from internal memory like Asus tf101 Ubuntu. Sorry for bad English.

Really????
{
"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"
}

If it possible unpack recovery and boot images then shoud be possible mount them like filesystem "mount -o loop ubuntu.img /mnt" (but other methot because mount -o loop doesn't works with boot images) that we can see what is inside them before unpacking it. it is possible or I'm wrong?

(UNOFFICIAL) TWRP 3.0.1 FOR LE1s (x507)

​Twrp3.0.1 for le1s x507
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Flashing instructions
Using flashify
Flash the image file using flashify
Using sp flash tool
Requirements
Naeems root kit (link given below)
Unlocked bootloader
Open sp flash tool
Select scatter file by clicking scatter button
Click download agent and select da dl
Double click recovery and select new twrp file(link goven below)
Uncheck all others including user data
Click download and connect your device in power off mode.
Happy flashing

athultaj1
You forgot to insert the download links.
{
"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"
}
But I see you have here
http://forum.le.com/in/index.php?threads/twrp-3-0-1-for-x507-le1s-unofficial.8706/

BJOnE
Errors :
1. Unable to restore system backup (extractTarFork() process ended withERROR=255) data restore works fine.
2. Cpu temperature always shows 0°C
3. Battery % always at 50% , even in previous build 3.0.0-0.1
Anyways thanks for the port
From the log :
==> extracting: //system/app/ (mode 40755, directory)
tar_extract_file(): failed to extract //system/app/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/0123456789ABCDEF/2016-04-05--01-34-55_DHXOSOP5501203231S_release-keys/system.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/BACKUPS/0123456789ABCDEF/2016-04-05--01-34-55_DHXOSOP5501203231S_release-keys/system.ext4.win000' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
original link
http://forum.le.com/in/index.php?threads/twrp-3-0-1-for-x507-le1s-unofficial.8706/#post-44754

laikexpert said:
BJOnE
Errors :
1. Unable to restore system backup (extractTarFork() process ended withERROR=255) data restore works fine.
2. Cpu temperature always shows 0°C
3. Battery % always at 50% , even in previous build 3.0.0-0.1
Anyways thanks for the port
From the log :
==> extracting: //system/app/ (mode 40755, directory)
tar_extract_file(): failed to extract //system/app/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/0123456789ABCDEF/2016-04-05--01-34-55_DHXOSOP5501203231S_release-keys/system.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/BACKUPS/0123456789ABCDEF/2016-04-05--01-34-55_DHXOSOP5501203231S_release-keys/system.ext4.win000' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
original link
http://forum.le.com/in/index.php?threads/twrp-3-0-1-for-x507-le1s-unofficial.8706/#post-44754
Click to expand...
Click to collapse
@laikexpert haha.... I was about to post it here since no one replayed there, now you did it for me

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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 am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​

Thanks man...you saved me ,i had almost given up on my yureka as even twrp was not working after i soft brick my phone last night
Thanks a lot!!!

OEM_NV_BACKUP The NV partition is invalid!

Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj

do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.

chintu1234 said:
do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.
Click to expand...
Click to collapse
As said....no.
TWRP did not backed it up.
Any other method/idea, ayone?
EDIT:
Just figured out that I have EFS backed up (oem_stanvbk.emmc.win). I will restore it from twrp, lets see how it goes.

jukyO said:
Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj
Click to expand...
Click to collapse
Any further ideas, as EFS restore from TWRp doeas not work.

Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app

jukyO said:
Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app
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"
}
here is the file that have in my EFS backup from TWRP

lockmunk said:
View attachment 3729740
here is the file that have in my EFS backup from TWRP
Click to expand...
Click to collapse
I have exactly the same.
Why restoration of it does not solve it?
If I pull
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
with dd:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
to sdcard, they have 1M each, whilst backup is 10M.
Can anyone try the same?
EDIT:
above mmcblk is for OPO, OPT has /dev/block/mmcblk0p20.
And size is ok if I do dd with it.

bump, anyone?

jukyO said:
bump, anyone?
Click to expand...
Click to collapse
bump #2.

got the same issue, damn x) need help, tried the 100% restore backup with qualcomm drivers etc, didnt restore 100%

bump..please help to share your modemst1 & modemst2 please......

androidbrick.com

Nothing on androidbrick...

Lumia 520 cannot flash partition

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).