THE PROBLEM I FACED DURING DUMPING RECOVERY IS THAT
1. /dev/block/platform( platform folder missing )
2. " by-name" also not present under/dev/block or any place in the /
3. partition layout not showing the name recovery
So I am attaching the following:
a. my / folder structure
b my cat /proc/partitions, /dev/block, cache recovery last log, parted file please review them and comment
c. I am rooted succesfully
Please upload twrp/cwm backup to Google drive/Dropbox
Use temporary twrp/cwm for Intel devices thread..
Please..
Related
Dear Owners,
I did some tricks for the HTM A6(W) MT6572 phone, which has got only ex4 system, cache, data partitions (eMMC memory type).
Please NOTE that these written things are related only HTM A6W, which has got MT6572 platform with EXT4 system partitions.
You need to know that some of the HTM A6 contains ubifs file system, which is complety different from this one.
Applying these files for other than HTM A6W phone can cause serious damage in the phone (brick)
Before you did any modification on your phone, DO a complete system backup!
These tricks are:
Rooting is really smooth and easy with the help of framaroot.
CWM recovery 6.0.1.2, originally compiled by Bruno Martins, modified by me, with the help of Maste Shifu bgcmgn’s MTKTools.
Link: CWM 6.0.1.2
md5sum: 3d847d2ed1d5fa3dbacd0aa860c5874d
You can install it via Mobileuncletools or with Flashtool (advanced users also can use dd command via adb)
Modifications:
- /etc/fstab.recovery is modified as per dumchar_info file
- the default.prop file was modified from stock recovery from HTM A6W
- the default curtaing.png was modified with text
- the init.usb.rc was copied from stock boot.img of HTM A6W
Repartition to 3GB data partition
I calculated the maximum size of the /data partition and reduced the internal SD card to the minimum size.
This action is also known as „repartition” or „extended userdata partition modification”.
This is about the modified content of the EBR1 file.
The modified ebr1 file link: ebr1
md5sum: 6b7f46b79f43979df7ddc7f4a11a26ba
If you do not know what it is about, please do not use it!
In the attached picture you can see that the displayed storage size in the settings menu is fake...
What I mean: using the settings --> storage menu item, the data partition is displayed as 4,12GB which is impossible, but if you use the settings --> applications menuitem, you can see the real value: 3GB. And this is true, it is really 3GB (As I mentioned I calculated it, and I was really surprised that this is the reality. Usually MT6572-based phones’ /data partition can be extended to about 2.5-2.6GB, but it is 3GB.
How to apply the change?
There are many ways to flash the ebr1 file.
1, Flashtool, with marking only the ebr1 part for download.
2, dd command, if your phone is rooted. Save the new ebr1 file (named as EBR1-almost-max-v1) to the following directory: /storage/sdcard0 ; You need to have acces to the adb terminal. In theminal, use the following commands.
su -
dd if=/storage/sdcard0/EBR1-almost-max-v1 of=/dev/block/mmcblk0 bs=1024 seek=512
- If your phone is rooted: with the help of MTKDroidTools (thanks to rua1).
- If your phone is not rooted: with the help of flashtool.
- CWM backup is also a must before any additional modification.
Finally, I cannot take any responsibility if you damage your phone by using the tricks above.
It worked for me.
This phone was mine only for some days.
Credits:
Base of the CWM – bgcmgn
MTKTools scripts for porting CWM – bgcngm
ebr1 calculation for this phone - cappa72 (me)
It works for me
hello, just want to let you know that your tricks work on my HTM A6(W) that I bought last week. I had to work through the problem of correctly installing and using the utilities you mentioned, because I'm not used to them, but all went smooth.
Just a question: is there any drawback with the current internal storage partitions? what about the 0Mb for internal SD?
Francesco from Italy
Hello Friends,
I just registered to this forum.
It's awesome to read all of the thread inside this forum...
but my brain is limited to learn everything in no time.
Well, I found this thread.
The title is: [RECOVERY][XSOLA] TWRP 2.7.0.0 touch recovery [2014-04-27]
.....................................................
.....................................................
.....................................................
.....................................................
"Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I don't own Xperia Sola so didn't test it. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type ..........................."
Do you all know what must I do on "placing my current rom's boot.img"? I just can't find the file on my Xperia Sola device.
Please Help.
Thank You.
Boot.img is not a file on the XP. It is the image of the boot partition.
You can extract it from the zip of your ROM or from the ftf from Sony or from the CWM backup.
Sheers
adi10pn said:
place your current rom's boot.img
Click to expand...
Click to collapse
have u kept the .zip file of the ROM you are currently using? if so extract the files from it and you will find a file named "boot.img"
Press Thanks if I helped you
Hello guys,
so i have messed up my ZenFone 5's booting configuration. good thing is, i know where i have messed up, unlike other noobs like myself. i have been modifying the adbon.sh file, where i added a conditional to check if a file(/dev/keycheck) exists and if it exists(will always return 'true'), to extract the contents of a recovery.tar(custom recovery). problem is, now i cannot boot normally into my device. if anyone can help me with three things, i'd be grateful.
1. How to modify the adbon.sh file using:
(a) preferred choice: using adb sideload <filename> ( i need to update THAT SPECIFIC FILE ONLY) ->(the file is in /system/bin/)
(b) secondary choice: using fastboot flash command. is it possible to update a single file using fastboot flash? (probably not, i think) should i have to flash the entire system partition with a stock/custom ROM? (i already know most about this, but a clear good guide can help me)(i know it will overwrite the total /system partition)
2. Give me a link to the original(stock) adbon.sh file if method 1(a) is possible.
3. Give me a compatible link to a CWM recovery for my device, ASUS_T00J (the recovery in my recovery.tar is a stock recovery, i got f**** fooled into downloading a stock one where i thought it was a custom CWM recovery)
Hi everybody
I'm new on this big forum, so this my first post...
I have made a backup for my chinese tablet (MT6582) by using MTK droid tools, and I have installed a recovery for it and I installed a rom but it didn't work. So I want now to restore the first stock rom by installing the backup with the SP flash tool ... I have all the wanted files (img) just the system.img file because I have just the system folder. So my question is: How to convert(pack) the system folder to a yaffs2img file. :good:
up ; I'm waiting your answer
please help me
Unfortunately i have wiped my basic system, so i 'v decided to install new one from here:
"ops cannot share links"
(if you know better places to download custom os for nokia 1 pls tell me)
When i install zip packeges from above via TWRP from external storage i get such error:
Code:
twrp 255 error installing zip file
How can i fix it?
P.S recovery.log :
ht tp s :/ / pastebin . com / 5hLEMbsA