Phone is a Star X19i
Now I'm looking at getting a system to allow me to back up the rom and re-flash if needed.
Post 4 has attachments of my boot, recovery and scatter files.
Old issue: (Solved)
Stupid thing I did I renamed the mtklockscreen.odex to mtklockscreen.odex1 just as a test in a half asleep phase to see if I would get the stock lockscreen loading.
Suffice to say the phone no longer boots.
Really don't think I can get into ADB and rename the file to get the phone booting again unless anyone knows a way.
Android was 2.3.6 and I asked the seller if it was possible to get the rom incase anything like happened which they didn't.
So anyone have any ideas?
I have attached the stock recovery and boot images made with cat and a scatter file I made to post 4.
As I have no idea about modifying these for hard root can anyone take a look?
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
dxppxd said:
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
Click to expand...
Click to collapse
I got into built in Factory mode and can see the file I renamed through ADB and android commander but cannot rename it back due to not having hard root access.
I also have a copy of the boot and recovery partitions 5 and 6 respectively I made in the adb shell yesterday as I was half looking at getting hard root access.
ren mtklockscreen.odex1 mtklockscreen.odex
ren: permission denied
I read you can do a custom recovery with root using SP Tools still so can anyone help me do this?
I know about system root etc and stuff and have flashed roms before on other tablets and have been a PC I.T tech (wouldn't think it due to the stupid mistake) but this recovery and scatter files etc is kinda new to me.
I have a scatter file now I just made if anyone is interested in helping me.
Yes I have a MTK6573 but the scatter file came from the MT6516 Rom Studio which I read works the same for the 6573.
Attached is also my stock boot and recovery partitions I made with cat yesterday if there usable to anyone to help.
Well I got it working and fixed.
I had to go into adb shell and su and mount the file system as writable, as I have used linux before I didn't know about android and what needed to be done and permission locks etc.
The stock boot, recovery and scatter files will remain on this thread if anyone wants to help create or find a recovery which can allow me to create backups and flash custom roms.
I may be able to provide a dump of android 2.3.6 for those that want it once I'm provided with a backup solution as I have read a few people wanting this updated android rom.
This got too close to what I would like liked with bricking this phone.
And I'm not comfortable unless I have a rom backup of this.
Rooting Advice: For anyone with a MTK6573 on Android 2.3.6 trying to root but having issues with super one click make sure you only turn on USB debugging after Android has loaded and just before you plug the usb cable in to run super one click.
I have seen a few thread and posters here about not being able to root the phone and this is the cause that debug needs to be switched on right before you connect and try to root.
Original seller has agreed to send the firmware and flashing stuff on cd for me so I can upload it for you all.
This is a win for MTK6573 Star X19i owners as I'll have the updated 2.3.6 Gingerbread firmware to release for you all root modify etc in a week or so.
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
cybermaus said:
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
Click to expand...
Click to collapse
That's what I read and did to get my scatter as I used cat then used the program linked in that thread to generate the scatter.
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | less​showed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv​
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...
I have been unable to find an answer after scouring the internet and XDA for answers,
I was trying to disable the primary mic (bottom) so that I was able to only use the secondary mic (top). This is/was possible by rerouting all references to Mic 1 with Mic 2 device in /system/etc/audio_device.xml. The problem is that I tampered a little bit further and broke the lot. Does anyone know how I can restore this file? If a complete re-flash of the system is required then would someone be able to provide a link to the stock firmware? I have not been able to find it.
Build: 36.0.A.100
OS: 6.0 (Marshmallow)
P.s - Yes, I should have created a 'proper' back-up of the partitions.
P.P.S - I have root access.
I found the solution via replacing the whole system partition with stock, heres how:
1) Download Flashtool (https://forum.xda-developers.com/showthread.php?t=920746)
2) Use XperiFirm to find the correct stock firmware
3) Use Flashtool's SIN Editor (tools -> Sin Editor) to get an ext4 file of the system partition
4) If there's a single file that needs replacing then it can be read/copied from the ext4 by mounting the file.; as I was using a Windows machine I used Ext2Explore.
5) The file will be restored through flashing the stock system partition
This was shared for anyone else who needed it.
Hey guys, i'm about to give up on this Z2 - it might be a hardware issue but the software is missing the /persist folder on EVERY clean install. Wanna check that before giving up.
Basically, i got a Z2 on 23.5.A.1.291 6.0.1 next to me. Turning Wi-Fi and BT on does nothing and MAC shows 02:00:00:00:00. I tried to fix it the past 5-6 hours and i am out of ideas.
What i tried so far:
1) Installing Carbon ROM 8.1.0 along with TWRP 3.2 and SU 2.82 --> didn't fix the problem but i read in xda alot and found out it could be driver problem and missing files in /persist folder.
Turns out i don't have this folder on the Z2. Compared with my Oneplus One which has this folder. They are both Snapdragon 801.
Creating the folder does not help as it just gets deleted when the phone is rebooting (which is normal to my understanding).
2) Finding out whether i even have a /persist partition on the phone.
Didn't work as i could not get adb shell nor Android Terminal to give me proper root access. Again no problem on my OPO (just for personal comparison)
3) Tried to flash stock FTF 23.5.A.1.291 with flashtools again.
Did not work as the phone was not recognized as Xperia Z2 after updating to Carbon ROM 8.1.
4) Use Emma to install 6.0.1 again --> this worked but it would only allow me to install an older Version of 6.0.1 which had no Wi-Fi functioning as well.
5) Tried flashtool again to go to my local 23.5.A.1.291 --> after being on the "older stock 6.0.1" it allowed me to do that, again no Wi-Fi.
Now i can't check for the /persist folder since root is not installed as i am back to Stock 23.5.A.1.291 with unlocked BL.
Any ideas on how to get the stupid driver installed? It drives me nuts. Every flashing process went perfectly fine with no sign of a failing /persist partition or anything.
Same issue here i guess: https://forum.xda-developers.com/xperia-z2/help/bluetooth-wifi-problem-stock-mm-n-o-rom-t3750689
The funny thing is that the radio, sensors and everything else works perfectly fine (4G).
The wifi module bcmdhd.ko is located in system/lib/modules. It should be around 665kb.
The firmware location is system/etc/firmwares/wlan/bcmdhd which contain 3 files.
If you want root you can prepare a prerooted ftf and flash it with flashtool.
If the above files are intact and have required permission 644 then the hw could be the culprit.
I don't have the persist folder on my Z2 running 23.5.A.1.291.
fredrickz said:
The wifi module bcmdhd.ko is located in system/lib/modules. It should be around 665kb.
The firmware location is system/etc/firmwares/wlan/bcmdhd which contain 3 files.
If you want root you can prepare a prerooted ftf and flash it with flashtool.
If the above files are intact and have required permission 644 then the hw could be the culprit.
I don't have the persist folder on my Z2 running 23.5.A.1.291.
Click to expand...
Click to collapse
No such file here
Dash_k said:
No such file here
Click to expand...
Click to collapse
To see those files you need to have root permissions.
First root your phone using prerooted firmware, flash it and use a root browser. When you install the stock rooted firmware those files will be copied from system.sin. Let me know after rooting.
Just make sure you flash the system partition. It will automatically install the drivers. Also flash the stock kernel.
Been trying for days to extract the kernel from Nougat to use it within Marshmallow in order to downgrade with vibration working on nougats bootloader - but for the life of me i can NOT get windows to actually read these files properly. have all kinds of mounting programs, a java based converter that doesnt actually work (sgs2ext4) i end up with this loop of the same lines, and a 0kb converted file. I can mount the regular img file fine, but it will NOT open without some sort of error. the files themselves are just fine as they will properly flash and run when using odin (when compressed into tar.md5)
Tried wthin twrp hoping the file manager might just let me browse through it since the phone is already linux based and can actually see the information... but no dice there either. It doesnt go into further detail than just showing me that theres an img file present, with options to delete, chmod, etc.
what can i do to dig down to this zimage portion of boot.img that everyone insists the kernel is within? (i say insist cuz i havent actually seen it for myself!)
none of the tutorials ive come across address these specific opening errors - other than that the error is happening because windows cant read it
diskinternals wont work, osfmount will mount but i cant read it .... where on earth are these drivers or programs or whatever i need to actually allow me to browse and explore these files properly? and dare i say, recompress them once ive found what im looking for!
i did also try flashify, thinking run nougat, backup kernel, install marshmallow, restore nougat kernel, but it just leads to freezing on boot logo. I need to get within these img files to actually do what i want to successfully, switching out only that one specific zimage part of the file, leaving the rest intact.
very frustrated here, would very much love some help with this...
Try this, helped so much!
https://forum.xda-developers.com/general/xda-university/unpacking-editing-packing-roms-img-dat-t3350261
Also, If you want to try, here is a link for the tools:https://www.androidfilehost.com/?fid=24459283995310951