Related
I wanted to write this "guide" for all the others that may be experiencing issues such as myself and others that I've talked to and helped. It was quite a learning experience and one of those "wow, I totally screwed myself" moments, to say the least lol.
There have been quite a few posts by others that outline how to update your rooted phone with the OTA but I wanted to put it down a bit more step by step with some extra information for those that thought it might be a good idea to just DELETE some apps from the /system/app patition (myself, included) without taking a full system backup using CWM, etc. I do NOT believe that a Titanium backup is sufficient if you choose to delete the application afterwards (as I see no evidence that the [required] .odex files are part of the TiBu backups)
Due to all the requests (here is my RAZR /system/app dump):
Pre-OTA: http://bit.ly/vwkbDw
Post-OTA: http://bit.ly/rZdQgC
So here we go...
1. Settings -> About Phone -> System Updates -> "Download Now"
2. Once downloaded, choose "Install Later" (important!)
3. Open up ES File Explorer or Root Explorer or you can even use adb to shell into the system (not recommended unless you're really good at this)
4. Browse to the /cache directory
5. Copy the two files named "Blur_Version.6.11.744.XT912.Verizon.en.US.crc" and "Blur_Version.6.11.744.XT912.Verizon.en.US.zip" to the /sdcard-ext location (NOT /sdcard)
6. Download and Install (from the Market) "OTA RootKeeper"
7. Run OTA Rootkeeper and select "Protect Root" (this will preserve files and links to the root application after the update). You CAN still choose to re-root using DoomLord/Zerg method but this is a LOT easier
8.You can choose to backup your apps via TiBu if you want to be extra cautious should something go wrong (but not required).
9. Power OFF the device. Then enter Motorola Recovery mode (Hold Vol+ and Vol- and Power). Click Vol- to highlight Recovery Mode and Click Vol+ to select it. Wait for the Triangle and exclamation point and then press both Vol buttons at the same time
10. Choose to "apply update from sdcard" by using the the Vol+ or Vol- to highlight and the Power Button to select
11. Choose the update file using the same method as step 10
12. Let it run and do it's thing...here's where the problems can start. If you have no problems you can skip to step 18
13. If you receive a "Status 7" error message it is probably complaining about checksum mismatch of the file that is ALSO listed in that output. This can also happen if the file is missing
14. Record the first 4 characters of the TWO checksums that it lists (this is important, do not forget) AND the filename (usually /system/app/<somename.apk> /system/app/<somename.odex>
Having these checksums will help you locate which file you need to get you back to "good" standing. The first value indicates the SHA1 checksum of the UPDATED file (POST OTA patching) while the second value indicates the SHA1 checksum of the older file (PRE OTA patching). There are quite a few resources on these forums where people have provided their "system dump".
You can also find this information after an unsuccessful install in the /cache/recovery/last_log directory on your phone - for those that use the install method from within the Android OS (Automatic OTA Install)
15. Download one or more of these "system dumps" and extract the file named in the error. Copy it to your sdcard and then use Root Explorer or Astro to copy it to the /system/app location (you might need to make it R/W on /system/app)
15A. For the advanced users:
You can save some guess work and get the sha1 value using a utility (windows/linux) to compare the strings with what was in the error message.
IF the checksums match you might as well copy over the corresponding .odex/.apk file as well.
IF the checksums do NOT match, you might as well scrap that "system dump" and download another one (and pray)
15B. IF you are unable to locate an original razr file that matches your criteria you can also take a stab and ask someone to send you their POST-OTA file(s) that you are missing. You can also compare the SHA1 checksum OR just try and see if it works. The installer will continue forward if it detects either the CORRECT old or new file already in place (*whew*)
16. Then return to step 9. Continue steps 9-15 until the update goes through.
18. Reboot after the update is complete
19. Verify the update was successful by following step 1 (there are other ways to see the version as well)
20. Re-run OTA RootKepper and select the option to "Restore Root"
21. Disconnect any USB cable to the phone and reboot. Verify root works properly (SetCPU, TiBu, SuperUser App, etc)
IF you are unable to regain root via Step 20, then you can always use the method that you previously used to RE-root your phone (Zert/DoomLord utility)
22. FREEEEEZE your apps from now on. (at least until there is an SBF). Stop deleting anything that isn't on your sdcard-ext partition
I hope that helps some folks out. I had about 8 files to replace and it seemed that there was never a "system dump" that had all of them. I helped one user by providing just ONE file that he accidentally deleted. In turn, after the update he provided me with both (updated) files that I needed. Win-Win!
I have my old and my NEW "system-dump" files so don't hesitate to ask me for them. If I receive enough requests I will end up putting them on one of the mediafire/megaupload places. A few other places to get the system dumps are from some of the ROMS provided for the US RAZR (i had some files match from the RAZRX 1.0 ROM)
If you noticed that I skipped number 17 then you were paying close enough attention ;-)
It worked, thank you.
Sent from my DROID RAZR using xda premium
great write up
droidony--droidforums
I cant find any dump links that are active. My problem is with the settings.apk. can anyone help?
Found one dump and no match.
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
I originally needed the maps odex file (as that was what was showing up in the log but I had it on my phone I must have done something as to how it disappeared) which i got from your download well one thing had lead to another with all these zips of the update and this is where I am at now. I guess I will stop here until I get better direction on what to do now. I am not sure if it is better or worse than before. This is the current log of where I am. If you know where to go from here please let me know. Thanks!
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
E:Error in /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------
update: I tried to install the 744 copy that was on the sd card and this is the error it gave me. The above is the error it gives me directly from the ota download and update.
-- Install /sdcard/download ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Failed to mount /dev/block/mmcblk1p20 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
script aborted: assert failed: mount("ext3", "MTD", "system", "/system")
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command ""
elyhlapetina said:
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
Click to expand...
Click to collapse
Same here. No files there.
elyhlapetina said:
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
Click to expand...
Click to collapse
Oaklands said:
Same here. No files there.
Click to expand...
Click to collapse
If you don't have root enabled you won't be able to view the folder contents. SO, if you used the OTA RootKeeper app and temporarily removed root, you will need to back into that application and restore root...
Viewing the last_log in the /cache/recovery location isn't needed, if you do the manual installation using the Motorola Recovery. The same error messages appear in the yellow text after the update fails and before you reboot the phone.
branshaw09 said:
I cant find any dump links that are active. My problem is with the settings.apk. can anyone help?
Found one dump and no match.
Click to expand...
Click to collapse
Branshaw, did you take a look at my two download options listed in my original post? Settings.apk SHOULD be in there. You can also try grabbing one from one of the few ROMS that are out for the RAZR - i suggest trying to pull the apk from the RAZRX 1.0 ROM
kb3awq said:
I originally needed the maps odex file (as that was what was showing up in the log but I had it on my phone I must have done something as to how it disappeared) which i got from your download well one thing had lead to another with all these zips of the update and this is where I am at now. I guess I will stop here until I get better direction on what to do now. I am not sure if it is better or worse than before. This is the current log of where I am. If you know where to go from here please let me know. Thanks!
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
E:Error in /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------
update: I tried to install the 744 copy that was on the sd card and this is the error it gave me. The above is the error it gives me directly from the ota download and update.
-- Install /sdcard/download ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Failed to mount /dev/block/mmcblk1p20 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
script aborted: assert failed: mount("ext3", "MTD", "system", "/system")
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command ""
Click to expand...
Click to collapse
It sounds like you ran something on your phone that may have adjusted settings in the build.prop file (supercharger, jakebitesmod, etc). I can try and give you a copy of mine when I get home tonight, but hopefully someone else in here would be kind enough to attach it to a post on this thread.
it worked!!
thank you so much it worked perfected
Great solution, but what if I just have to restore an app (Facebook Authenticator in this case) I'm already Post-OTA, deleted it by accident, any help please? been scratching my brain for days. TIBU just hangs when I try to restore it.
jerkwad said:
It sounds like you ran something on your phone that may have adjusted settings in the build.prop file (supercharger, jakebitesmod, etc). I can try and give you a copy of mine when I get home tonight, but hopefully someone else in here would be kind enough to attach it to a post on this thread.
Click to expand...
Click to collapse
Actually I haven't ran anything extra just copied the map codex in with the others and the pre and post update on here gives signature verification error lie the other couple I tried from droid forums from the other guy who had a zip for a solution which was a stock root zip. This is amazing my Droid 1 could flash anything etc. And I was trying to be a stock good boy with this phone except root.
can someone please help me on what to do now. after i got to trying to install the update i recieved the status 7
this is what my phone said
assert failed: apply_patchcheck("system/app/livewallpappers.apk", "37db550d10330f4e0bcf0efb60a86b62f7598a4a3", "d3686011083bcb1b46cb9d1702b1788bf5772e37")
E:error in /tmp/sideload/package.zip
(status 7)
Installation aborted
So I took a look at what was missing, and it doesn't match with the directions you gave. Atleast I don't think it does.
here's what i got:
--Install /sdcard/Android Dev Update ...
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/preinstall/KnowYourDevice/Motorola_XT912_BatterySave.3gp",
5faf882a9f143c2e45a264aad9c067233a43be8b", "6bcc903965d9cd3862f5c5a5760e129d36b07cf5")
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted.
I didn't, myself, remove or freez any apps.
jerkwad said:
Branshaw, did you take a look at my two download options listed in my original post? Settings.apk SHOULD be in there. You can also try grabbing one from one of the few ROMS that are out for the RAZR - i suggest trying to pull the apk from the RAZRX 1.0 ROM
Click to expand...
Click to collapse
I am trying to download your pre ota file now. The settings.apk md5sum in razrx ROM fine match my error report
I have the same problem. Im rooted and use astro file manager and nothing is in cache.
Sent from my DROID RAZR using xda premium
I have same issue with guidedtours.odex
checksum first 4 are
64d7
1c18
5bb6 & 5cc1
Sent from my DROID RAZR using xda premium
95ea and b39c for gmail.odex any info greatly appreciated.
HDW
[Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11
Q&A for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
denizyildizi345 said:
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
Click to expand...
Click to collapse
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
carliv said:
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
Click to expand...
Click to collapse
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
denizyildizi345 said:
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
Click to expand...
Click to collapse
No, for checking recovery root you need to look here: CM11-0/out/target/product/msm8226/recovery/root . But anyway that folder looks strange (I see a perl script there)....
Check my screenshot below.
And type a
Code:
make clobber
before stating a new build, or
Code:
make clean
between repetitive builds.
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
george676 said:
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
Click to expand...
Click to collapse
You need to be more specific: what recovery you try to build, in what environment (if it's not cm-11), and post a link to your device folder tree. That error means that the compiler can't find an init.rc file to add in ramdisk.
Compiler stops after a few segments
This is shown in my terminal:
Code:
cp: cannot stat ‘/home/paul/cm-10.2/out/target/product/Ultra/root/init.recovery.*.rc’: No such file or directory
make: [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1 (ignored)
mkdir -p /home/paul/cm-10.2/out/target/product/Ultra/recovery/root/system/bin
cp -rf device/CherryMobile/Ultra/recovery/root /home/paul/cm-10.2/out/target/product/Ultra/recovery/
cp: omitting directory ‘device/CherryMobile/Ultra’
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1
[email protected] ~/cm-10.2 $ make clobber
And you wrote about the problem:
During the build process you may encounter some errors or warnings.
*********************
Code:
Code:
cp: cannot stat `/home/carliv/CM11-0/out/target/product/P780/root/init.recovery.*.rc': No such file or directory
make: [/home/carliv/CM11-0/out/target/product/P780/recovery/root.ts] Error 1 (ignored)
This will not stop the build, and it appears if you don't use a init.recovery.{hardware}.rc file. Can be ignored, as the build process does.
Though in my terminal it just stopped at that part so I had to rename mine which was originally init.recovery.qcom.rc to init.recovery.*.rc
--edit--
And yet it still would not continue ... Any ideas on how to fix this?
--edit # 2--
Here's the pastebin link just in case ->biQ7kjV8 add that to pastebin...(I can't post links)
--edit # 3--
I fixed it... Turns out that it was just a BoardConfig.mk parameter that I forgot to complete
Calculate proper BoardConfig.mk partition sizes
I have this log:
Code:
----- Making recovery image ------
/home/paul/cm-10.2/out/target/product/Ultra/recovery.img maxsize=8380416 blocksize=135168 total=8409088 reserve=270336
error: /home/paul/cm-10.2/out/target/product/Ultra/recovery.img too large (8409088 > [8650752 - 270336])
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery.img] Error 1
make: *** Deleting file `/home/paul/cm-10.2/out/target/product/Ultra/recovery.img'
Meaning I have wrong sizes for the partitions so I need help on it...
When I ran the following:
cat /proc/mtd
cat /proc/emmc
they both return: No such file or directory...
Now If I run the command: cat /proc/partitions
it comes up with this:
As far as I know.... mmcblk1p1 is my external sd card which is about 32 GB...
My system image is about 1 GB and more(confirmed) when I used the dd command(to dump it) and is located at mmcblk0p16
Userdata reaches more than 4 GB as reported by the dd command(file size too large) and is located at mmbblk0p25
here(recovery.fstab):
/boot mtd /dev/block/mmcblk0p10
/cache yaffs2 /dev/block/mmcblk0p18
/data yaffs2 /dev/block/mmcblk0p25
/misc mtd /dev/block/mmcblk0p20
/recovery mtd /dev/block/mmcblk0p19
/system yaffs2 /dev/block/mmcblk0p16
-- edit --
I solved this already
Help required for compiling CWM for android 4.4.2 version only?
I am on Ubuntu 14.0.4 and I am trying to build a CWM recovery for Celkon Q 5009android 4.4.2, Broadcom processor). I have set up build environment and currently working on syncing repo. I have heard that it takes too much time and disk space to complete this process. I am interested to know in the following particular scenario : want to build only CWM recovery from source for an android running on version 4.4.2. So do I have to download all repositories or is there any shortcut that would enable me to not download all, but a certain part that is required for android 4.4.2? If yes, how to go about it? please help.
Please help. I do not undertstand why 'repo sync' always fails at a particular stage, though I have 30+ GB of disk space available in my working folder named 'cm12'. Following is the last screen message :
Fetching project platform/external/ant-glob
Fetching projects: 8% (40/495) Receiving objects: 86% (2389/2771), 26.68 MiBerror: RPC failed; result=56, HTTP code = 200iB | 124.00 KiB/s
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
remote: Sending approximately 1.94 GiB ...
remote: Counting objects: 85, done
remote: Finding sources: 100% (85/85)
error: RPC failed; result=56, HTTP code = 200iB | 88.00 KiB/s
fatal: The remote end hung up unexpectedly
Now should I run 'repo sync' again or should I use 'repo sync -j1' ?
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch device/lge/mako-kernel
error: Exited sync due to fetch errors
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Black Manta said:
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60297989&postcount=51
Somewhere around that post you will find your answer.
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
4javier said:
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
Click to expand...
Click to collapse
First let me ask you where did you find a cwm for lollipop to build it? I'm interested to see that.
Second in recovery fstab you may want to add emmc partitions like boot, recovery... Check my github and look at elephone p6000 device folder (it's close enough to understand). If internal sdcard is on data/media you don't have to add it at all in fstab (at least that was the rule for kitkat... again I need to see the source for that lollipop cwm to tell you exactly). In elephone device recovery fstab you can see that usb and external sdcard are defined as auto for type not vfat because it is better to let minivold manage that.
Normaly for cm12.1 ther is no need to copy any rc file in root, only the fstab. {hardware}, which you said you did.
Again I can tell more if I will see the source code for the recovery, and last thing my guide is quite old now but I'm glad you found it useful.
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
4javier said:
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
Click to expand...
Click to collapse
I did understand it's cm12.1, but that was my question since there is no cwm for cm12.1 only cyanogenmod recovery which is different. At the moment I only recommend twrp for cm12.1+ and for that you have to use a different fstab, easy to find on github or here on xda in twrp threads.
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
4javier said:
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
Click to expand...
Click to collapse
Yes for all and for twrp fstab I think you can study device folders from twrp github (few are mediatek).
My kitchen now detects if image has mtk header and will repack it the same way (it stores a variable in unpacked folder which will tell that it must add a mtk header).
I decided to follow this guide to integrate the changes needed to build twrp instead of cwm: http://forum.xda-developers.com/showthread.php?t=1943625
It doesn't cover all the preparation steps like yours do. Do you think there are changes to be made to make your guide suitable for cm12 and twrp, or I can follow it until the " Build a CWM-based Recovery " paragraph?
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
What android version where you at and what did it upgrade to? Also, try booting into recovery and erasing all data.
i had tried everything i had wipe cache it and hard reset it too but still nothing work for me i just need a stock firmware of that mobile (Mobile name is swipe konnect plus ) and my phone android version is 5.1 lollipop please help me :crying:
what recovery is installed?
Need stock rom and custom recovery
Hey pls give me swipe konnect plus stock rom and custom recovery
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
That is unfortunately not how it works here...
swipe konnect plus error on inatalling cm12.1
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
aksthecount said:
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
Click to expand...
Click to collapse
What'd you use to port the ROM? Android kitchen or yourself? What kernel do you use?
I port it myself with XDA guide
I use custom ROM kernal 3.4.x and copy my kernal file uevent.tc and zimage file my kernal very is 3.10.72+
---------- Post added at 03:56 PM ---------- Previous post was at 03:53 PM ----------
It says unable to mount dev/block/mmcblk05/at system
---------- Post added at 04:01 PM ---------- Previous post was at 03:56 PM ----------
What does that mean
Hey, RAZERDAHACKER pls hlp me pls,pls,.......
Stock firmware for swipe konnect plus
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
Hello , if you really want the stock firmware then reply of this message . I will tell you where you can find the STOCK firmware for this device. But for sharing link of another Website i need permission from this XDA team. If they allow me then i can post here the link of the STOCK firmware.
Thank you .. and waiting for your reply.
sorry for late mess yaa give me the link
aksthecount said:
sorry for late mess yaa give me the link
Click to expand...
Click to collapse
tap on the quoted thread below to view the full answer
x.ak**** said:
like all my comments above to encourage me to help you.
Okay so first of all i will let you know why a phone gets bricked-
>corrupted rom
>some system files got deleted
>rooting
>modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
my case
i always keep two phones with me like one for my experiments and one as a backup. In this case i'll be talking about my lyf wind 3 that got bricked.
>actually i was trying to install twrp onto that phone but first i had to root it, and due to the upgraded android security, i wasn't able to do via kingoroot so i tried i-root and it did the job but instead of kingo-superuser i got some ****ty superuser so i tried granting permission to the actual superuser and while doing so i accidentally double rooted my phone (first with i-root and then with kingoroot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
Click to expand...
Click to collapse
x.ak**** said:
tap on the quoted thread below to view the full answer
Click to expand...
Click to collapse
My case was that I flash cm 12 on my swipe konnect plus n was working fine but was reddish the common bug of cyanogenmod
and it can be fixed no matter how many I change file to clear bug so I just lost hope then I restore my stock via twrp n then the mobile was lagging to much so then I thought that it must be coz that twrp didn't restore my stock properly so search on Google swipe konnect plus firmware n I got the site on firmwarefile.com there was three stock room for swipe konnect plus so I download all of them n when I flash one of them it got brick then I flash another but sp flash tool giving me error "dram enable failed"
So I googled it n found that if we flash wrong preloader it hard brick your device that means the firmware for swipe konnect plus on the website r all wrong firmware n also check the build.prop of it was written the same model but I don't know what is happening I just want to abuse whoever upload swipe konnect plus firmware coz it brick my device pls if anyone is reading this pls pls pls pls help me to I just want preloader.bin file for my device if anyone anyone or your frnd is using swipe konnect plus pls pls pls pls contact me on my email [email protected]
---------- Post added at 09:29 PM ---------- Previous post was at 09:21 PM ----------
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
Hey do u still have swipe konnect plus reply me pls
Hello guys!
So after I saw Strix's latest TWRP (January 21) I tried to change my file system to f2fs, but everytime I do, it gives me an error message: Failed to mount 'system ' (Operation not supported or transport endpoint)
What do I need to do to make it working?
Try TWRP M4 Recovery
Hello guys,
I have a Ulefone Be Touch 2 (with a MT6752 cpu) that only boot and stay on the ulefone logo, and I can't install any ROM (official or custom ones)...
In fact, the tools (latest SPFlashTool v5.1628 and the one provided by ulephone I used successfully earlier) do the download process until 100% without error message, but the only thing that seems to be on the phone (and working) is the recovery.
With this two softwares I am able to install the official recovery or TWRP (2.8.7.0 from needrom), and they both are usable.
But when I try to do something in recovery mod, it tells me that cache or system partitions (and others) are not mounted (or found).
In SPFlashTool, I tryed many features without success but I have (NAND and UFS) errors when doing memory tests :
#External RAM:
#
# Type = DRAM
#
# Size = 0x80000000 (2048MB/16384Mb)
#
#NAND Flash:
#
# ERROR: NAND Flash was not detected!
#
#EMMC:
#
# EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
# EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
# EMMC_PART_RPMB Size = 0x0000000000400000(4MB)
# EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
# EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
# EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
# EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
# EMMC_PART_USER Size = 0x00000003a3e00000(14910MB)
#
#UFS:
#
# ERROR: UFS was not detected!
I don't understand what it meens and how can I change the recovery if the NAND is gone? Are system partitions and recovery stored in different places/memory (types)?
I searched and read on differents thread (the UBT2 review, mtk6755 ERROR: NAND Flash was not detected by split52 , [GUIDE] How to 'unbrick' your Mediatek MT65xx...) and googled and watched related videos but didn't find anything than matches and can really help me.
So, if someone can help me I would really be grateful.
Thank you in advance.
I'm sorry if I post this thread in the wrong section (I think it's the first I creat).
sylkyls
I had a problem like your's when I walked all over my partition layout because of a botched flash. Didn't have UFS errors tho. No info anywhere. Had to verify my scatter file and recovery fstab layout agreed with each other. Ended up modifying my scatter file. Took it one partition at a time using the fstab until the recovery recognized all partitions then backed up my files, reformatted and flashed the stock rom using SPF Tools. Took a while to boot. After that, the original scatter file worked. Still don't make sense why it worked that way but it got me back working.
smith901 said:
I had a problem like your's when I walked all over my partition layout because of a botched flash. Didn't have UFS errors tho. No info anywhere. Had to verify my scatter file and recovery fstab layout agreed with each other. Ended up modifying my scatter file. Took it one partition at a time using the fstab until the recovery recognized all partitions then backed up my files, reformatted and flashed the stock rom using SPF Tools. Took a while to boot. After that, the original scatter file worked. Still don't make sense why it worked that way but it got me back working.
Click to expand...
Click to collapse
Thank you smith901,
I don't know how to do this: I can run a terminal into the recovery but if I do cat /etc/fstab or less /etc/fstab , I only have :
/system ext4 rw
/cache ext4 rw
/data ext4 rw
/external_sd auto rw
I think I'm doing the wrong way.
Could you tell me (or redirect me to) a method please?
Have a nice day
sylkyls
sylkyls said:
Thank you smith901,
I don't know how to do this: I can run a terminal into the recovery but if I do cat /etc/fstab or less /etc/fstab , I only have :
/system ext4 rw
/cache ext4 rw
/data ext4 rw
/external_sd auto rw
I think I'm doing the wrong way.
Could you tell me (or redirect me to) a method please?
sylkyls
Click to expand...
Click to collapse
Seems to be fstab problems.
Use whatever unpacking tool you are comfortable with to unpack the stock recovery and TWRP. Then replace your fstab files in the root and /etc directories after changing what you want, rw to /system or whatever. Modify the twrp.fstab file in /etc using the values from stock fstab. You might have to add in or replace your rc and mt6735 files also. Repack then flash. The log screen in TWRP will let you know what partitions can't be read. Choosing the correct encryption partition took some trial & error.
Once you get it all to read, the modified twrp.fstab, files in the unpacked stock recovery folder plus a device tree, and the TWRP building thread will get a recovery built by yourself as soon as you can sync from git.
smith901 said:
Seems to be fstab problems.
Use whatever unpacking tool you are comfortable with to unpack the stock recovery and TWRP. Then replace your fstab files in the root and /etc directories after changing what you want, rw to /system or whatever. Modify the twrp.fstab file in /etc using the values from stock fstab. You might have to add in or replace your rc and mt6735 files also. Repack then flash. The log screen in TWRP will let you know what partitions can't be read. Choosing the correct encryption partition took some trial & error.
Once you get it all to read, the modified twrp.fstab, files in the unpacked stock recovery folder plus a device tree, and the TWRP building thread will get a recovery built by yourself as soon as you can sync from git.
Click to expand...
Click to collapse
Thank you again, but I'm really sorry that I can't apply your instructions... ( unpacking with 7-zip does not give me any fstab file )
Could you try to do it with the official rom please? ( download link is in the bottom of this page: http://ulefone.com/download/betouch2.html , at the next step my phone needs the "option 2" rar file).
With custom roms (zip files flashable with a custom recovery or rar archive), I can unpack thems and obtain/open a fstab file ( recovery.fstab ) but not with things flashable with SPFlashTool.
sylkyls
sylkyls said:
Thank you again, but I'm really sorry that I can't apply your instructions... ( unpacking with 7-zip does not give me any fstab file )
Could you try to do it with the official rom please? ( download link is in the bottom of this page: http://ulefone.com/download/betouch2.html , at the next step my phone needs the "option 2" rar file).
With custom roms (zip files flashable with a custom recovery or rar archive), I can unpack thems and obtain/open a fstab file ( recovery.fstab ) but not with things flashable with SPFlashTool.
sylkyls
Click to expand...
Click to collapse
I meant an unpacking tool like Carliv Image Kitchen or Android Image Kitchen. I'm rarely this helpful so once I finish cleaning the carpet I'll have a look.
The recovery.fstab file look slim in this recovery but that is what they made.
Download Aindroid Image Kitchen.
Follow the instructions to unpack your stock recovery and TWRP recovery.
Make the changes you want. Copy needed files, /etc/recovery.fstab, fstab.mt6752 and probably the *.rc files from stock to TWRP. Just check everything to be sure.
Repack TWRP then flash.
I don't use Windows so I couldn't use the program provided in the archive.
sylkyls,
did you solve the issue? I have the same problem.
cmarqz said:
sylkyls,
did you solve the issue? I have the same problem.
Click to expand...
Click to collapse
Hello,
Sorry every one but I forgot to follow this thread as I had a lot of work and someone giave me another phone ( a samsung note 4 N910F) that I repared (and am using now) and then I did let my ulefone away from my priorities.
Sorry cmarqz but I didn't try the solution proposed by smith901 on my MTK6752 device.
Maybe I'll try it later.
Did you find a solution for your device?
Best regards XDA users.