Database Info

[Completed] [Q] Stucked at Boot Loop after changing Boot animation

Hello,
I'm Using a Rooted Starmobile Up has an MediaTek MT6582M
well, it started when i was changing the bootanimation of my phone with an marvelboot.zip using ES File Explorer, i forgot to set the permissions so after i restart it, my phone stucked at boot animation.
i copied the marvelboot.zip at the /Device > system > media folder as far as i can remember.
i think it will be solved if i am able to delete the bootanimation.zip from that media folder using computer or something else.
i am wondering how can i delete that file from the system folder, or perhaps change permission? and is there a way to browse the system folder from android to computer?? i just wonder if theres such, but i will go with your answers.
i have no CWM installed and i dont know how, i dont know ADB, or SDK and all
when i tried installing CWM from recovery menu, it says installation aborted and thats my only way.
can someone help me?
another thing is i forgot to backup the firmware, and ofcourse warranty is voided as it is rooted, i cannot get it's firmware anywhere.
thanks again
I need your help, thank you.

OK so you can post your question here: http://forum.xda-developers.com/showthread.php?t=2257421&page=1
However, I urge you to keep searching for the stock firmware. This is a rare device that has practically no support.
If you had adb support which is highly unlikely you could use the command "adb push bootanimation.zip/system/media"
But I very much doubt you will be able to get adb to communicate.
I wish you all the best in searching, but I think you may have just learned a very costly lesson on always having a backup before tinkering.
Good luck

hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?

whateverwhenever said:
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
Click to expand...
Click to collapse
I honestly don't think it would work. You really need a custom recovery or a way to access your bootlooping phone's system.
You can check this thread out on adb http://forum.xda-developers.com/showthread.php?t=2588979
If you're successful in getting adb to work you may have a shot at fixing it. But the odds are against you.
This is why we are all encouraged to read and be careful.

[Q] quick question

I have a Alcatel One Touch Pop 7 tablet from T-Mobile. There is someone on a YouTube video who has the same tablet, but has bricked it installing a custom ROM. He is begging me to make a backup of my "system" folder to send to him.
My question is, is that safe to do? I'm a complete noob when it comes to rooted devices, so I don't know if there is anyway that could be damaging to me, or if I would be doing someone a solid and helping them bring their tablet back to life.
Please, can someone advise me if this is OK or not (me making a backup of my system folder and sending it to him?)
Thanks in advance for reading and responding

auburn2eugene said:
I have a Alcatel One Touch Pop 7 tablet from T-Mobile. There is someone on a YouTube video who has the same tablet, but has bricked it installing a custom ROM. He is begging me to make a backup of my "system" folder to send to him.
My question is, is that safe to do? I'm a complete noob when it comes to rooted devices, so I don't know if there is anyway that could be damaging to me, or if I would be doing someone a solid and helping them bring their tablet back to life.
Please, can someone advise me if this is OK or not (me making a backup of my system folder and sending it to him?)
Thanks in advance for reading and responding
Click to expand...
Click to collapse
Yeah, No Problem Dude for Backup...It is totally Safe...
Backup provide your data safe & if by mistake you delete your any files... You can restore again. So,Don't Take Doubts any Backup your system.

next question
I copied the system folder for him. Now he is asking for the boot.img file. I searched my tablet with Root Explorer and it didn't find a boot.img file... Any ideas?

backup your kernel with any app. just google it.

davidpersi said:
backup your kernel with any app. just google it.
Click to expand...
Click to collapse
This isn't about me making a backup for me. I am trying to help someone who bricked their tablet, as said in my first post. I backed up the folder he asked me to back up. Then I uploaded it to my Google drive and sent him the link. He got my upload, and messaged me back saying the folder did not include the boot.img file. So, with Root Explorer, I searched my tablet for the boot.img file. Root Explorer didn't find the file he was missing. I am asking if anyone knows where I should look?

please help a117 owners, you experiance is needed.

Hello xda friends.... im new here and i need a help from u guys. Please help mee..
i just bricked my micromax magnus a117. What i did--- rooted my phone then installed an app meteos6589 (something like that) to increase app storage. Then i restarded my phone(with usb debugging off(if it afffects anything )). And after that it is showing micromax logo only.
so anyway i downloaded stock rom v4 from mounlisky. and tried to flash with sp tools. But but but problem is arising something like "pmt didnt mathched...................." . So sp tools is saying to select and do format+download option. But i have nothing in backup only microsd and internal sd data.
So the point is i dont have backup of nvram or anything else, phone is bricked at micromx logo, usb debugging off. So how do i get my phone back to life.
anyone please....
Any detailed help is appreciated.. thank you..

