Simple And Easy Method
Code:
[FONT="Courier New"][COLOR="Red"][SIZE="1"]* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot[/SIZE][/COLOR][/FONT]
INSTRUCTIONS 1:
1. Download and install Odin/usb drivers.
2. Power off the device and boot into download mode by holding [VOLUME DOWN+HOME +POWER].
3. A Warning screen appears,now press volume up once and connect the phone to the PC.
4. Open Odin with admin rights and you should see the phone added at some ID COM: port,
if not then you have to download and install the appropriate drivers.
5. Now click on AP and select the downloaded recovery file.
6. Press start And It will reboots.
INSTRUCTION 2
1.Copy Downloaded Supersu zip to Your SD
2.Power of Your device
3.Hold volume up+home+power to enter into recovery mode.
4.Press Install And Select zip from SD
5.Swipe to Install
DOWNLOADSTwrp3.0.2.0.tar.md5 With ODINSuperSu
Does this also work for E700F too?
Theareach said:
Does this also work for E700F too?
Click to expand...
Click to collapse
i don't know brother.....try it and let me know
Rizoo27 said:
i don't know brother.....try it and let me know
Click to expand...
Click to collapse
So I gave it a try! Surprisingly, it works! Everything seems to work just fine for my variant, but the brightness doesn't. Well, I was looking for a functional custom recovery for a long time so yeah, It won't be my issue. Thanks
Theareach said:
So I gave it a try! Surprisingly, it works! Everything seems to work just fine for my variant, but the brightness doesn't. Well, I was looking for a functional custom recovery for a long time so yeah, It won't be my issue. Thanks
Click to expand...
Click to collapse
I'm glad it worked for u....:good::good: Happy To Help for brightness just go to settings and select brightness symbol and adjust ur brightness hope it works and thank u for testing
Thank you @Rizoo27.. can i flash this 4.4 stock ?
midhun.akd said:
Thank you @Rizoo27.. can i flash this 4.4 stock ?
Click to expand...
Click to collapse
Twrp i guess will work not to sure about supersu......but u give it try
Theareach said:
So I gave it a try! Surprisingly, it works! Everything seems to work just fine for my variant, but the brightness doesn't. Well, I was looking for a functional custom recovery for a long time so yeah, It won't be my issue. Thanks
Click to expand...
Click to collapse
Try this rom http://forum.xda-developers.com/gal...nt/stockcustomrome700h08november2016-t3496190
midhun.akd said:
Thank you @Rizoo27.. can i flash this 4.4 stock ?
Click to expand...
Click to collapse
Try this rom http://forum.xda-developers.com/gal...nt/stockcustomrome700h08november2016-t3496190
Rizoo27 said:
Try this rom http://forum.xda-developers.com/gal...nt/stockcustomrome700h08november2016-t3496190
Click to expand...
Click to collapse
Hello Rizzo I testing now
---------- Post added at 04:23 PM ---------- Previous post was at 04:19 PM ----------
Tested run perfectly with E700m
Thanks
If possible analize this post
http://forum.xda-developers.com/gal...ot-how-to-enable-otg-support-android-t3519835
Rizoo27 said:
Try this rom http://forum.xda-developers.com/gal...nt/stockcustomrome700h08november2016-t3496190
Click to expand...
Click to collapse
Has anyone confirmed that this work on E7OOF, bro?
If possible test otg support in your rom
Thanks
This one working flawlessly, thank you!
Sent from my SM-E700H using Tapatalk
Works as expected.
Recovery works good, although the brightness issue still persists. Proper node path for brightness setting seems to be
PHP:
/sys/devices/soc.0/1a00000.qcom,mdss_mdp/qcom,mdss_fb_primary.136/leds/lcd-backlight/brightness
in the stock ROM kernel, as echoing different values between 0-255 on that node changes the device brightness on the fly in my testing.
Though that "RECOVERY IS NOT SEANDROID ENFORCING" bothers me too much so I added the string SEANDROIDENFORCE to the end of recovery image provided in the OP.
As I use Apps2SD to keep some apps on microSD Card, I've also added an fstab entry for the second partition of type ext4 at /dev/block/mmcblk1p1 with mount point name /sdext2.
I suppose absence of a second partition on microSD Card wouldn't affect booting of recovery if I put a different card in my phone ?
At any rate, the modded recovery image's zip is in attachments for anyone to test out, test is whether it fails to boot when it can't mount 2nd partition from microSD Card.
Test script for brightness path in E700H
I've made a test ash script that attempts to vary device brightness level from minimum to maximum [0-255]. The essential code is as below:
PHP:
# brightness node path
node_path=/sys/devices/soc.0/1a00000.qcom,mdss_mdp/qcom,mdss_fb_primary.136/leds/lcd-backlight/brightness
# while loop to demonstrate brightness changes
# $i must be [0-255]
i=0
counter=0
while [ $i -le 255 ]
do
# clear
counter=`expr $counter + 1`
echo "brightness = $i, brightnessLevel=$counter"
sleep 1 # try to minimize the effect of lags
echo -n $i > $node_path
i=`expr $i + 15`
sleep 1
done
I'll link a tar.gz attachment of the script for anyone interested to test it out.
The testing steps are :
1. Put the brightness_test script file in /data/local/ or any other directory with read/write/execute access.
2. Set proper permission for the script: chmod a+x ./brightness_test.sh
>>At this stage you could run it in your current ROM if you wish. But as test
is for the TWRP given by OP,
3. Power down and reboot to recovery.
4. Go to advanced >> terminal , choose directory "/data/local" or where you put the script file.
5. Run it, "./brightness_test.sh"
Expected results should be, device brightness reduces, and then begins to rise as the while loop runs.
The expected results should be as shows in this video:
https://youtu.be/TBByqHRSyiA
@Rizoo27 , could this discovery of brightness node, allow the brightness setting in TWRP provided by you to work as intended?
Please respond!
I too seek to build the recovery as a learning exercise.
Related
Notes:
Click to expand...
Click to collapse
This build is a rework/continuation of MDJ Froyo Sense Revolution series
If m-deejay decides to update his original build, I will discontinue this build
Use this at your own risk. I will not be accountable if this causes you phone to fail, or you lose your data. The backup of your data is your responsibility.
I am a newbie to the android development, so please be patient with fixes and releases; and your help and advice will be appreciated.
Finally: Please, Click Thanks if you appreciate the build, and all works.
Kernel Usage
Click to expand...
Click to collapse
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with a lot of fixes Just to confirm, this kernel was originally S9.2 from MDJ, so up until then all credit is to him
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
ROM Links
Click to expand...
Click to collapse
I have tested an upgrade myself to these releases myself, and have not encountered any problems. But everyones setup is different, the upgrade process may work for you. But would recommend to do a NAND backup before you do. FINALLY, I will not be held responsible if you lose any data.
DFT releases will not be provided, so DON'T ask
The build of this ROM is available here, If anyone wants to have play with this build, then feel free to checkout the repository by running the following command in Linux. This will grab the whole repository onto your machine.
Code:
git clone http://github.com/arif-ali/android_leo_fsr.git
Froyo Sense Revolution 2.5.1 NAND CWM MAGLDR, Click or scan the image
Froyo Sense Revolution 2.5.1 NAND CWM cLK, Click or scan the image
Forum Links
Click to expand...
Click to collapse
ClockworkMod HowTo
cLK howto
config.txt Howto
Click to expand...
Click to collapse
ppp_mode - set PPP or not, valid values 1 or 0 (not for cLK)
gps_zone - zone from pool.ntp.org, values may be uk, us, europe etc... check pool.ntp.org, for all possible values
example config
Code:
ppp_mode=1
gps_zone=uk
cLK Howto
Click to expand...
Click to collapse
Download the attached cLK1.3.3_system_250M_arif-ali.zip, or cLK1.3.3_system_210M_arif-ali.zip
turn phone on with volume down key, so that it is in SPL
install cLK by double-clicking CustomRUU.exe
To install recovery download the correct one from post #2 of cLK thread (link below)
reboot phone into fastboot by keeping the back key pressed
flash recovery by running "fastboot flash recovery recovery.img"
How To (CWM - MAGLDR)
Click to expand...
Click to collapse
Make sure you have partitioned the SD card correctly (ext partition, and a vfat partition)
Make sure you have followed the ClockWorkMod Howto to add the recovery to the phone (see links in the thanks/credits section)
Download the link above and put it into the vfat partition, maybe in a folder called ROMS
Boot phone into MAGLDR by holding on the Red button/close call
Select AD Recovery (Option 8)
Select Install zip from sdcard
Select choose zip from sdcard
Select the ROM from the SD
Select Yes to install the zip
reboot the phone and enjoy
How To (CWM - cLK)
Click to expand...
Click to collapse
Make sure you have partitioned the SD card correctly (ext partition, and a vfat partition)
Download the link above and put it into the vfat partition, maybe in a folder called ROMS
Boot phone into fastboot by pressing the back key
flash the recovery using "fastboot flash recovery recovery.img"
reboot phone into cLK recovery by holding on the Home key
Select Install zip from sdcard
Select choose zip from sdcard
Select the ROM from the SD
Select Yes to install the zip
reboot the phone and enjoy
Howto ROM Manager
Click to expand...
Click to collapse
After booting into the phone, you need to create the following file on your sdcard, and reboot the phone. Hopefully after this, your phone should work.
Code:
/sdcard/clockworkmod/.settings
with the following contents
Code:
{"is_clockworkmod":true,"current_recovery_version":"3.0.1.9","readonly_recovery":false,"recovery_timestamp":1300214577721,"flash_recovery":"flash_image recovery %s ; ","reboot_recovery":"","detected_device":"leo"}
I will attempt to get this added in the next release
Please READ!!!
Click to expand...
Click to collapse
make sure that any app that you do install move it back to the phone, and that will automatically reside on the SD card in the ext2/ext3/ext4 partition
For the this ROM 210 MB in /system, So you need the Recovery_250M from the RaiderX303's thread
To Do List / Work in-progress
Click to expand...
Click to collapse
v2.6
Fix AudioFlinger Issue
Fix volume issues
Add Stock Theme Option
Thanks/Credits
Click to expand...
Click to collapse
m-deejay (ROM & kernel)
Cotulla (MAGLDR, HSPL)
kholk (Radio)
RaiderX303 (ClockworkMod)
birkoffsjunk (img2cwm)
tkirton (dtapps2sd)
cedesmith (cLK)
letama (ril_wrapper)
#htc-linux and #htc-linux-chat
All ROM users
Screenshots
Screenshots
Changelog
v2.5.1(25/03/2010)
new kernel AA 0.5 (see kernel changelog for details)
support for ROM Manager if using cLK
Add latest ROM Manager to cLK build
update to cLK 1.3.3
cache moved to mtd cache
Add ES File Explorer
Update gmail, youtube apks
v2.5(13/03/11)
added cLK support
moved AA 0.3 kernel
added PPP support
added config.txt support
fixed APN issue in framework
Initial Release (by me)
Downloading & try soon
chairman_palm said:
Downloading & try soon
Click to expand...
Click to collapse
Any feedback?
Update to 2.5.1
Updated, highlights below,
* new kernel AA 0.5 (see kernel changelog for details)
* support for ROM Manager if using cLK
* Add latest ROM Manager to cLK build
* update to cLK 1.3.3
* cache moved to mtd cache
* Add ES File Explorer
* Update gmail, youtube apks
enjoy
Ok I am jumping on board and will give this ROM a try will give feedback in a few hrs after ROM has settled in
Update: ROM loaded and runs really smooth, picture messages are blurry - only allows a max 300k message size
added English (US) through MoreLocale2 app
I know this is a work in progress so keep up the great work arif
Update 27Mar11 -
have been using this ROM just over 24hrs and so
fare not to bad
Battery drain is a little higher than what I am used to
Have to remember to us speaker phone when I make first
call after reboot due to Robot voice and subsequent freezing of my phone if I fail to do so.
Also have periodic data connection failure of which I do not
experience on my other HD2 with a diff. ROM.....This was just FYI and not meant to degrade your hard work Arif
stock theme
Here is an initial attempt at doing the Stock theme
http://www.multiupload.com/LL8NO4MB13
feedback would be great
Why sdext doesn't work? I have properly partitioned card which works with other roms, but here my phone states that I have 3mb free space after install. I even re partitioned card without success.
maxld said:
Why sdext doesn't work? I have properly partitioned card which works with other roms, but here my phone states that I have 3mb free space after install. I even re partitioned card without success.
Click to expand...
Click to collapse
Have you used the required config.txt?
Sent from my HTC HD2 using XDA Premium App
Honestly I tried to find it but I'm so blind that I did it without it. Thanks for the help mate.
Edit:
I searched again and still can't find it. Could you upload me one?
maxld said:
Honestly I tried to find it but I'm so blind that I did it without it. Thanks for the help mate.
Edit:
I searched again and still can't find it. Could you upload me one?
Click to expand...
Click to collapse
Look at the first post it tells you how to create one. Its simple open note pad on your computer put in the right details and save it as config.
Sent from my HTC HD2 using XDA Premium App
Yeah, i have read it, but there are only ppp and gps options listed.
maxld said:
Yeah, i have read it, but there are only ppp and gps options listed.
Click to expand...
Click to collapse
Okay try this in create the config.txt like I said and in it put a2sd_mode=data
Sent from my HTC HD2 using XDA Premium App
Thank you kindly for your help, sir. Unfortunately it didn't help, maybe OP will have a trick how to activate sd ext partition.
maxld said:
Thank you kindly for your help, sir. Unfortunately it didn't help, maybe OP will have a trick how to activate sd ext partition.
Click to expand...
Click to collapse
* create a file called config.txt
* add the following contents to the file
a2sd_mode=data
* run "adb push config.txt /sdcard/."
* reboot your phone.
If this doesn't work, then run the following commands
adb shell ls -l /dev
adb shell mount
adb shell df
and let me know the results
Thanks, I'll report results in a moment.
Edit 1: It will be a longer one, because my connection is ridiculously slow and I have to download sdk and jdk
Edit 2: None of your advices helped, still have 3.85 MB of free space.
Anyone have the new version?
giorgib said:
Anyone have the new version?
Click to expand...
Click to collapse
What do you mean writing "the new version"?
There isn't a new version yet, and haven't planned one as yet. But I have some ideas that I wanted to try to fix some of the issues that this ROM has
Most of my time has been spent on doing the CM nightlies and the CWR updates, and getting RM support for the leo. But I will see when I can get time out to do an update here as well.
Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.
Tweeks:
Camera Tweek (You need busybox installed for this), or you can unpack the zip and apply the patch manually/setting the permission corectly.
It will improve the overall video recording quality, by increasing the size limit cap of the video (old setting 600 Kb vs new 1200 Kb)
Custom Firmwares
Reserved
Recovery
CWM WITH ACCESS AT THE SYS_BOOT PARTITION ======>>>>> Bigger chance in bricking your device if you sleep while you flash something.
CWM NON TOUCH / NO ACCESS TO SYS_BOOT
Way to flash:
Version 1)
- enable usb debugging
- install adb drivers
- use the command adb reboot bootloader
- use the command fastboot flash recovery recovery.img
Version 2)
- shut down the phone
- press the volume key minus and power key
- use the command fastboot flash recovery recovery.img
Do not forget to unpack the zip files.
Please have in mind that with the no_sys CWM, you cannot restore the phone to stock using an official update.
Unbricking
Copied from here
Here's a small tutorial for people who bricked their phone while formatting the sys_boot partition in CWM Recovery. When you format that partition, nothing works except a screen shows up saying "RESET FOR ENTRY QPST DOWNLOAD". This screen is also known as the Qualcomm Diagnostic Mode.
Requirements:
A linux distribution (Ubuntu)
sys_boot.img (https://docs.google.com/file/d/0BxJJu-wXKdltTE90SGtEMmFQZHM/edit)
Follow the steps to restore the sys_boot partition:
1. Connect your phone to a pc using the cable
2. Install the drivers if necessary:
https://dl.dropboxusercontent.com/u/17562266/USB Modem Driver.rar
3. Open your terminal
4. Type "lsblk" (without the quotes).
You should see a list, showing every connected disk and partition. Look for a partition with a size around 50M. This is the partition we need, so remember the corresponding name under the 'NAME' column. It can be "sdc", "sdd" or "sde" followed by a number.
5. Cd to the directory you placed sys_boot.img in
cd [filename]
6. Type "sudo dd if=/dev/NAME of=sys_boot.img bs=512
Replace NAME with the name you got from lsblk, and press enter.
The output should look something like this:
3959420000 bytes (3866621 KB) copied, [ time spent], [KB/s]
7. Remove the cable from your device, do a battery pull and try to boot your device
Normally, it should boot correctly. If you formatted the /system partition too, you have to get into recovery mode by holding the upper volume button while booting, until a red screen appears.
If you have any questions, or if this doesn't work for you – let me know in the comments.
Thanks a lot to Adonis K. and globula_neagra for the sys_boot image and pointing me in the right direction.
Credits to DieterHolvoet from arctablet for putting it together.
THX! Much appreciated!
I own this device since today and you Sir made me very happy with your cwm and ability to root.
---------- Post added at 08:19 PM ---------- Previous post was at 07:42 PM ----------
I can confirm. Touchversion of CWM does not work.
File for non-touch CWM seems the same as touch btw. Could you please fix the link? Thx!
Yes, the touch version doesn't work.
The no-touch no-sys version works fine.
Here is the link for the no-touch/no-sys version (taken from the arctablet forums): http://globula.arctablet.com/ARCHOS_50_PLAT/CWM_A50_Plat_NoTouch_No_SYS.img.zip
globula must have misstyped it
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Nash123 said:
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Click to expand...
Click to collapse
I will fix these issues tomorrow.
Thank you!
GEN 11 ?
cajl said:
GEN 11 ?
Click to expand...
Click to collapse
Yes the Archos 50/53 Platinum and Archos 80 Xenon are Generation 11
NO !
it will be announced at IFA and I would see in Berlin
cajl said:
NO !
it will be announced at IFA and I would see in Berlin
Click to expand...
Click to collapse
I could try to convince you that they are Gen11, but you will have to trust me, the update page does not lie.
OK Archos 53 also ...
Anyone know if it's possible to partition the internal memory and internal sdcard together? I'm getting really low in internal space intended for app installations (180mb left, getting insufficient space errors)
Updated the third post with a new touch cwm, test version, i don`t have a platinum to test it.
Adonis, i don`t think is possible, tough you can use directory binder
I need some help with some file from the Archos 50 Platinum, I want to test if the phone function works on Archos 80 Xenon (it should in theory as this is not the first tablet made by Archos/Arnova that has a crippled phone function, my 7C G3 is capable if doing/receiving phone calls)
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Adonis K. said:
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Click to expand...
Click to collapse
Then it will be no touch for the moment, tough is strange, on the Archos 80 Xenon is working fine.
Not having the phone is a big impediment for me to test things, and I have the Xenon only till 28`th, so this is my main platform for testing for now (identical spec with the 50 Plat, even the partition layout is identical , that`s why i believe that the phone function should work)
I will do another try with the touch version from the Xenon in the next days, maybe with will work with that one.
Yes, the directory binding is the same as simlinking
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Nash123 said:
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Click to expand...
Click to collapse
I think you will need the sys_boot recovery for that, or the stock one, the non_sys boot will not allow you to flash stock firmware.
HOW TO ROOT YOUR MICROMAX A58
1. go to settings-> Security-> enable Unknown sources.
2. go to about phone in in settings -> About phone -> tap on the build number several times to enable developer options
3. in settings-> Developer options -> enable Usb Debugging
4. Now download framaroot 1.8.1 apk. download link attached. (Thanks to "alephzain" for this awesome app)
(link to his thread http://forum.xda-developers.com/showthread.php?t=2130276 )
5. install it
6. open and click Boromir exploit
7. voila ur phone is rooted.
8. now reboot to see super su in app drawer
7. check it using root checker app from play store.
{
"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"
}
click thanks if i helped..
CUSTOM RECOVERY SEE BELOW POST
Ctr , twrp, gravity box, link2sd
CUSTOM RECOVERY
Guys this has been developed by @yuweng @dhinesh77 and @carliv (Master Shifu)
Hats off to the guys for their awesome work.
Dont flash cwm recovery only flash CTR or TWRP recovery because our system format is UBIFS..
just download the CTR auto porting tool from the below thread
http://forum.xda-developers.com/showthread.php?t=1825722
Click to expand...
Click to collapse
(see for "Added on Jan 17, 2014
CTR v2.1 for MTK devices with ubifs ONLY " in the thread)
extract and run the program.
don't forget to install adb drivers before using the above tool. you can find the drivers here.. select other option in phone model.
http://www.mediafire.com/download/seg916ycv20cxj7/drivers.rar
ctr recovery is fully functional....
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sorry TWRP recovery not working in this method
Hi here is the fully working TWRP recovery for Micromax A58
Quote:
DOWNLOAD recovery from
http://www.mediafire.com/download/9zpdq057829ltbj/recovery.img
Click to expand...
Click to collapse
OR
from the attachment below
STEPS TO INSTALL:
TO FLASH USING MOBILE
Click to expand...
Click to collapse
Flash using Mobileuncle tools (need a rooted phone)
-->Download the recovery and Put it in root of your SDCARD (ROOT OF SDCARD MEANS DON'T PUT THE FILE IN ANY FOLDER)
-->Open Mobile uncle tools and select Recovery Update
-->Flash recovery file
-->Done
Now reboot to recovery to check.....
Credits:
christiantroy
@yuweng
@Dees_Troy
@carliv
@dhinesh77
@dhinesh77
Source
https://github.com/dhinesh77/Team-Win-Recovery-Project
Click to expand...
Click to collapse
link to @dhinesh77 thread
http://forum.xda-developers.com/showthread.php?t=2615386
Click to expand...
Click to collapse
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STEPS FOR REBOOTING INTO RECOVERY
1. switch of the mobile
2. remove the battery
3. replace the battery
4. hold the power button and volume up button until you see an android robot
5. now press the power button again to go into recovery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Steps for installing Gravity box
download the xposed module apk from the attachment or from
http://repo.xposed.info/module/de.robv.android.xposed.installer
Click to expand...
Click to collapse
1. After installing apk reboot the phone
2. open the app and select download option
3. now browse to find gravity box[JB] (i mean for jelly bean os)
4. download the latest version
5. install it
6.now go back to modules menu in xposed installer app and tick the gravity box option
7. now reboot your phone
8. enjoy using gravity box
https://www.youtube.com/watch?v=O7p2kW8-nnw
STEPS FOR MAKING LINK2SD WORK
Thanks to @abi.z for the scripts
Steps
1. Partition your sd card to have an ext4 2nd partition. 1 gb partiton max (adviceable) (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore. (dont open it)
3. Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. open terminal emulator app. and type the following command without quotes
"su" (press enter)
"mkdir /data/sdext2" (press enter)
"chmod 777 /etc/install-recovery.sh" (press enter)
5.Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
For people who want to use other partitions
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition number
then EXECUTE the script or REBOOT for the changes to take place.
INSTALLING VIPER EQUALIZER FOR QUALITY SOUNDS
I HAVE TESTED VIPER FOR ANDROID FX NOT XHiFI AND IS WORKING GR8 IN OUR PHONES
1. Download, extract and copy ViPER4Android_FX.apk (FX version v2.3.2.2 )to your device.
2. Install the apk as USER app or SYSTEM app is up to you.
3. Run FX app from app drawer, allow root access if asked.
4. When driver installation prompted, choose Yes.
5. V4A auto detects your CPU and show available driver modes
6. Choose your desired selection.
7. After installation done, Reboot device.
8. now open the app and select compatibility mode for audio to work.
TO DOWNLOAD THE APP GO TO THE BELOW FORUM
FORUM LINK:
http://vipersaudio.com/blog/?page_id=48
All stock items for micromax A58
< STOCK ITEMS
DRIVERS : http://www.4shared.com/rar/sWXxgEmM/Mobistel_Cynus_T1_Drivers_x86.html
STOCK ROM : https://drive.google.com/uc?id=0B6-h6iUVgfhJbWRIYW9MNmV0UzQ
STOCK BOOT.IMG : http://www.mediafire.com/view/id21q1m9a34b5dr/boot.img
STOCK RECOVERY : http://www.mediafire.com/view/g8tkf2a7qqv0zpu/recovery.img
SP_Flash_Tool : http://www.4shared.com/zip/xsHShvMw/SP_Flash_Tool_exe_v313320187.html/>
DONT FORGET TO CLICK THANKS IF I HELPED
Click to expand...
Click to collapse
confused!!!!
@dhinesh77 bro link2sd app is not working on my phone what about yours??
Do you know any way to fix it. it says mount script cannot be created, no such file or directory
Can we change ubifs to ext4 format.. Or is there any custom roms possible.
I have installed gravity box via xposed module and its really awesome on our phone.
Waiting for ur reply!!!!!:fingers-crossed:
alanvmathew said:
@dhinesh77 bro link2sd app is not working on my phone what about yours??
Do you know any way to fix it. it says mount script cannot be created, no such file or directory
Can we change ubifs to ext4 format.. Or is there any custom roms possible.
I have installed gravity box via xposed module and its really awesome on our phone.
Waiting for ur reply!!!!!:fingers-crossed:
Click to expand...
Click to collapse
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
dhinesh77 said:
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
Click to expand...
Click to collapse
Oh it hurtz.
Can we flash recovery using mobile uncle tools??? Or we can't? If we can then I all make a tutorial for it here.
alanvmathew said:
Oh it hurtz.
Can we flash recovery using mobile uncle tools??? Or we can't? If we can then I all make a tutorial for it here.
Click to expand...
Click to collapse
I tried with recovery manager it worked, didnt tried with mobileuncle app
dhinesh77 said:
I tried with recovery manager it worked, didnt tried with mobileuncle app
Click to expand...
Click to collapse
kewl ll make one then...... what happened to link2sd bro?? did u try?
or is there any other script that can work for us?
alanvmathew said:
kewl ll make one then...... what happened to link2sd bro?? did u try?
or is there any other script that can work for us?
Click to expand...
Click to collapse
@dhinesh77 bro link to sd any news?????
Rooted but Cannot enter Recovery mode
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
abi.z said:
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
Click to expand...
Click to collapse
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
abi.z said:
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
Click to expand...
Click to collapse
thanks guys it seemes uploaded is corrupted i will check this weekend , meanwhile try ctr recovery its expected to work 100%
---------- Post added at 06:31 AM ---------- Previous post was at 06:30 AM ----------
abi.z said:
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
Click to expand...
Click to collapse
alanvmathew said:
@dhinesh77 bro link to sd any news?????
Click to expand...
Click to collapse
Sry bro i dont have enugh space to make ext parttion on sdcard , so i cant able to check
@dhinesh77
Thnx dude..I was wondering wats wrong with my phone s recovery mode..
As mentioned in my prev post that ctr auto porting tool fails in last step too.tried on winxp.
Waiting for or next upload bro.thanks for your works
BTW will try ctr again toninght
Sent from my Micromax A58 using xda app-developers app
abi.z said:
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
Click to expand...
Click to collapse
Did u install busy box in phone before proceeding. Try installing busy box. Then in ctr try manual porting option and use the stock recovery.IMG. if u did not take back up of stock.IMG I can share it with u. It will work I too had this problem... If u have any doubt ask me.
i am gonna share two roms with you u can use it.
T-09 version rom
http://www.adrive.com/public/RYVRp2.html
T-07 version rom
http://www.4shared.com/zip/wB64yz-vce/A58_T07_2_.html
extract the correct version of rom for your phone and use the recovery.img . you can see the version in about phone option or by removing the battery.
alanvmathew said:
Did u install busy box in phone before proceeding. Try installing busy box. Then in ctr try manual porting option and use the stock recovery.IMG. if u did not take back up of stock.IMG I can share it with u. It will work I too had this problem... If u have any doubt ask me.
i am gonna share two roms with you u can use it.
T-09 version rom
http://www.adrive.com/public/RYVRp2.html
T-07 version rom
http://www.4shared.com/zip/wB64yz-vce/A58_T07_2_.html
extract the correct version of rom for your phone and use the recovery.img . you can see the version in about phone option or by removing the battery.
Click to expand...
Click to collapse
Thanks dude.
@dinesh77 s post helped me to conclude the issue.
Your post led me back on track and thanks for uploading the roms. Although i dint download because of my limited conn speed, itll be of help to someone.
Here's how i solved the issue.
I checked unpacking my existing recovery image and it was corrupted.
I was having a problem since i flashed the corrupted recovery initially, and lateron ctr porting tool was not able extract the existing recovery details for porting.
So i got twrp recovery from your the mediafire link in the first post did a porting and then everything worked fine with ctr recovery.
twrp recovery was running, but backup functionality wasnt working.
Iam not able to use advanced restore from ctr recovery.
All othr functions works from ctr..
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
dhinesh77 said:
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
Click to expand...
Click to collapse
@alanvmathew
Good News bro, I have somehow managed to get link2sd working with fat32.Had to do a lot of trial and error with manual mounting and reformating and reformating..
Was after link2sd till 3:00am
In office now. Will try to reproduce the issues and soon come up with the correct solution for link2sd after iam home.
link2sd
abi.z said:
Thanks dude.
@dinesh77 s post helped me to conclude the issue.
Your post led me back on track and thanks for uploading the roms. Although i dint download because of my limited conn speed, itll be of help to someone.
Here's how i solved the issue.
I checked unpacking my existing recovery image and it was corrupted.
I was having a problem since i flashed the corrupted recovery initially, and lateron ctr porting tool was not able extract the existing recovery details for porting.
So i got twrp recovery from your the mediafire link in the first post did a porting and then everything worked fine with ctr recovery.
twrp recovery was running, but backup functionality wasnt working.
Iam not able to use advanced restore from ctr recovery.
All othr functions works from ctr..
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
@alanvmathew
Good News bro, I have somehow managed to get link2sd working with fat32.Had to do a lot of trial and error with manual mounting and reformating and reformating..
Was after link2sd till 3:00am
In office now. Will try to reproduce the issues and soon come up with the correct solution for link2sd after iam home.
Click to expand...
Click to collapse
Congratulation bro! And please share the procedure here so we can also get benefit of it. Thanks in advance.
Increase internal Memory !! Link2sd Working !! [Use Manual mount Script]
Steps
1. Partition your sd card to have an ext4 2nd partition. I used a second primary partition of 512mb (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore.
3. Mount /system read-write and Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. Using filemanager(root) goto /data and create directory sdext2. or mkdir /data/sdext2 using root terminal
5. Set permissions on the copied file using filemanager(root) as in screenshot or chmod 777 /etc/install-recovery.sh using root terminal.
6. Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Incase you want to test if link2sd will work or not with your current sdcard 2nd partition, issue the commands in terminal
su
mkdir /data/sdext2
mount -t ext4-o rw /dev/block/mmcblk0p2 /data/sdext2
or
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition no.
!!eNJOY!!
abi.z said:
@dhinesh77
Thnx dude..I was wondering wats wrong with my phone s recovery mode..
As mentioned in my prev post that ctr auto porting tool fails in last step too.tried on winxp.
Waiting for or next upload bro.thanks for your works
BTW will try ctr again toninght
Sent from my Micromax A58 using xda app-developers app
Click to expand...
Click to collapse
It seems root access was denied for ctr auto port tool, hence why you failed, reinsure that you have running auto port tool under c:/ ; anyhow I will upload ctr compiled recovery too on this weekend sry or delay
dhinesh77 said:
It seems root access was denied for ctr auto port tool, hence why you failed, reinsure that you have running auto port tool under c:/ ; anyhow I will upload ctr compiled recovery too on this weekend sry or delay
Click to expand...
Click to collapse
@dhinesh77 Ya please upload so that others can use it.. If you want i can upload ported ctr recovery.
It was not root access causing problems,I had flahed the corrupted download to phone initially and then the recovery.img which ctr was reading from my phone was corrupted for autoporting tool to work on, and was failing while extracting the .img..
1 week old Bolt A58 with Root+Gravity+CTR+Link2sd
Everything is fixed now, and i will be gifting it to my father this weekend.
Thanks for help everyone
abi.z said:
Steps
1. Partition your sd card to have an ext4 2nd partition. I used a second primary partition of 512mb (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore.
3. Mount /system read-write and Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. Using filemanager(root) goto /data and create directory sdext2. or mkdir /data/sdext2 using root terminal
5. Set permissions on the copied file using filemanager(root) as in screenshot or chmod 777 /etc/install-recovery.sh using root terminal.
6. Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Incase you want to test if link2sd will work or not with your current sdcard 2nd partition, issue the commands in terminal
su
mkdir /data/sdext2
mount -t ext4-o rw /dev/block/mmcblk0p2 /data/sdext2
or
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition no.
!!eNJOY!!
Click to expand...
Click to collapse
WORKED.......!!!!!!! :laugh::laugh::laugh:
abi.z said:
@dhinesh77 Ya please upload so that others can use it.. If you want i can upload ported ctr recovery.
It was not root access causing problems,I had flahed the corrupted download to phone initially and then the recovery.img which ctr was reading from my phone was corrupted for autoporting tool to work on, and was failing while extracting the .img..
1 week old Bolt A58 with Root+Gravity+CTR+Link2sd
Everything is fixed now, and i will be gifting it to my father this weekend.
Thanks for help everyone
Click to expand...
Click to collapse
Mr.Carliv has updated his recovery version to 2.2 , ported just now and updated in main post , all bugs fixed in ctr recovery too :good:
Read Carefully Before Doing Anything !
Requirement :
- TWRP Recovery TWRP_XT1760_3.1.1_MTKr1.img
- Minimal adb & fastboot
- Installed adb & fastboot drivers
- Moto E4 mediatek variant :laugh:
- Mediatek variant version SKU XT1760 :highfive:
- USB cable :cyclops:
- Unlocked bootloader
- Backup of whole firmware through Miracle Tool :silly:
Bugs :
- Not found yet
How To Enter Fastboot Mode :
- Press power and volume down button along
- When you see START in device screen leave both buttons
- locate to META MODE window only using vol. down button
- It is next to START window
- When you apply commands in fastboot mode
you will see fastboot command execution in this window
How To Install :
- Unpack the zip file first
- Drop TWRP_XT1760_3.1.1_MTKr1.img in this folder
- C:\Program Files\Minimal ADB and Fastboot\TWRP_XT1760_3.1.1_MTKr1.img
- Close this windows now !
- Open Minimal ADB & Fastboot command window
- Type These Fastboot Commands :
- fastboot devices
- fastboot flash recovery TWRP_XT1760_3.1.1_MTKr1.img
- TWRP Recovery installed now !
How To Boot into TWRP :
- Press power button and volume down button along
- When you see START in device screen leave both buttons
- locate to recovery window using vol. keys
- Press power button once
- Now your device boot in TWRP mode
- Done for now !
How To Disable Verity in Order To Boot into System :
( Follow this step if you were going to install TWRP recovery only
else if you want TWRP installed and a rooted device than follow below step. )- Place no-dmverity zip file in external SD_CARD
Download link :
http://www.mediafire.com/file/m0w6zu83am6z38i/no-verity-opt-encrypt.zip
- Disable Read-Only Option in TWRP Recovery
- There select allow modifications, swipe, wipe data & cache
- Again boot into TWRP
- Install no-dmverity
- Reboot to system
- Done !
How To Root Moto E4 Mediatek Variant SKU XT1760 :
( Follow this step if you want installed TWRP recovery and a rooted device ! )
Thread link :
https://forum.xda-developers.com/moto-e4/how-to/moto-e4-guide-to-rooting-international-t3657328- Still unable to Root this device with SuperSU & Magisk
- SuperSU failed to mount "/" Rootfs
- Magisk failed to load image file
Downloads TWRP Recovery :
http://www.mediafire.com/file/emz8j0smqdsbc8g/TWRP_XT1760_3.1.1_MTKr1.zip
Credits :
@squid2
for original twrp recovery
and ported by me, from qualcomm variant to mtk variantOriginal Thread Link :
https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
Ok stream of development started...thanks karthi for this effort.
Kartik bro does it have dm-verify issues? Do we need to disable dm-verify on first boot to twrp?
drganbds said:
Ok stream of development started...thanks karthi for this effort.
Kartik bro does it have dm-verify issues? Do we need to disable dm-verify on first boot to twrp?
Click to expand...
Click to collapse
Thread Updated !
Refresh for new content
@drganbds search for no-dmverity.zip you will find one.
at this time my internet connection is slow cannot upload the file right now.
Good to have a TWRP for both variants.
Where did the term "International" come from? Both the Qualcomm and Meditatek versions of the Moto E4 are sold in several countries, so using the term "International" to refer to the MediaTek version seems confusing to me. Users may think "International" works on phones sold in all countries. I think it would be better to name this as TWRP for the MediaTek version rather than "International".
squid2 said:
Good to have a TWRP for both variants.
Where did the term "International" come from? Both the Qualcomm and Meditatek versions of the Moto E4 are sold in several countries, so using the term "International" to refer to the MediaTek version seems confusing to me. Users may think "International" works on phones sold in all countries. I think it would be better to name this as TWRP for the MediaTek version rather than "International".
Click to expand...
Click to collapse
But not all users know what mediatek is so It probably makes sense to put "(mediatek)" in the title
mendelgordon said:
But not all users know what mediatek is so It probably makes sense to put "(mediatek)" in the title
Click to expand...
Click to collapse
Yes, and the model numbers should be specified also. Users just need to know what their model is.
squid2 said:
Good to have a TWRP for both variants.
Where did the term "International" come from? Both the Qualcomm and Meditatek versions of the Moto E4 are sold in several countries, so using the term "International" to refer to the MediaTek version seems confusing to me. Users may think "International" works on phones sold in all countries. I think it would be better to name this as TWRP for the MediaTek version rather than "International".
Click to expand...
Click to collapse
Thanks for the suggestion
amarc78 said:
Yes, and the model numbers should be specified also. Users just need to know what their model is.
Click to expand...
Click to collapse
updated :good:
@squid2 @amarc78 @mendelgordon @drganbds
i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side
kartik verma said:
@[email protected]@[email protected]
i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side
Click to expand...
Click to collapse
Sorry dude im eager to help you but I have very very little knowledge on Linux commands...because I'm a doctor
drganbds said:
Sorry dude im eager to help you but I have very very little knowledge on Linux commands...because I'm a doctor
Click to expand...
Click to collapse
isn't a big deal. i also a medical stream student
kartik verma said:
isn't a big deal. i also a medical stream student
Click to expand...
Click to collapse
I was playing with Linux (Ubuntu) on unpacking and packing boot image for cpu governors, tweaks etc, and with Android kitchens for creating so many roms for grand Quattro device but since 4years I haven't done anything and i stopped it...that's y I couldn't help you...
drganbds said:
I was playing with Linux (Ubuntu) on unpacking and packing boot image for cpu governors, tweaks etc, and with Android kitchens for creating so many roms for grand Quattro device but since 4years I haven't done anything and i stopped it...that's y I couldn't help you...
Click to expand...
Click to collapse
ok :crying:
kartik verma said:
@[email protected]@[email protected]
i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side
Click to expand...
Click to collapse
Isn't kernel adiutor able to add init.d support (not really, but it works)
Edit: Where are you putting those commands? If in TWRP, try in a file explorer like mixplorer. If in a file explorer, try twrp.
mendelgordon said:
Isn't kernel adiutor able to add init.d support (not really, but it works)
Edit: Where are you putting those commands? If in TWRP, try in a file explorer like mixplorer. If in a file explorer, try twrp.
Click to expand...
Click to collapse
seriously very strange problem.
init.rc unable to set file permission.
kartik verma said:
@[email protected]@[email protected]
i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side
Click to expand...
Click to collapse
Can you upload the unmodified boot.img for me?
Sent from my LGLS755 using XDA Labs
amarc78 said:
Can you upload the unmodified boot.img for me?
Click to expand...
Click to collapse
sure...
kartik verma said:
sure...
Click to expand...
Click to collapse
https://www.mediafire.com/download/u0ex0htrtmutc15
link
kartik verma said:
https://www.mediafire.com/download/u0ex0htrtmutc15
link
Click to expand...
Click to collapse
Try this. Init.d should be enabled. I also removed dm-verity and force encrypt and made it insecure. I wanted to make a flashable zip but I have no device info to do so. You'll have to extract it and flash the img. You might need to add the etc/init.d folder and set it's permissions manually. Let me know if it works ok.