Develop Bugs

[Q] CWM backup

Hi
I try cwm backup, sd card and internal sd, i have try mount everything but still backup size is only 16mb. Anyone know why?

Same here.

huoh
depserz said:
Same here.
Click to expand...
Click to collapse
I think no1 read Q&A thread. Pls someone post this bug root+cwm thread cos this forum is lame and i cant post it. " only if u have 10 or more posts, plaaplaaplaa, jaadijaadijaa"

If your CWM Recovery is 6.0.0.0 and higher then the small backup size is perfectly normal... There is another folder called blobs which actually stores the most of your backup data
The way the new CWM works is it makes a shared folder ( blobs ) that all recovery instances use... for example ( easiest example ) if you make a recovery of a fresh new device, then install a few apps , then make a recovery again , the blobs folder will hold the data that is used in both of those recovery images, and the their respective folders will only hold data that is exclusive to that particular image...
kinda like this :
{
"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"
}
the 2 gray circles are 2 recovery images , and the white area they intersect within is what they both have in common ( the blobs folder )
that way if you make many recovery images, the wont be 800MB each, they will be 15-30MB with one folder that has the stuff they "have in common"... saves on space and time
im not good at explaining , but i hope you can understand it xD

Ooh, thanks

Linux Tool by szoke12 (Android)

Linux Tool by szoke12​
Hi everyone!
I made a small tool for linux. It doesn't supports all of devices, but many yes.
Please use it just for your own risk!
It's just a script, but it has more options:
-monitoring device informations
-root android phone (2.0, 2.1, 2.2)
-install recovery image (not all device!) I tested it on Huawei U8160.
-unroot the device (on many device)
-reboot phone to normal or recovery mode.
-root, recovery install and reboot - Please use it, just if you are placed the files to the good place, and you are sure!!!
-if you connected more device to your pc, the program will ask to choose device.
-backup/restore downloaded apps (just the apps, not the data - may be later)
-install one or more apk
-the program contains an advanced menu with some function.
Install:
0) Connect the device, and turn on the "USB debugging" option
1) Download the zip file
2) Unzip to anywhere
3) Start a Terminal and change to the extracted folder ("Linux-Tool_by_szoke12")
4) cd Linux-Tool_by_szoke12
5) chmod 755 tool.sh
6) ./tool.sh
7) Use!
Tested on Ubuntu 10.04, 10.10, 11.04, 12.04, 12.10, Mint 11.
First the program downloads the needed files, and the starts.
Here is a screenshot:
{
"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"
}
Download: LINK
(This is the 0.5 version of the program. I developed it since the previous year.)
Enjoy!
If you can use it, or have problem or idea, please write feedback.
And press a "THANKS" button!
And sorry for the language... I don't speak English so well...

[TOOL] IMEI Backup Restore (without PC)

The tool is created to backup restore IMEI from phone itself (Recovery)..
Why should i backup?? -
This Tool takes backup of below important partitions .
modemst1 ,modemst2, fsg, fsc, DDR ,bk1 ,modem
This part of the device contains some important and some basic info related to our device identity like Bluetooth address, wireless devices MAC addresses, and the very main IMEI address , programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things.
which is very specific to your device and can't be easily generated.
So we can't take chance losing these data.
Requirments-
Any Custom Recovery (like TWRP,CWM etc..)
Process
Download the zip from Here http://d-h.st/rp2 or from Attachments .
Place it in your sdcard.
Goto recovery and flash it.
follow the instructions ...
Note-
The Backup files are stored in "MYIMEI_TOOL" folder of your Internal or SD card as you choose.
Credits -
This tool uses some scripts from Dr.ketan's EFS tool for Note ll
Sector1369 (Me)
This Tool is only for Redmi 1S
Screenshots-
{
"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"
}

Sorry for the camera screenshots..
Recovery taking the screenshot after closing AROMA installer ,Also tried to pull directly from frambuffer but blured images ...

I've already backup my imei using terminal emulator. Can i restore my backup using this?

zacutesz said:
I've already backup my imei using terminal emulator. Can i restore my backup using this?
Click to expand...
Click to collapse
yaah just move ur files to MYIMEI_TOOL folder

or u can take new backup
its all GUI based..
its Easy...

Not working on redmi 1s when i flash via twrp restart phone no aroma start.

How to upload the original build.prop file?

Hey,
I made root on my Shield TV 2017 16GB. All worked great.
I decided to edit the bulid.prop file to change the device name, but I don't think I did everything right.
I made a copy of this file on a PC before editing.
The trouble is that the device does not start. The Nvidia logo and the animation of the android logo are shown, which loads indefinitely.
I started the menu with A + B. I chose option 2 (Boot recoovery kaenel) and the second menu came up.
I chose (apply upade from ADB).
ADB detects the device in "sideload" mode.
Can I upload the file itself?
Do I need to restore the entire system?
Sorry for my bad English.
Best regards,
Menu 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"
}
Menu 2

use twrp to push the build.prop to system..
if u cant figure it out then flash stock and start over
you can only flash official updates through stock recovery and adb sideload

elliwigy said:
use twrp to push the build.prop to system..
if u cant figure it out then flash stock and start over
you can only flash official updates through stock recovery and adb sideload
Click to expand...
Click to collapse
Thank you. I was able to upload files using ADB Sideload.
The system started and works as it should.

Where to get a good persist.img file from?

Im once again into this typical "I bricked my phone and spend endless hours searching for tutorials and hoping that something work" stuff. This time I broke my persist.img and noticed something strange:
There are dozen of tutorials which state that one should download a clean fastboot rom to extract the persist.img (".\images\persist.img") from the image folder and flash it either using recovery or fastboot edl in combination with a modified rom to only flash this partition.
Now I noticed that the persist.img partition is pretty empty for most Xiaomi stock roms:
{
"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"
}
In comparisation the persist partition I extracted from a friend who luckily got the same phone:
How is the above persist partition from the stockrom supposed to help someone when there are just empty files? Atleast for me it didnt bring back the sensors when I flashed it. On the contrary the persist partition from my friend fixed everything.
If the persist file of every stock rom is empty beside a few zero byte files the conclusion would be that the only way to get a working file is to get your hands on a unmodified one from someone else.
Or is there some magic that will enrich the partition with new files as soon as you boot the stockrom for the first time?
How come there are so many tutorials saying that one should flash this partition from stock?

are you sure you have downloaded a fastboot (TGZ) rom and open the TAR file?
Package Name: grus_eea_global_images_V12.5.1.0.RFBEUXM_20210526.0000.00_11.0_eea_0f94ab4db4.tgz