so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?

ranganitesh said:
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
Click to expand...
Click to collapse
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.

syserr said:
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
Click to expand...
Click to collapse
So what files are needed to be backup along with mtk droid tool, just wanna know.

ranganitesh said:
So what files are needed to be backup along with mtk droid tool, just wanna know.
Click to expand...
Click to collapse
I don't use MTKDT at all. I do see some uses for it though. SPFT is a pain, but I wish every device (SoC maker) had an SPFT so you could read or write any chunk of flash.
If you look at a scatter file you will see lots of blocks/partitions that the flash is divided into. Each of these has a purpose of course, but the one marked NVRAM (a horrible confusing name) is the most important to get backed up, it has unique "calibration data" for your specific unit. You may find a "nvram.bin" that MTKDT created... this may be exactly what SPFT would backup too... if you are lucky.
So if MTKDT made a nvram.bin that is about 100x better than having a nvram.tgz or however he archives the /data/nvram files.

[Completed] Revisit Accessing a .backup file on windows for lost information.

My original post was closed before I could respond...
Below the original is a response I received.
Hi Im not a developer and dont know much about android i just don't know who to ask for this particular problem.
I had a ZTE Obsidian phone that wont get past the Metropcs boot screen so I did a system restore menu by holding power and the up vol button.
After going to boot menu I created a backup to my sdcard. userdata_20150101_003623.backup this is the file name I was given. To make sure I created another one and the only diffrence is trhe file extension saying backup1.
I then factory reset the phone and tried to reboot but it still has the same problem. I purchased a new phone the asus Zenfone3. I then tried to do the same thing here but restore the phone using the same backup from the ZTE but I received an error saying the backup is out of date. The zte was running on lollipop and the asus on marshmellow.
Im on windows 10. I was hoping to find away to extract my contacts and possibly the app color note with the notes I wrote in it from the backup.
Is this possible can I extract these files from a .backup to my windows 10 desktop some kind of way or can I get another zte phone and create a clone of my last one from the backup file
Greetings and welcome to assist. Do you know what format the backup was saved in ? Where you using twrp or cwm? You could use titanium backup to extract from the backup on your phone if you have root or I think assayed kitchen has the option to extract from a back up here
https://forum.xda-developers.com/che...tchen-t3410545
Good Luck
Sawdoctor
Do you know what format the backup was saved in ?
No I dont know what format the file is saved in. The file extension just says .backup
Where you using twrp or cwm?
Im a novice at android and developing. I dont know what these are. I used my no rooted phone from Metro Pcs (ZTE Obsidian Z820) before I factory rest it I created a backup using the factory restore system on the phone. I did not use a computer or third party apps to do this.
You could use titanium backup to extract from the backup on your phone if you have root or I think assayed kitchen has the option to extract from a back up here.
The phone was from metro pcs and not rooted. I have also downloaded the (Assayed Kitchen) program but have no idea how to use it to access the .backup file. There are no instructions for some one of my limited knowledge on android phones.

JollyDangerous said:
My original post was closed before I could respond...
Below the original is a response I received.
Hi Im not a developer and dont know much about android i just don't know who to ask for this particular problem.
I had a ZTE Obsidian phone that wont get past the Metropcs boot screen so I did a system restore menu by holding power and the up vol button.
After going to boot menu I created a backup to my sdcard. userdata_20150101_003623.backup this is the file name I was given. To make sure I created another one and the only diffrence is trhe file extension saying backup1.
I then factory reset the phone and tried to reboot but it still has the same problem. I purchased a new phone the asus Zenfone3. I then tried to do the same thing here but restore the phone using the same backup from the ZTE but I received an error saying the backup is out of date. The zte was running on lollipop and the asus on marshmellow.
Im on windows 10. I was hoping to find away to extract my contacts and possibly the app color note with the notes I wrote in it from the backup.
Is this possible can I extract these files from a .backup to my windows 10 desktop some kind of way or can I get another zte phone and create a clone of my last one from the backup file
Greetings and welcome to assist. Do you know what format the backup was saved in ? Where you using twrp or cwm? You could use titanium backup to extract from the backup on your phone if you have root or I think assayed kitchen has the option to extract from a back up here
https://forum.xda-developers.com/che...tchen-t3410545
Good Luck
Sawdoctor
Do you know what format the backup was saved in ?
No I dont know what format the file is saved in. The file extension just says .backup
Where you using twrp or cwm?
Im a novice at android and developing. I dont know what these are. I used my no rooted phone from Metro Pcs (ZTE Obsidian Z820) before I factory rest it I created a backup using the factory restore system on the phone. I did not use a computer or third party apps to do this.
You could use titanium backup to extract from the backup on your phone if you have root or I think assayed kitchen has the option to extract from a back up here.
The phone was from metro pcs and not rooted. I have also downloaded the (Assayed Kitchen) program but have no idea how to use it to access the .backup file. There are no instructions for some one of my limited knowledge on android phones.
Click to expand...
Click to collapse
Greetings ans welcome again. It is unusual for a stock recovery to be able to make a back up that is the problem, it is only normally possible to make a backup using a custom recovery like cwm or twrp so I assumed you had done this. You can not restore a backup from a different model of phone as it is incompatible, if you copy your back up to your pc and right click it to get properties it should tell you what file extension was used. You won't be able to restore the back up to a different model of phone but may be able to extract contacts, messages, photos etc
Regards
Sawdoctor

sawdoctor said:
Greetings ans welcome again. It is unusual for a stock recovery to be able to make a back up that is the problem, it is only normally possible to make a backup using a custom recovery like cwm or twrp so I assumed you had done this. You can not restore a backup from a different model of phone as it is incompatible, if you copy your back up to your pc and right click it to get properties it should tell you what file extension was used. You won't be able to restore the back up to a different model of phone but may be able to extract contacts, messages, photos etc
Regards
Sawdoctor
Click to expand...
Click to collapse
Yea thats what I thought but wanted to verify it. Im currently trying to find the same model phone online so I can use the files.
When I click the properties button the file type is listed as "BACKUP (.backup)". I dont think there is a program that can actually read this file type at least I cant find one that does.
If there is one I would like to be able to get that kind of info off of it.

Backup problems and questions

Hi, first of all, thank you for reading me.
I think i messed up big time.
I had Havoc OS 4.1 installed since more than a year and it was kinda messy e.g. the sim card card wasnt recognized anymore so wasnt able to make calls because i played to much in the settings.
Having some stupid but incredibly addictive games on this smartphone i decided to keep it like this and since i'm a complete n00bs and being afraid of security risk of rooting my device i never rooted it.
Big mistake.
So, recently, one games needed an update (like they all do at least once a week) and since i'm anti-google/f***book (no comment please) i nvever saved my progress in the cloud and "that" game required absolutely an update.
I installed the update from an alternative apk source and , (applause if you want and laugh), it screwed up the game.
Now the nightmare begin.
Since the device isnt rooted i made a backup of /data partition. Gone crazy and before i might explode in an uncontrollable fury and madness i used LMSA to rescue the phone. And myself, lol.
Now i have stock android and i am googled to the bone. My butt hurts. My head too.
THE (first) simple question is : how can i restore this backup because i have the error 255?
Notes and observations; logically i would say because the device is back with stock rom and doesnt have the same os/rom installed and/or the partition and whatever is not the same wich may explain the error 255.
SECOND QUESTION: can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
I know i have to give as much information possible but i dont what else to give. If you need logs, or everything else just say it nicely and i will give it to you with immense pleasure.
Oh yeah, model : XT2113-2 5g Kiev RETCA 128gb a/b type and maybe was crypted before because twrp asked me the password to make backup or else.
Thank you in advance and i really hope somebody would help, if not i just loosed 1.5 years of stupid gaming because i messed up like an idiot. (A lesson well learned, the hard way...)

Thank you so much for not answering this simple question.

Kerplunk83 said:
Thank you so much for not answering this simple question.
Click to expand...
Click to collapse
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.

Finally a sign of life from someone here.
Thank you sd_shadow
sd_shadow said:
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Click to expand...
Click to collapse
These precious brief and concise 2 lines of a simple answer is immensely welcomed.
Wich point me to reply that to my knowledge i interpret it as a security chip with big chances that its in relation to the knox technology.
It also point me to ask WHY, if i cant back up because of that, why/how is it possible to install a custom rom or gsi (sorry i still dont make the difference because i dont understand it) on this very protected smartphone?
That must explain why i had problems trying to root it and fail each time.
Finally i think that i should use another device for android gaming since i dont want to depend on f***book and google.
Thanks again sd_shadow. Even if it was a very simple answer it enlightens me alot.
Note: sorry for my bad english.

Kerplunk83 said:
how can i restore this backup because i have the error 255?
Click to expand...
Click to collapse
This error code means that at some point your backup of /data could not be extracted further. But for more detailed infos you must provide a recovery.log which will be generated when doing a backup of e.g. /boot.
>>> Please DO NOT copy+paste it here!! <<<​Rename it (recovery.log > recovery.log.txt) to be able to upload it within "Attach files".
Kerplunk83 said:
can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
Click to expand...
Click to collapse
Yes, use Titanium Backup (TB). Although it's very outdated it still features a restore of single apps out of a TWRP backup. Here's how you do it:
1. IMPORTANT: TB will only search for TWRP backup files on internal storage!! Use the default path created by TWRP, e.g.: /sdcard/TWRP/BACKUPS/ZY322V8K28/2023-04-08--06-53-20/
2. Install and open Titanium Backup.
3. In the upper right corner tap
MENU > scroll down to "Extract from Nandroid backup" > choose your backup folder
##############
Notes:
- Usually a TWRP backup of /data consists of several parts (data.ext4.win000, ~win001, ~win002 etc). TB requires all of them (or at least those ones with the /data/data/ path inside).
- If you are facing this error message:
Could not find any data in this TWRP backup
then your TWRP backup is compressed with gzip. To decompress it you must rename the file
data.ext4.win001 > data.ext4.win001.gz
and extract it with any archiver tool, e.g.:
- ZArchiver (Android)
- 7zip (Windows)
- Problems finding any TWRP backup data with Titanium Backup? Then please check your path!! (see above section)
Good luck!!

Thank you very much WoKoschekk i'll do it as soon i'll have the time for since i'm working today.
Thank you so much again, i'll keep you posted with logs and such.

I'm sorry i didnt gave news since, i'm not doing very well.
there's those 2 question i still have in my head;
1-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Ultimately, how can i be rooted if there's a chip preventing me to do so?
I'll keep you posted when i'll be of better health, thank you.

Kerplunk83 said:
-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
Click to expand...
Click to collapse
TWRP backup = *.tar archive
TB unpacks the needed app's data and nothing else. You must be rooted to have access on /data for restoring your apps. But for the backup process it doesn't matter if you were rooted. Root is part of your boot.img.
Kerplunk83 said:
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Click to expand...
Click to collapse
TB is for free. But a paid version unlocks additional features (not related to the TWRP restoring feature).
And yes... root is mandatory for TB. As I said before you must have r/w access on /data/*.
Kerplunk83 said:
if there's a chip preventing me to do so?
Click to expand...
Click to collapse
Which chip?? You already have root access via TWRP. Magisk is only needed in system and just a patched boot.img (custom kernel).

Get well soon!

WoKoschekk thank you for this insanely fast reply.
All those answers and infos have now a gigantic value for me, if only i knew that before.
To describe a bit more my situation i slept only few hours since 5 days, vomiting, heavy coughs and fever.
I'm sure i'm not supposed to but i will anyway, i engage myself and promise to reward you (in particular) and others for the help you're bringing me. It wont be much but very important to me.
I'll go try to get (again) some rest. Just before i go, why was there a mention about my device;
"
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
"
I dont ask you (WoKoschekk) or other to explain in the most explicit and endless details of what is exactly this "chip" and all the history that goes with it cause i dont want to be a pain but just why it was mentionned. Only, why?, it has ben mentionned.
I cant wait to get better since i finally see possibilities to get back those files.
Have a nice week-end and thanks again.

@Kerplunk83 To reveal the mystery behind "the chip": Motorola released two variants (Snapdragon/Mediatek CPU) of this model. Since the CPU largely determines the system structure, building a functional TWRP for both of them is very challenging. It seems that TWRP for the SD's variant got some bugs while the MT's variant runs more smooth. Due to this fact the error 255 is caused by something that you weren't be able to fix.
Regarding your problem: To restore an app and its specific app data you need the proper permissions to write in /data/data and /data/app. For this permissions you either need TWRP or Magisk installed. TWRP seems to be unable to write in that specific directory. On the other hand you don't want to install Magisk. I'm sorry but with this setup your problem can't be fixed.
Just out of curiosity, could you provide me a recovery.log showing error 255 during the restore process?
Please DO NOT copy/paste the whole log and post it here!! Instead of this you should rename the file (recovery.log => recovery.txt) because a file called *.log isn't allowed for upload. But a *.txt file is.
Options to create a recovery.log:
1. adb pull /tmp/recovery.log
=> copies a recovery.log into your ADB/fastboot folder
2. Do a backup of sth. like "boot" because the backup process will create a recovery.log by default
3. TWRP mainscreen > advanced > create log (kernel log isn't needed here)
=> log is stored on the default storage (internal or external) that you have choosen for backups etc.