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:
Related
Welcome
I wrote this post to help people get their Archos g9 tablet running custom roms. If you have any improvement ideas, please post them so I can make this better source of information.
List of content:
Post 1
What is recovery
What is SDE and how to install it
-Also SDE for 4.0.25
List of most commonly used roms
How to install custom roms
How to install offical rom
How to multiboot android 4.0 based roms
Installing 3G stick and Huawei modems support.
Post 2
Change symlinks/binds.
Installing ADB
Installing SuperCharger
Installing Chainfire3D
But why?
FAQ
Useful links
What is recoveryYou can boot to recovery menu by holding volume- while booting your device. From recovery meny you can calibrate your touchscreen, wipe data and do this kind of stuff. Installing SDE creates new entry to recovery menu, called Special Developers Edition. There you can remove android kernel, flash new, export hdd and data. In recovery move up and down with volume + and -. Select by pressing power button
What is SDE and how to install itSDE is shortened word from Special Developers Edition. After SDE is installed, your tablet is able to boot to official rom, recovery, and SDE rom. Most of the roms advice you to use "Remove android kernel" from SDE before you install kernel. When you remove your android kernel from there and install kernel from custom rom, your archos boots directly to custom rom. If you don't delete it, your device boots to official, but keeping volume - while booting gives you change to boot to SDE.
There are 3 guides how to install SDE. Official SDE watermarks your device for archos (there is no watermark on screen ), so they can detect you have installed SDE in some point. It stays even if you remove SDE. Official way is more safe. Also, it removes "only" software warranty. If your devices powerbutton, Usb-port or etc brokes, you can still send it to warranty. Link to official SDE install guide. Big thanks for Shano56.
Then there is unofficial, a bit more dangerous method. It doesn't watermark your device, but is more complicated. Guide tells that it's outdated, but it worked for me. I used official 4.0.4 version while installing. Link to the guide. Big thanks to Shano56.
4.0.25 Guide, by surdu_petru
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
Click to expand...
Click to collapse
List of most commonly used romsThese roms are most commonly used. Most of them are still being developed. I also included link to rooted official honeycomb, because some people have better touchscreen responsibility with it.
ParanoidAndroid 3
Cyanogenmod 10, 4.2 mockup
Cyanogenmod 10
AOKP ROM
[email protected]
Clean_Slim&Fast(Based on official 4.0.25!)
Ubuntu. This requires special kernel, which is compatible with official android 4.0.4Overclockable stock rom
Early CM9
Stock ICS rom with root & busybox
Stock honeycomb with root. (FYI, kernel requires renaming while installing)
How to install custom romsCustom roms have different installing methods, but basic idea is same. You move image file with specified name to specified location.
When coming from stock rom or whengoing to stock rom:
CyanogenMod 10, AOKP, CyanogenMod 9
surdu_petru said:
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
[email protected], Ubuntu, Root 4.0.7 Clean_Slim&Fast
surdu_petru said:
Install :
- copy archos.ext4.update(archos.ext4 in case of Clean_Slim&Fast) in /mnt/storage/ , you can use this command > adb push archos.ext4.update(remove .update if Clean_Slim&Fast) /mnt/storage/
- go to SDE -> Developer Edition Menu -> ( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- after everything was installed - please reboot your device !
Click to expand...
Click to collapse
Honeycomb
Install like Cyanogenmod and AOKP and others, but rename initramfs.cpio.gz to initramfs.cpio.lzo
How to install official romDownload official 4.0.7 rom from here.
Now boot to recovery (hold volume- while booting) and choose update firmware.
Now there should be noew drive in your pc. Drop the downloaded firmware_archos_it4.aos to there and press ok in recovery. Keep usb plugged in while installing. It should take around 30 seconds to 2 minutes. Now choose ok again. your tablet should now reboot to stock rom.
4.0.24 Official is owrking on some devices, but because it won't work on all, i won't cover it here(yet)
How to multiboot android 4.0 based romsInstall modified initfram from this topic. Use the zimage from the rom you want to multiboot. AFAIK you can multiboot with following combos:
[email protected], Ubuntu (download newer kernel from later pages.), Root 4.0.7
and
AOKP, CyanogenMod 9.
You cant use [email protected] and AOKP because they do not use same kind of data. That means that after you have run first rom, the second will bootloop. That is also why it requires wiping data when changing from stock to aokp and vise versa.
Detailed:
Download dmenu-0.3a.zip, and extract initframfs to desktop. Then download [email protected] and stock 4.0.7 rooted. Extract Image files and zimage from either one of the roms. Now just instal like described in earlier section, while using initframfs from multiboot and kernel from other rom.
Installing 3G stick and Huawei modems support.
Trevd made a package to add 3G stick and extra Huawei modems work for AOKP and generally all ICS ROMs. This guy is awesome because he also made some Huawei modems work.
trevd said:
Hi surdu_petru and AOKP fans.
Great work as always, It's not a rom i'll ever use but It's the first time I've loaded an AOKP Rom, I like notification layout, I'll be having that away for my own personal rom Anyway I was more just passing through and noticed 3G was not working yet. As seen as though that seems to be my speciality and preoccupation/addiction for the last 9 months I thought I do something to remedy that situation for you.
Here's an hotfile link to download the update [ 3g-archos-aopk.7z ] this should contain everything you need to get the Archos 3G Dongle, just for ****s and giggles as a extra bonus i've also included the huawei support file as well :good:
Installation:
From a command prompt / bash terminal
Code:
7z x 3g-archos-aopk.7z
adb push 3g /
adb shell reboot_into sde
extracting the 3g-archos-aopk.7z will give youu a 3g directory in you current directory, we then push the contents of the 3g directory to the root direcotry on the device. This operation is recursive.
Have Fun!
What follows is a detailed explanation of what files and modifications are required to add 3G support.
Archos 3G Stick
The changes / additions to add this functionality breaks down like this ; The following required binary's were on the device already:
** /lib/modules/hso.ko is insmod'd by the device specific init file /etc/init/init..rc
Code:
/lib/modules/hso.ko[B]**[/B]
/usr/bin/usb_modeswitch
/system/lib/libtcl-ril.so
/system/bin/rild
/system/bin/pppd
/system/xbin/chat
/etc/ppp/init_pppd_datakey
/etc/ppp/ip-up-datakey
/etc/ppp/ip-down-datakey
/etc/ppp/peers/datakey
/etc/chatscripts/datakey_start
/etc/chatscripts/datakey_stop
/etc/usb_modeswitch/1bbb_f000
The following required services were already defined in the device specific init.rc's located in /etc/init/init..rc ,
*** switch_ms_3g defined by /etc/init/init.archos.rc
Code:
service service switch_ms_to_3g[B]***[/B]
service pppd_secrets
service pppd_datakey
service ril-daemon
So what's missing? you may ask as this pretty much is everything that is needed by the Archos 3G Stick.
Standard Archos Roms use the UsbKeyManager.apk system service to start the switch_ms_to_3g and ril-daemon service's. I replace that with my own ueventd handling native service and add an additional to configuration file keep everything clean
Code:
/system/bin/hotplugd
/init.dongle.rc
I've added the following line to the top of the /init.rc
Code:
import init.dongle.rc
All that is left to do now is enable mobile networks on the rom. I used apktool to decompile the /system/framework/framework-res.apk and change the following values
res/values/bools.xml
Code:
true
true
res/values/arrays.xml
Code:
wifi,1,1,1,-1,true
mobile,0,0,0,-1,true
mobile_mms,2,0,2,60000,true
mobile_supl,3,0,2,60000,true
mobile_hipri,5,0,3,60000,true
mobile_fota,10,0,2,60000,true
mobile_ims,11,0,2,60000,true
mobile_cbs,12,0,2,60000,true
wifi_p2p,13,1,0,-1,true
"1,1"
"0,1"
"7,1"
"9,1"
res/values/strings.xml
Code:
ppp1
Huawei Support
The extend this functionality further I added the following files
Code:
/etc/ppp/init_pppd_gprs
/etc/ppp/ip-up-gprs
/etc/ppp/ip-down-gprs
/etc/ppp/peers/gprs
/etc/chatscripts/gprs_start
/etc/chatscripts/gprs_stop
/etc/usb_modeswitch/ [ numerous configurations files ]
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
We also need to chmod 6755 /system/bin/pppd but that is handled/checked in the /init.dongle.rc so there is no need to do that manually
Click to expand...
Click to collapse
Change symlinks/bindsTrevd wrote guide to let people know how to change binds. That way you can move large folders, like Gameloft games and navigator files to ExternalSD, saving InternalSD space.
trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
Installing ADBADB comes from word android development bridge, and it allows you to debug, move files and get shell access to your tablet.
Archos said:
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
Go to the Android SDK page and download the latest SDK for your operating system.
For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
Click to expand...
Click to collapse
Running adb from anywhere
steviewevie said:
We need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Click to expand...
Click to collapse
sources:Archos, steviewevie
Installing SuperchargerSupercharger is a multiscript which makes the tablet work much better. Its created by Zeppelinrox, and its official topic is here. We are using also script manager in this guide. That way we can make MinFrees and OOM apply.
In this guide we'll use Apex launcher which is moved to /system/app for our default launcher.
We are also using adb to configure and run Supercharger.
Because stock launcher is odexed and i am not writing how to deodex, we are not using it.
First make sure apex is your default launcher. This can be tested by pressing home button in homescreen.
If it show mini previews of your homescreens, apex is your default launcher.
Now lets begin:
go to here and download newest file. At
the time of writing, it is Update 9_RC11_test6. Move it to your adb folder.
Then open commandline. This can be opened with windowskey + R and writing cmd. Navigate
to adb folder using cd command. I have made adb to run from anywhere, so i just navigate to the downloaded file.
Now use command "adb push v6* /mnt/sdcard" then use command "adb shell". Now you should have
shell access to your tablet. Now do following
su
cd /mnt/sdcard
sh V6* /remember capital V)
Supercharger script should open now. After presentation, script should print after telling your busybox version
"com.anddoes.launcher is the home launcher!" Now continue install. Supercharger will tell you everything you need to know.
So just follow the instructions. After choosing kernel tweak, you get bunch of permission denieds.
We can't help them, so lets just continue.I recommend on using all the tweaks that you can,
but it is your choise do you want to use or not. After all the selections are selected and your in
driver panel, choose number 32. It'll reboot your tablet and wipe dalvik. When the tablet has booted, lets run supercharger script again.
So write these again:
su
cd /mnt/sdcard
sh V6_Super*
After getting to drivers panel, you notice that minfrees are not in effect, and neither is OOM Grouping Fix BUT if they are, you can ignore this step..
Install script manager from market and open it. Give it root permissions and navigate to /system/etc/init.d
press SS99SuperCharger to open its settings. Now press the Su button and then Boot button.
Now press save, and then click it's name which appers to right. Then press back button and reboot.
Now Minfrees should work, and OOM too.
Now you can run 22 if you want to try it. Supercharger is now fully working.
Installing Chainfire3D
Chainfire said:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Click to expand...
Click to collapse
It is very useful for running gameloft games and other games too. I recommend buying it. There are some plugin for it, but i'm not going to tell you about it now.Play store link.
After downloading it, open it and choose "Chainfire3D Driver" and from there "install". Then confirm it and tablet should reboot. Now reopen it and choose "Default opengl setting". From there you can tweak 3D performance if some games lag. Also, if you install plugin, there you can apply them. I personally use "reduce texture quality".
But why?
This section is to point few reason why to follow these guides. Lets begin:
SDE
Well, you should install this if you want to customize your tablet. If your happy with your tablet running stock, you don't need this, or any other guides.
Custom roms/kernels
Custom roms allow you to use root, they make your tablet faster and add extra functionality. This "functionality" includes: Overclock, run init.d scripts, enable both cores with all governors, root and themes. The benefits are not limited to these, but I could name this quickly. If you wan't to try something which is close to stock, but still has root and some custom functionalities, i would recommend deodexed 4.0.7, or [email protected]
Install official roms
These roms do not require SDE, but will not include root or anything fun . Updating your official rom has many benefits. They include fixes and boost your tablets performance.
Multiboot
Multibooting allows you to have 2 or more roms, which you can choose which to boot on startup. I would recommend this if you want to test functions with root, but still have "backup plan" if testing rom renders unbootable.
3G support
Basicly this allowes some extra huawei 3G sticks to work. There is no list of working stick, you just have to try and hope.
Change symlinks/binds
These allow you to "move" eg. gameloft games to external sd, and allow you to acces your externalsd via internalsd folder.. That way your gamedata does not eat the valuable internalsd space.
ADB
You need this to transfer rom to your tablet. It is also required when you sent logcat reports to help remove bugs.
SuperCharger
This makes your tablet work more fluid. I personally install supercharger to all my android devices. It removes need for task killer, and makes the device work better. Everyone has different results, and it costs only time to install, so i would recommend installing it.
Chainfire3D
This tool allows you to play games made for other GPUs and it can tweak application graphics. You can make the game look worse, but run better or adjust the grphics for a bit higher, so the game looks nicer.
FAQ[/CENTER]
These questions and answers are collected from various sources.
surdu_petru said:
How to activate second core for all govenors in surdu_petrus roms?
To activate the second core, you need the following steps :
- copy /system/S1tweak in /system/etc/init.d/ or ( > adb shell ; # cp /system/S1tweak /system/etc/init.d ; # exit )
- open No-frills CPU Control :
- choose the desired Governor ( but not hotplug ) !
- choose the desired frequency , but not overclocked ! ( when the device will boot - will open with the selected frequency , so please choose max. frequency = your max. stock frequency )
- check "Apply on boot"
- check "Applay"
- check allow if superuser asked permission
- reboot your device !
- Now , both core will be used in any selected Governor ( other than hotplug ! ).
Click to expand...
Click to collapse
What modems does Trevds mod support?
trevd said:
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
Click to expand...
Click to collapse
Shano56 said:
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Click to expand...
Click to collapse
[/quote]
Useful linksSome link i consider useful are here:
G9 101 16GB 1.5GHz Teardown! (Lots of Images)
XBMC for android
Want faster GPS? Follow this guide
3th just i remember something to add. Comment and give me some feedback. It helps me to make this topic useful for beginners, and for those who seek info.
I meant to edit first post... well, this works as 4th reserved then.
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
trevd said:
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
Click to expand...
Click to collapse
Thanks for the feedback.
I removed the part which had github link, and modified the AOKP section to tell it works with all ICS ROMs.
I'll included your mini guide. I might even have some use for it myself...
Sent from my GT-I9100 using xda app-developers app
help me for multi boot ubuntu ics bleuv03
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
muti642 said:
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
Click to expand...
Click to collapse
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
muti642 said:
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
Click to expand...
Click to collapse
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
THX
julle131 said:
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
Click to expand...
Click to collapse
Thank you thanks you it works well, I do not use the right kernel or the good image of ubuntu. ps: the touchscreen does not work but using the OTG is perfect.
thank you again julie :good:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
solrakk6 said:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
Click to expand...
Click to collapse
Yes, you must use adb. I assume your "untoot" means unrooted. You use cd command to navigate to your adb folder and from there to platform-tools. Also drop archos.ext4.update to there. Then use the adb command to move the file. Moving file to that location does not require root.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
hondacity said:
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
Click to expand...
Click to collapse
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
hondacity said:
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
Click to expand...
Click to collapse
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
http://update.archos.com/9/gen9/gen9_4.0.26/firmware_archos_it4.aos
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
hondacity said:
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
Click to expand...
Click to collapse
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Dear,
I applied same as you say but ending on same 221 error. Any thoughts please.
Best regards.:crying:
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.
Rooting Ascend P1 U9200 B315 EUI1.5 JB v4.1.1
----------------------------------------------------------------------------
Anyone wanting to root there Ascend P1 U9200 phone after the new firmware update, here are the files, and info you need, to do so...
First off, plug UR phone in switch it on and let Windows search for the driver, Then click "Let me choose..." or "browse for it..." or similar. Then select "Let me choose which driver to install", then click "list of drivers" or similar, Then click the one near the top that has adb or similar in the title, it don't matter if you choose the wrong one, it just means it wont connect and you'll have to redo this part again and pick a different driver.
Remember!! You MUST run these commands as Administrator.
1. Download the files below, extract them to a folder, preferably one without any spaces in the path, i.e.. C:\U9200Root\ should do perfect.
3. Right Click the "Click-To-Root-U9200.bat" file and under compatibility options click run as administrator or the like.
4. Run (Double Click) the Click-To-Root-U9200.bat (As Administrator!) (or right-click then, "run as administrator...")
4. Reboot your fone and click yes on your fone to install SuperUser.
that's it, your rooted
for those wanting to do the commands there self...
1. Download & extract the files to C:\U9200Root\
2. In the CLI type: "C:\U9200Root\adb reboot bootloader"
3. Then "boot TWRP.img"
4. Then Restart your fone and choose yes to install SuperUser
PS if you've not got much space left in your system partition you may have to delete something from /system/app/ to make space for the SuperUser files.
REMEMBER the space reported on your fone by android is the space on your data partition/memory & sd card and not the system partition!
You can check how much system data etc space you have left from terminal if u have it installed, or on the TWRP recovery which you will have just installed.To do this, Reboot the fone holding the Vol. Up Button, click on advanced then terminal then type "df -h" without quotes if system partition is less than say 10-20mb free then delete maybe, uneeded languages?, chrome.apk?, GSM_Maps.apk? or the like, then reinstall them to the /data/app part later. Since many of these apks get updated and the old ones left undeleted in /system/app/ anyways, I always move the system apks updates from /data/app to /system/app/, makes things a lot tidier and saves a lot of space both in /data/app and /system by not having two of every apk file youve ever updated just remember to copy the libs to /system/lib(s)
Anyways hope I helped someone with this...
cheers John -G-
PS Please Click on Thanks to Thank me as i have 0 in my Thanks Meter lol
PS I moved this to here as it was added to the end of an old un-related topic sooo.... John -G-
ask me any questions you have, do you like my multi color dos txt in my bat file (Coders will get it,its unusual and very hard to do with many colors )
sorry for been so long but i never knew no one would move it or stick it ???? and i was in jail for a while there so,,,
...Good Luck Rooting/Moding!!!
Software LOL
Heres The Software LOL..........
here all my drivers
the drivers------->>>>
shall stonri
sonnettie said:
the drivers------->>>>
Click to expand...
Click to collapse
Where can I find blaze driver?
Hi
After adb reboot bootloader you can also install CWM with fastboot :
fastboot flash recovery clockworkmod.XXXX.img
With CWM you can backup your phone (always a good idea )
After rebooted in CWM install SU with any zip file (ex : SU___Busybox_1.20.2_Flashable.zip )
phoenixpb said:
Hi
After adb reboot bootloader you can also install CWM with fastboot :
fastboot flash recovery clockworkmod.XXXX.img
With CWM you can backup your phone (always a good idea )
After rebooted in CWM install SU with any zip file (ex : SU___Busybox_1.20.2_Flashable.zip )
Click to expand...
Click to collapse
Worked like a charm.
It's what i did with my phone, ans cwm saved me a couple of times
Envoyé depuis mon U9200 avec Tapatalk 4
How to remove TWRP...? I want to update U9200-EM-UMTS-V100R00G411D00B336....thanx in advance.
Stuck
My U9200 is just stuck on the HUAWEI logo when you boot it...
And the cmd application just keeps saying < waiting for device >
Any help is appreciated...
with B336 this method doesn't work.
EDIT:
The problem is not in TWRP or CWM; the problem is that there is not enough space in folder /system/app.
From TWRP I went to "Advanced" and then "file manager"; here from the /system/app I deleted all the languages other than Italian-pack (my language), chrome.apk and gsm-map.apk. Then I flashed SU_flashable and after boot-up SU was finally installed.
It seems that the difficulty of obtaining root permissions in all stock roms from b105 onwards is precisely linked to the lack of space in the / system / app.
I hope to be helpful to those who find themselves with the same problem.
Ricolaa said:
My U9200 is just stuck on the HUAWEI logo when you boot it...
And the cmd application just keeps saying < waiting for device >
Any help is appreciated...
Click to expand...
Click to collapse
you need the fastboot drivers or install hisuite from hauwie
where what is a Blaze driver? It doesn't work!! It asks for the blaze driver which I cannot seem to find!!!!
How can I go back to the stock firmware from CWM ignore if I am posting on a wrong thread
cVinu said:
How can I go back to the stock firmware from CWM ignore if I am posting on a wrong thread
Click to expand...
Click to collapse
Just downloaded the stock rom and flash it with your recovery.
Sent from my U9200 using xda app-developers app
awaisthebest said:
Just downloaded the stock rom and flash it with your recovery.
Sent from my U9200 using xda app-developers app
Click to expand...
Click to collapse
I recovered stock recovery and flash with B123 but showing error msg installation failed!!!!!!
hi im having some issues trying to get the SU, i cannot erase the .apk contained in /system/app in order to gain more space.
- i cannot see any folder inside of system folder just one called /system/bin
i really dont know if that really would be the problem because i checked with "df" command and i see everything righ
but when i reboot even if i swipe to accept the configuration or install de SU.zip archive anything happend.
i will appreciate your help, thx!!
kannox said:
hi im having some issues trying to get the SU, i cannot erase the .apk contained in /system/app in order to gain more space.
- i cannot see any folder inside of system folder just one called /system/bin
i really dont know if that really would be the problem because i checked with "df" command and i see everything righ
but when i reboot even if i swipe to accept the configuration or install de SU.zip archive anything happend.
i will appreciate your help, thx!!
Click to expand...
Click to collapse
Sounds like you need to go to [mount] the check the unchecked boxes well at least [system]
sonnettie said:
Sounds like you need to go to [mount] the check the unchecked boxes well at least [system]
Click to expand...
Click to collapse
Done! Thank you all!
free space
please tell me how i free space to root android because it stuck in hawei logo it said you cant delete files tnx lot sorry for my bad english!
Thanks!
Thanks!
Worked on Linux:
Code:
> sudo apt-get install android-tools-fastboot android-tools-adb
> adb reboot bootloader
> sudo fastboot flash recovery TWRP.img
> sudo fastboot boot TWRP.img
I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THIS GUIDE.
This is primarily for D802 users. However, people with other variants have had some issues and asked for help, so I have added some files here to help them as well.
PREREQUESITES
1) You must be rooted.
2) Then download one of the following files:
2.6.3.3
IMG
Download the D802 img file here.
Download the AT&T img file here.
Download the VZW img file here.
AUTO
Download the automated D802 file here.
Download the automated AT&T file here.
Download the automated VZW file here.
ZIP
Download the ZIP if flashing from a different TWRP version, or CWM: D802, AT&T, VZW
NOTE: If USB-OTG does not seem to be working on TWRP 2.6.3.3, please revert to 2.6.3.2. if this feature is needed.
Themes - Samurai Champloo
Download the theme itself here.
Download the Flashable ZIP of the theme here.
Download the Flashable D802 TWRP 2.6.3.3 and theme here.
2.6.3.2
Download the D802 img file here, or the latest official software F320K img file here.
Download the automated D802 file here, or the latest automated official software F320K file here.
Download the ZIP if flashing from a different TWRP version, or CWM: D802, F320K, TMO, VZW
INSTALLATION
Auto-Method
1) Extract the contents of the RAR file.
2) Double-click "Install.bat".
3) Prompt will open, click any button to proceed.
4) RSA Fingerprint message will appear on the phone (accept).
5) After installation procedure, type "y" and press enter to reboot into recovery!
1st Manual Method: Initiate ADB and use the following code.
Code:
[COLOR="DarkOrange"]REPLACE "XXX" WITH THE ACTUAL IMG NAME! DO NOT TYPE THE ORANGE WRITING![/COLOR]
adb push XXX.img /data/local/tmp/XXX.img
adb shell
[COLOR="DarkOrange"]IF YOU DONT SEE A # prompt, type su to get it.[/COLOR]
cd /data/local/tmp
dd if=/data/local/tmp/XXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[COLOR="DarkOrange"]Be sure to replace "data/local/tmp" with the actual place your img is stored.[/COLOR]
exit
adb reboot recovery
2nd Manual Method: Place the img on your phone, then use a terminal emulator app with the following code.
Code:
[COLOR="DarkOrange"]REPLACE "XXX" WITH THE ACTUAL IMG NAME! DO NOT TYPE THE ORANGE WRITING![/COLOR]
su
dd if=/data/local/tmp/XXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[COLOR="DarkOrange"](Be sure to replace "data/local/tmp" with the actual place your img is stored.)[/COLOR]
Optional Method: If you want to run some safety checks first, use loki [method here as first option].
INSTALL THEME MANUALLY
1) Connect your phone to your PC.
2) Go into your "internal storage" (internal SD card).
3) Find and open the TWRP folder.
4) Add a folder called "theme".
5) Place the ui.zip into the "theme" folder.
ENTER RECOVERY
Method 1: Hold the power button + volume down button until the LG image appears. Once it does let go of the buttons then immediately push and hold them again until recovery boots.
NOTE: The method above will arrive at the "hard reset" area, but when choosing hard reset, it will take you to TWRP (without actually resetting).
Method 2: Download the free app "Rebooter" from Google Play. If you have root, you will be able to select to reboot into recovery (among other options).
SLOW WIPE CACHE FIX
1) Once in TWRP, go into Settings.
2) Check off the box, "Use rm -rf instead of formatting."
3) Go back and now go into Wipe.
4) Wipe Cache (or another option with wiping cache).
Credit: Credit goes to Dees_Troy and wolfgart, djrbliss who made all recoveries for this phone possible, WACOMalt for his steps, and thecubed for his auto-install code.
USB-OTG
To access USB-OTG devices, go into the desired area (Install, Backup, or Restore). Select "Internal Storage" at the top. Press your USB-OTG device. It may take a second to show as selected on the screen. Once selected, press OK.
If your device does not show up, you can first try going to Mount and check off the USB-OTG box. If it doesn't allow you to check the box, then it doesn't support that device.
NOTE: It may not work with OTG cables and USB devices...
MISC.
Folder Name - There is an "issue" with the date and time [1970]. This issue is reflected in the backup folder names. There are two options to change a backup folder name:
Go into recovery and select Restore. Select the folder you wish to rename. There should now be an option to change the backup folder name.
Go into your TWRP folder by connecting to a PC or using a file explorer and change the backup folder name.
Time Zone - The time zone may be wrong but can be changed in Settings.
SUPPORT
Please check previous posts to see if your question has been answered prior to posting (there is a good chance it has).
Please always include with whether you are rooted or not.
Please always include the variant you are using.
Please always include the method you used.
Please always explain what happened in as much detail as possible.
Anything else that may be relevant.
Otherwise, you might have to wait for others to help you...
now for the mods and custom roms (hopefully kernels too)!!!! Thanks bros!
Thank you for all built hardwork. Was waiting for this.
-LG G2
Thank
Sent from my LG-D802 using Tapatalk 2
Thank you ! Flash successfull on my D802.
But when I want to wipe cache + dalvik cache, it stay on "wipe cache", it's normal issue ?
When I used Wipe Cache it took a long time to finish.
Ok thank you
Like 10 minutes or more ?
Envoyé depuis mon LG-D802 avec Tapatalk 4
I don't recall the exact time, but I would say at least 10 minutes.
Heatshiver said:
I don't recall the exact time, but I would say at least 10 minutes.
Click to expand...
Click to collapse
I have the same. But its not 10min. It is one min. Maximum two.
Sent from my LG-D802 using xda app-developers app
cosmique said:
I have the same. But its not 10min. It is one min. Maximum two.
Click to expand...
Click to collapse
I've noticed the time changing for certain things. One restore I did took nearly 30 minutes! I did restore after that took less than 10. As long as it works, that's all that matters! :good:
I'm on a Recovery Loop. Selected Reboot > System and it keeps rebooting to TWRP.
Used Flashify btw.
m0ngstr0us said:
I'm on a Recovery Loop. Selected Reboot > System and it keeps rebooting to TWRP.
Used Flashify btw.
Click to expand...
Click to collapse
Did you have a recovery before this installed? If so, what recovery? Did you have a good WiFi connection when you downloaded the file (i.e @home, @restaurant, etc.)? Did you try any other methods before flashify?
This should be fixable in either case. If you have a backup from before, I suggest restoring. If not, then you may have to follow this guide to unbrick your phone.
Oddly enough, I'll be in Singapore tomorrow, but I won't be able to reply until late night.
Works perfectly. Thanks!
Sent from my LG-D802 using xda app-developers app
Heatshiver said:
Did you have a recovery before this installed? If so, what recovery? Did you have a good WiFi connection when you downloaded the file (i.e @home, @restaurant, etc.)? Did you try any other methods before flashify?
This should be fixable in either case. If you have a backup from before, I suggest restoring. If not, then you may have to follow this guide to unbrick your phone.
Oddly enough, I'll be in Singapore tomorrow, but I won't be able to reply until late night.
Click to expand...
Click to collapse
Heya! Restoring as we speak. Home networks pretty stable.
Currently downloading the firmware. I can see that the system was not mounted on TWRP. Hence the Recovery bootloop.
Jumped from the Samsung era, gosh I didnt know LG doesnt have much support.
Once back up, bahhh imma just remain stock till more Devs pops up.
Cheers man.
m0ngstr0us said:
Heya! Restoring as we speak. Home networks pretty stable.
Currently downloading the firmware. I can see that the system was not mounted on TWRP. Hence the Recovery bootloop.
Jumped from the Samsung era, gosh I didnt know LG doesnt have much support.
Once back up, bahhh imma just remain stock till more Devs pops up.
Cheers man.
Click to expand...
Click to collapse
Feel free to try CWM, it's much easier to install, and also has a touch-interface.
Heatshiver said:
Feel free to try CWM, it's much easier to install, and also has a touch-interface.
Click to expand...
Click to collapse
I need sleeppppp ~ T.T Lol! Its 1:14am here man. Getting up at 6am later. Prolly another round (with CWM) over the weekends!
I travel to the airport in 4 hours, no rest for the wicked!
Heatshiver said:
I travel to the airport in 4 hours, no rest for the wicked!
Click to expand...
Click to collapse
Just want to check the link is still up, as i'm getting a dead page on the file.
Edit: Ignore the above, i couldnt get online at all. Rebooted and now all ok. Used Flashify to backup original and then flash TWRP.
Thanks
Sent from my LG-D802 using Tapatalk 4
can i use this method to upgrade from twrp 2.6.3 to 2.6.3.2 ?
j_h3000 said:
can i use this method to upgrade from twrp 2.6.3 to 2.6.3.2 ?
Click to expand...
Click to collapse
Yes. I have done so.
TWRP Recovery for the LG F3Q (codenames: fx3q, d520)
Background story (who ever wants to know):
As I'm currently testing around with flashing etc I hated it to re-flash the stock ROM again and again. It is sooo time consuming..
In that kind of ROM compiling learning process I also was able to build a working TWRP recovery for the LG F3Q so that was such a good feeling But as said the caveat was that because of the locked bootloader we can reach TWRP (or CWM) only when executing "adb reboot recovery" from the running system. That was not really satisfying me though..
Some day I've done a factory reset and well I saw that this is starting my TWRP recovery when executing it! Well it isn't such a surprise as TWRP sits on the recovery partition and will be triggered by the factory reset script but... well do you think what I think? When it would be possible to start TWRP fully and not that factory reset part of TWRP than we would have a workaround to reach the recovery mode without booting the system (which is in fact not possible anymore when flashing of system.img/boot.img fails)
That said.. I was in touch with the TWRP developers bigbiff and Dees_Troy and many thanks for the hint they gave me! I have build a new TWRP version based on that information I got and well the idea of that is:
Vol Down + Power -> LG Factory Reset screen appears
Confirming with power 2 times as asked
Voila: No factory reset anymore but TWRP is here!
Well that will have a caveat - READ CAREFULLY:
As you may think of the factory reset in the boot-up process and within the ROM will not working anymore until you flash another recovery!
But if you know that it is not such a caveat because you can choose the wipe options within TWRP to do a "manual" factory reset.
v2.8.1.0 build 5
USE THAT ON YOUR OWN RISK! BACKUP BEFORE!
Working (quickly tested):
Install (to flash a custom Kernel)
Mounting partitions
Reboot Recovery | System
adb shell (also see known issues)
Backup (compressed | uncompressed | encrypted (!) | unencrypted)
Restore (unencrypted | encypted (!) | compressed | uncompressed)
Internal storage /data/media
MTP which mounts the external storage!
File Manager
Terminal Command
Power charging while in TWRP
Displaying CPU temp
Totally untested:
WIPE (should work)
decrypting /data (but should work as it do so for encrypted backups already)
Every option which is not stated as "Known issue" or "Working"
Known issues (with workarounds):
ADB works only when screen "timed out" (manual locking does not help it must time out) therefore ADB can take up to 1 minute after boot until it becomes available (because screen need to be timed out first)
Workaround: set the time limit in the screen menu to e.g. 10 sec (that is the default value for now)
Timezone is not set correctly (that seems to be a well known bug in several devices using TWRP.... )
Workaround: set a timezone which displays the most accurate timezone
Known issues (without workarounds):
When you use the "Power Off" option in the "Reboot" menu the device will reboot instead of powering off
Wiping /data not possible after "factory reset buttons" used. You need to choose "wipe" and then "format data" manually (or use mke2fs on CLI).
Vibration is not working (I will not fix that atm because I like it that way)
Hardware keys at bottom doesn't work
If you use the factory reset button /data partition will be inaccessible and need to be re-flashed (means you will LOOSE your app and system configs when you use factore reset)
Download:
Attached you will find the TWRP v2.8.1.0 version ready to use even with locked bootloader:
BACKUP EVERYTHING BEFORE USING THIS. USE AT YOUR OWN RISK!
DD Image file:twrp_v2.8.1.0_build5_fx3q_FR-OFF.img.zip = FactoryReset is disabled / TWRP will be loaded instead (also see known issues)
Read the Installation & Usage instructions in this thread on how to install that file.
Installation & Usage instructions
Pre-Requirements
Read the FAQ
YOU NEED ROOT! (check FAQ)
YOU SHOULD do a NANDroid BACKUP! (check FAQ)
You need to boot up, enable USB debugging and then connect USB cable.(check FAQ get ROOT - the link contains a guide on that)
You better doing a NANDroid backup right? (I mentioned that before - but DO it! NOW!)
For the best usage experience install the sediKERNEL or use joel's debloated stock ROM which includes it already
Bulletproof Method 1: "the average user"
Use this guide if you simply want to install & use TWRP like it should be. If you're unsure use this guide!
Install:
Download the TWRP recovery file and unzip it
copy it to your device (e.g. adb push or simply copy & paste by your file browser)
Download the loki_tool (https://github.com/djrbliss/loki/raw/master/bin/loki_tool)
copy loki_tool to your device (e.g. adb push or simply copy & paste by your file browser)
execute:
adb shell
su (you may need to grant permission)
mount -oremount,rw /system
cp /PATH-WHERE-YOU-COPIED/loki_tool /system/bin/ && chmod 755 /system/bin/loki_tool
loki_tool flash recovery /PATH-WHERE-YOU-COPIED/twrp_X.X.X.X_recovery_FRoff/off.img
reboot recovery --> you should see the TWRP screen
Usage (sediKERNEL v2.0 or higher installed):
Power on the device
when you see the LG logo the first time do NOTHING!!
When the screen goes black THEN press Volume UP + Volume DOWN. Both the same time and hold them pressed.
Release the buttons when the screen goes black again
Wait. You will see the LG logo a third time and then you will see the recovery screen!
If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.
Usage (without sediKERNEL v2.0 or higher):
boot into your ROM
execute "adb reboot recovery" from your PC or open a Terminal on your device and execute "su" then "reboot recovery"
Bulletproof Method 2: "developers only"
This is the developers preferred way of installing TWRP. It ensures that even when your ROM or Kernel gets damaged that you still be able to boot into recovery. This is to the developers or heavy testers who are knowing what they do ONLY!
But even when you think this is for you: Read the important hint at the end before deciding if you want to choose this method.
Install:
flash recovery image to your RECOVERY partition:
adb shell su -c dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
adb reboot recovery
A user reports the the by-name does not worked for him but this one:
adb shell su -c dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/mmcblk0p17
-> If you can see TWRP now everything is fine - Otherwise DO NOT continue!
BACKUP YOUR WHOLE DEVICE NOW! I highly recommend to backup everything except /data from within TWRP because it is easy and works (from TWRP v2.8build5 or higher)
BACKUP /data is recommended to be done NOW and this way:
adb shell su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/external_sd/userdata_backup_stock.img
--> This can take a long while but it contains also the backup for the internal storage not only /data and that internal part is not backupable over TWRP
while in TWRP flash the same recovery image to your BOOT partition now (do not think that this is dangerous. The boot partition is not a magic thing or so it is only the partition which will be started from the bootloader thats all about it. So yes you can install a recovery image on the boot partition without any harm.):
adb shell su -c dd if=/external_sd/twrp_vXXXXX_fx3q_FR-OFF.img.loki of=/dev/block/platform/msm_sdcc.1/by-name/boot
watch carefully that the process ended without errors and that the size is exactly the same as it should be (about 1,3GB)
adb shell sync
power off the device by taken out the battery (do not use reboot or something we want to be sure that the next step is absolutely really the normal boot up)
Boot up normally --> you should see TWRP !! You're NOT in recovery mode you're booting the normal boot mode!
Go on with flashing the sediKERNEL into your RECOVERY partition:
Download the sediKERNEL from here (the stock one could work, too but never tested ...)
push it to your device with adb or MTP (since v2.8build5)
Flash the sediKERNEL to your RECOVERY partition:
adb shell su -c dd if=/external_sd/sediKERNEL_JB-vXXXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Reboot into Recovery by using TWRP GUI or by executing "adb reboot recovery"
Your ROM will boot.
Usage:
From now on every time your device booting up you will see the TWRP screen and need to choose Reboot-->Recovery to boot your ROM.
This is the absolute best way to use TWRP if you want to be sure that you will reach the recovery even when your ROM gets damaged and is confirmed to work very well (as always guarantees are not available )
Important hint:
Be sure that you keep in mind that from now on your recovery and boot partition are not the same anymore (you can always revert back to the normal behaviour, of course!). So if you want to flash a kernel image you need to ensure that it goes to the RECOVERY partition instead of the normal BOOT partition (because on boot partition is TWRP now).
If I got my ROM working I will definitively add an option to the installer where this will be ensured and I asked @joel.maxuel for his stock ROM to add that, too. As for now we are the only ones who are developing for the F3Q so you should be save enough atm but you will need to keep that always in mind when you want to replace the kernel and/or ROM.
What would happen if you forget about that? Well nothing really bad because when you install a kernel or ROM the boot image partition simply gets overwritten and that means only that your TWRP is not there anymore but the system will boot (if the new kernel/ROM is not buggy or damaged). You then could install TWRP by method 1 or using method 2 by using the boot image/Kernel you want to install.
Damage your device - booting (NOT RECOMMENDED will loose /data ):
You probably NEVER want to use this method. It is here for reference only.
I highly recommend to choose one of the above bulletproof versions instead of this one because it WILL damage /data and you need to restore that whole partition afterwards.
All my tests has shown that this comes not from TWRP (in one of my tests I disabled everything in the sourcecode of TWRP which wipes /data) but coming from LG itself. The factory reset button/option do something with the /data partition sturucture and afterwards you cannot use that anymore. I also tried to restore the partition info by trying all backup superblocks but that doesn't worked. No backup superblock is accessible.
Restoring them by mke2fs and e2fsck does not work unfortunately.. (mke2fs -S /dev/block/platform/msm_sdcc.1/by-name/userdata && e2fsck -yf /dev/block/platform/msm_sdcc.1/by-name/userdata)
So if you have loosed your /data and/or internal storage you need to have a DD imaged backup near.
Install:
same as for "Bulletproof Method 1" above
Usage:
When you choosen FR-OFF then TWRP will be able to start without booting up the whole system (also see known issues):
Power Off the device (remove battery)
Vol Down + Power --> Then put the battery back --> LG Factory Reset screen appears
Confirming with power button 2 times as asked - if you downloaded and flashed the FRoff version of TWRP it will NOT open the normal reset procedure but /data and the internal storage are not accessible afterwards (read above about the details). That means your app configs and systems configs get lost that way. You have been warned!
Voila: No (full) factory reset anymore but TWRP is here when you have damaged your ROM or for some dev approach
If you want the factory reset back simply choose the file twrp_2.7.1.0_recovery_FRon.img.lok and follow the above instructions. Afterwards you will have TWRP but it will be reachable only when you execute "adb reboot recovery" from the running system.
XDA:DevDB Information
sediTWRP for LG Optimus F3Q, Tool/Utility for the General Discussion
Contributors
xdajog
Source Code: https://github.com/xdajog/bootable_recovery_twrp_fx3q
Version Information
Status: Stable
Current Stable Version: v2.8.1.0 build 5
Stable Release Date: 2014-11-18
Created 2015-05-19
Last Updated 2015-07-20
FAQ
Frequently Asked Questions (FAQ)
What is that "adb" thing?
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
Normally adb itself is not available as a standalone application - it comes with the Android SDK which is very big and heavy if you want to use adb and/or fastboot (another great tool) only.
But we live in a great world with many people wanting to make things easy so here you go when you want/need only adb and fastboot:
download & install adb at lifehacker
(Direct link for Windows users: Go to easy ADB install thread)
How to get root for the F3Q?
Here is the tool and guide: Saferoot
[*]What is a "nandroid" backup?
nandroid means essentially: "a full image of all your partitions" so it is a full snapshot of your ROM including all your apps and contents.
The name NANDroid is a portmanteau of "NAND" (as in Flash memory - NAND flash) and "Android." (Source)
[*]How to create a "nandroid" backup?
(See above for the meaning of "nandroid backup")
You have several options on how to do that.
The normal and absolutely recommended way is to do that "offline" (from within recovery mode) but you can also do it "online" (while Android is running).
.
Offline nandroid backup by using TWRP recovery: Guide
If you have no custom recovery installed read on.
.
Online nandroid backup:
by using an app:
There is 1 (known to me) "online" nandroid backup tool available which will backup from within your running Android: PlayStore.
I tested it and still using it since a while and I really like it but I would not fully resist on it.
I had no problems backing up but sometimes an app is lost when restoring. This may have been fixed but well it is like imaging a running Windows or Linux system:
Do not do it online if you can - it may/will work but there could be problems/inconsistencies later!!
If you never made a nandroid before doing it online will not harm anything and should be your first start. So install the Online Nandroid backup tool and begin.
Check out this guide for some hints: Guide
(If you like the Android app do not hesitate to buy the unlock key to support the developer!)
by using commandline tools:
First of all you need "adb" installed (check out the FAQ answer number 1 above).
Then you need someone who is telling you the device partition table and you need a big sized SD card to hold the images.
The reason is that you will use a special command named "dd" which images the whole partition (not the content only!).
dd is a VERY dangerous tool because if you use it wrong your device may get bricked so it is essential that you are using the
correct command and check that twice!
Check out the next FAQ on how to do this for the F3Q.
[*]How to create a "nandroid" backup for the F3Q - WITHOUT having a custom recovery?
The whole process will take a big amount of time but it is worth to follow each step including the md5sum checks at the end.
Please read the previous FAQ first because there you will find more information about background and other options you may have.
Ensure you have a SD card inserted which is big enough and having enough free space available (4GB at least! I recommend at least 8 GB but this depends on the size of your current data partition. A completely stock ROM with nothing installed and unused will need 3 GB space).
.
Install "adb" on your pc (check out the FAQ #1 above).
root your device (check out FAQ #2 above)
connect with adb to your (running) F3Q:
adb shell
(you should see a prompt)
su
(you need to grant permission if you haven't yet)
Then backup your current ROM and data:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/storage/external_SD/system.2015-07-20.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/boot.2015-07-20.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/storage/external_SD/userdata.2015-07-20.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/storage/external_SD/recovery.2015-07-20.img
# If you never backed up your EFS you really should do that once:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/external_SD/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/external_SD/modemst2.img
Click to expand...
Click to collapse
Just to be sure you can do an online backup now, too ( Guide ) Online Nandroid backup App
.
copy the backup(s) to your device (connect USB cable - open your external storage and drag&drop) <--- DO NOT SKIP THIS STEP!!!! It is absolutely essential!
Check your copy on your device:
md5sum /storage/external_SD/system.2015-07-20.img
md5sum /storage/external_SD/boot.2015-07-20.img
md5sum /storage/external_SD/userdata.2015-07-20.img
md5sum /storage/external_SD/recovery.2015-07-20.img
md5sum /storage/external_SD/modemst1.img
md5sum /storage/external_SD/modemst2.img
Click to expand...
Click to collapse
Download a md5sum checker like this one Windows MD5 and load each file you copied to it (on Linux the "md5sum" command can be used of course).
compare the md5sums from the above output and ensure that they are all matching.
[*]Why is factory reset not working when installing TWRP? (or: AAAAaaaah my /data is inaccessible after doing a factory reset!!!!)
All my tests has shown that this comes not from TWRP (in one of my tests I disabled everything in the sourcecode of TWRP which wipes /data) but coming from LG itself. The factory reset button/option do something with the /data partition sturucture and afterwards you cannot use that anymore. I also tried to restore the partition info by trying all backup superblocks but that doesn't worked. No backup superblock is accessible.
Restoring them by mke2fs and e2fsck does not work unfortunately.. (mke2fs -S /dev/block/platform/msm_sdcc.1/by-name/userdata && e2fsck -yf /dev/block/platform/msm_sdcc.1/by-name/userdata)
So if you have loosed your /data and/or internal storage you need to have a DD imaged backup near. Sorry but you have been warned (known issues) before.
.
if you want the factory reset back simply choose the file twrp_2.7.1.0_recovery_FRon.img.lok and follow the above instructions. Afterwards you will have TWRP but it will be reachable only when you execute "adb reboot recovery" from the running system. v2.7. is not recommended to use but atm the only option if you really want that. Instead I would better try the wipe options from within TWRP and re-installing your ROM of choice or simply using the official LG flashing tool to get your F3Q fully reset.
.
History / Changelog
Previous development (v2.7.1.0)
I HIGHLY RECOMMEND USING v2.8 instead of this version!
You have been warned.. If you still want that buggy version go on here:
USE THAT ON YOUR OWN RISK! I STRONGLY RECOMMEND TO BACKUP EVERYTHING BEFORE PROCEEDING.
Working:
Install (to flash a custom Kernel)
Mounting partitions (see known issues for the internal one)
Reboot Recovery | System
adb shell
File Manager
Terminal Command
Totally untested:
WIPE (may work)
Known issues:
If the device becomes locked and then unlocked by the user adb will restart on the device (or crash and start again. haven't had looked into that yet)
When you use the "Power Off" option in the "Reboot" menu the device will reboot instead of powering off
RESTORE (will NOT work!)
BACKUP (will NOT work!)
You cannot mount the external sd via USB or MTP
Vibration is not working (I will not fix that atm because I like it that way)
Timezone is not set correctly (that seems to be a well known bug in several devices using TWRP....
Internal storage is missing (/data/media)
Hardware keys at bottom doesn't work
If you use the factory reset button /data partition will be inaccessible and need to be re-flashed (means you will LOOSE your app and system configs when you use factore reset)
Download:
Attached you will find the loki'ed TWRP version (v2.7.1.0):
AGAIN: THIS IS A PROOF-OF-CONCEPT only. It definitively WILL have bugs and problems! I want to proof that it will be possible to have TWRP on this device and also have a way to boot up into TWRP without booting the whole system.
twrp_2.7.1.0_recovery_FRoff.img.lok = FactoryReset is disabled / TWRP will be loaded instead
twrp_2.7.1.0_recovery_FRon.img.lok = FactoryReset is enabled / TWRP can be reached with "adb reboot recovery" only
Read the Installation & Usage instructions in the OP on how to install that file.
Awesome work! Saves having to risk modifying the bootloader (for now). :laugh: :highfive: Thanks!
xdajog said:
TWRP Recovery for the LG F3Q / D520
...
Click to expand...
Click to collapse
I'm unable to get logs from TWRP, it does crash reliably when messing about in settings and such.
Timezone fix is needed. (Devices time is set to the correct local time, but TWRPs timezones arent correct.)
Device does not show internal storage.
Wipe menu does not differentiate from internal storage and /data
there's no /mnt, /storage or /sdcard present while in TWRP.
Uhm, I'm sure there's some more I've missed, but that's all I've got for now.
eriklion said:
I'm unable to get logs from TWRP, it does crash reliably when messing about in settings and such.
Click to expand...
Click to collapse
Uhm what do you mean? adb shell and then open /tmp/recovery.log? Clicking on the small mini icon at middle bottom of the screen? Both working for me. Have you tested the above attached version or the one I gave you at dropbox? The above is a more current one!
Timezone fix is needed. (Devices time is set to the correct local time, but TWRPs timezones arent correct.)
Click to expand...
Click to collapse
hm I will look into that
Device does not show internal storage.
Click to expand...
Click to collapse
yeah forgot to mention that. Is that shown in CWM btw?
Wipe menu does not differentiate from internal storage and /data
Click to expand...
Click to collapse
Could you explain what does that means?
there's no /mnt, /storage or /sdcard present while in TWRP.
Click to expand...
Click to collapse
/mnt and /storage are not needed or am I wrong? /sdcard would point to the internal storage I think but I decided to use /external_sd instead which is accessible in the latest version.
Finally got around to test. Looks great, I love having TWRP over CWM!
Unfortunately the backup function is not working. TWRP errors out and reloads itself. I have a pastebin, sorry it's so long but I wanted to try a couple different backup options before I gave up and produced a log file:
http://pastebin.com/QUfNw6Rk
The portions of interest are:
Code:
Backing up Cache...
I:Creating backup...
I:Creating tar file '/external_sd/TWRP/BACKUPS/1db9cba/1970-01-24--22-43-59 JZO54K//cache.ext4.win'
I:addFile '/cache/recovery' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/cache/recovery/log' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
...
Code:
Backing up Data...
I:Creating backup...
I:Creating tar file '/external_sd/TWRP/BACKUPS/1db9cba/1970-01-24--22-43-59 JZO54K//data.ext4.win'
I:addFile '/data/dontpanic' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg0' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/next_count' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg1' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg2' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg3' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg4' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg5' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg6' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg7' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 2.7.1.0 on Sun Jan 25 03:44:01 1970
I:Single storage only.
I:No internal storage defined.
I:No storage defined, defaulting to /sdcard.
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Starting the UI...Pixel format: 480x800 @ 32bpp
Pixel format: RGBX_8888
Not using qualcomm overlay, 'msmfb43_80201'
framebuffer: fd 4 (480 x 800)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/boot'
I:Processing '/cache'
I:Processing '/data'
I:Processing '/misc'
I:Processing '/recovery'
I:Processing '/external_sd'
I:Processing '/system'
I:Creating Android Secure: /external_sd/.android_secure
I:Backup folder set to '/external_sd/TWRP/BACKUPS/1db9cba'
I:Settings storage is '/external_sd'
Updating partition details...
I:Unmounting main partitions...
E:Unable to unmount '/data'
I have a stock based ROM to test, and I want to make sure I can enter recovery through the bootloader should things go sour. If TWRP can backup and restore, that allows me to go back to my true stock after the test. Any ideas?
joel.maxuel said:
Finally got around to test. Looks great, I love having TWRP over CWM!
Unfortunately the backup function is not working. TWRP errors out and reloads itself. [.....] Any ideas?
Click to expand...
Click to collapse
Yes.
There are several things coming in place when it comes to backing up out of TWRP atm...
You hopefully have read the big fat red warning ? What I mean is the part regarding /data gets lost when you do a factory-reset
That said if you have entered TWRP by pressing the physical keys your /data partition will be wiped (really bad thing but that it is made for and I haven't had the time to look into that further)
The result is a cleaned /data which is not mountable until you format it with mke2fs.
(e.g.: "adb shell mke2fs -T ext4 /dev/block/mmcblk0p15")
If you do not do that what MAY happens is that TWRP failing because of missing /data (and if not then you should ensure that /data was really backed up)
But as your log told me it seems to be not the problem here 'cause the /data partition is detected by TWRP. so it could be 2)
Mounting points.
As stated the mount points are not fully working in TWRP atm. That means when it comes to /sdcard which is the internal device storage it will fail, too because it cannot be found. The reason for this is that LG mounts /sdcard by the sdcard service but that is somehow tricky thats why it is not working atm.
And on top: the internal storage normally needs to be mounted to "/data/media" especially when we want to use MultiROM later.
So +1 for /sdcard or/and internal storage related
background info: http://teamw.in/DataMedia
The last one I could imagine is "something else" which could be catched by "/proc/last_kmsg"
The important thing is that this file gets written only after a crash and when the battery was not removed. So if the device reboots to TWRP again try to adb shell to the device and then paste the last_kmsg again. Maybe we can find something here.
When I will continue on TWRP I think of upgrading to v2.8 because they enable MTP here which could be good for copying data between device and pc..
BTW:
I have no idea what CWM port which is also be available would do in case of starting a backup especially what will REALLY gets backed up!!!!
IMHO the best way on doing a nandroid backup atm is "adb shell dd ...." Takes a long time but then you can be sure. I can give you all the mountpoints if you need them.
As I currently have not such much success with porting the ROM I will now come back here to TWRP and will finish it to have a hopefully fully working recovery. I cannot say the timeline for this but it will definitively be the next what I want to do because when this is done I can better match the rest for the ROM.
xdajog said:
<SNIP>
IMHO the best way on doing a nandroid backup atm is "adb shell dd ...." Takes a long time but then you can be sure. I can give you all the mountpoints if you need them.
As I currently have not such much success with porting the ROM I will now come back here to TWRP and will finish it to have a hopefully fully working recovery. I cannot say the timeline for this but it will definitively be the next what I want to do because when this is done I can better match the rest for the ROM.
Click to expand...
Click to collapse
This should work (I've done it before for eriklion):
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/storage/external_SD/system.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/boot.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/storage/external_SD/cache.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/storage/external_SD/userdata.2014-11-12.img
Now, is there a recommended adb command to wipe data and cache, since factory reset function is not the best choice? I see a few with the following process...
Code:
adb shell
su
format DATA
format CACHE
...but not much commentary on it.
I appreciate the second (third, whatever you are on) crack at TWRP. Hopefully the next version will squash the bugs. Btw, I will see if I can provide a /proc/last_kmsg tonight have posted a last_kmsg here.
joel.maxuel said:
This should work (I've done it before for eriklion):
Code:
adb shell
dd /dev/block/platform/msm_sdcc.1/by-name/system /storage/external_SD/system.2014-11-12.img
dd /dev/block/platform/msm_sdcc.1/by-name/boot /storage/external_SD/boot.2014-11-12.img
dd /dev/block/platform/msm_sdcc.1/by-name/cache /storage/external_SD/cache.2014-11-12.img
dd /dev/block/platform/msm_sdcc.1/by-name/userdata /storage/external_SD/userdata.2014-11-12.img
Click to expand...
Click to collapse
yes thats all you need to backup & restore
joel.maxuel said:
Now, is there a recommended adb command to wipe data and cache, since factory reset function is not the best choice? I see a few with the following process...
Code:
adb shell
su
format DATA
format CACHE
...but not much commentary on it.
I appreciate the second (third, whatever you are on) crack at TWRP. Hopefully the next version will squash the bugs. Btw, I will see if I can provide a /proc/last_kmsg tonight.
Click to expand...
Click to collapse
I always do it that way:
Code:
Starting TWRP
adb shell
("su" in TWRP not needed normally)
mke2fs -T ext4 /dev/block/mmcblk0p15 (for userdata)
mke2fs -T ext4 /dev/block/mmcblk0p14 (for cache)
Then you can be sure it is clean and well formatted. ext4 is for both cache and userdata and works fine for me.
twrp v2.8 with many enhancements and fixes is on its way
Stay tuned ....
if you get bored in the meanwhile ... click thanks
Is someone here with running the stock ROM (or absolutely not modified means formatted! /data partition) who is willing to give me a quick help? It must be stock or placed back to stock by using a backuped image dump if you have one.
The following need to be done in recovery so you need to have CWM or TWRP installed. Boot into recovery (adb reboot recovery) and then use "adb shell" to connect.
I need your output of this command:
Code:
mke2fs -n /dev/block/platform/msm_sdcc.1/by-name/userdata
This will not do/destroy/modify anything.
It should display some information about that partition. Read the details here http://linux.die.net/man/8/mke2fs
The reason is that LG factory reset seems to wipe superblocks (wanted by LG or not - fact is that they are thrown) and THEN forwarding to the recovery tool like TWRP but to be sure I need the above output from 1 or 2 people to be sure enough on how to proceed.
Thanks in advance
As Joel investigated that may destroy /data cause of a buggy version of mke2fs!! Oh man..
-----
Sent from my SGH-I927 using XDA Android mobile app
Ok thx to joel I'm able to investigate the LG facotry reset further.
In parallel I will try another way which will be (if I get it working) absolutely smooth and will not have such workaround character like the current idea (hijacking factory reset).
Give me some time but if that works it would be a great solution for accessing recovery..
Stay tuned some good things may happen...
-----
Sent from my SGH-I927 using XDA Android mobile app
Finally v2.8 for F3Q has arrived !!! I think a very good approach now!
Have fun and as usual any thx click.... and so on
Check out the OP for Download and details:
http://forum.xda-developers.com/showpost.php?p=55239027&postcount=1
UPDATE:
I have completely reworked the "Installation & Usage instructions" section in the OP. PLEASE READ and be happy
xdajog said:
Finally v2.8 for F3Q has arrived !!! I think a very good approach now!
Have fun and as usual any thx click.... and so on
Check out the OP for Download and details:
http://forum.xda-developers.com/showpost.php?p=55239027&postcount=1
UPDATE:
I have completely reworked the "Installation & Usage instructions" section in the OP. PLEASE READ and be happy
Click to expand...
Click to collapse
Great work.
Am looking at method two. If I was to install a ROM, wouldn't the boot partition (thus my new recovery) be overwritten by the ROM package's boot.img? And when I was cooking with the Kitchen, the ROM required a specific mount point for the boot partition. If it is supposed to point to recovery, seems to me that neither would boot (overwritten recovery, ROM pointing in the wrong location).
So, what is this solution getting around? So we have an option to load TWRP before a system we don't necessarily trust will boot? Thus avoiding the bootloader fallback even more? Or is it a broken boot.img breaks TWRP as well so even if we try to go in through the bootloader, TWRP fails to load as well?
Sorry for my confusion, still trying to grasp all this new information.
joel.maxuel said:
Great work.
Click to expand...
Click to collapse
Thanks
Am looking at method two. If I was to install a ROM, wouldn't the boot partition (thus my new recovery) be overwritten by the ROM package's boot.img?
Click to expand...
Click to collapse
Method 2 will suggest that if you install a custom ROM that you are be able to use/choose the boot.img partition (I hoped that the "hint" at the was clear enough but better to ask of course!)
And when I was cooking with the Kitchen, the ROM required a specific mount point for the boot partition. If it is supposed to point to recovery, seems to me that neither would boot (overwritten recovery, ROM pointing in the wrong location).
Click to expand...
Click to collapse
Well yes you either need to point to the recovery partition or (and that would be what I recommend) you let the user choose what he wanted to do.
So, what is this solution getting around?
Click to expand...
Click to collapse
The best we can do here (and that is what I will do for my custom ROM if I get it done some day) to use AROMA installer and ask the user if he has a recovery installed in the boot partition or not. Then you can choose what to do in the updater script.
I uploaded an example of my AROMA installation setup for the "sediROM for Samsung Captivate Glide" in this post. This one is VERY complex but you will get the idea and many input on how to do things.
So we have an option to load TWRP before a system we don't necessarily trust will boot? Thus avoiding the bootloader fallback even more?
Click to expand...
Click to collapse
Yes using method 2 we have always coming TWRP up when powering on the device. We then can choose to do things in there or to boot to "recovery" which will be the ROM. What do you meant with "bootloader fallback"?
Or is it a broken boot.img breaks TWRP as well so even if we try to go in through the bootloader, TWRP fails to load as well?
Click to expand...
Click to collapse
Not sure If I got you. When the boot partition gets overwritten TWRP and any possibility to get into TWRP will be lost because it sits only in the boot partition when using method 2. If you choose to do a factory reset when powering on the device or from within the ROM I have no idea what happens then unfortunately. That is untested but if you willing to test..
Sorry for my confusion, still trying to grasp all this new information.
Click to expand...
Click to collapse
No worry about that happy if that is useful for someone
xdajog said:
I uploaded an example of my AROMA installation setup for the "sediROM for Samsung Captivate Glide" in this post. This one is VERY complex but you will get the idea and many input on how to do things.
Click to expand...
Click to collapse
Thanks! I will take a look at this in the next few days.
xdajog said:
Yes using method 2 we have always coming TWRP up when powering on the device. We then can choose to do things in there or to boot to "recovery" which will be the ROM. What do you meant with "bootloader fallback"?
Click to expand...
Click to collapse
Bootloader fallback as in having to access TWRP via the bootloader. Our regular method is to access form the ROM, but if the ROM is bricked for whatever reason, the fallback is through the bootloader.
xdajog said:
Not sure If I got you. When the boot partition gets overwritten TWRP and any possibility to get into TWRP will be lost because it sits only in the boot partition when using method 2. If you choose to do a factory reset when powering on the device or from within the ROM I have no idea what happens then unfortunately. That is untested but if you willing to test..
Click to expand...
Click to collapse
I was alluding to the scenario if one was to choose method one, installed a ROM, and things got busted badly... Would you even be able to access TWRP with a bad boot partition? I think so, because recovery partition should be self sufficient (I think you proved it by swapping their places by way of method two), it is just getting into recovery by way of bootloader) I don't particularly like.
Had to face that fear last night, and ultimately, TWRP started up fast enough from the bootloader that it seemed like nothing happened, but when i went to dump the log, it could not recognize the sdcard. DD'ing my userdata partition back fixed that issue.
joel.maxuel said:
Bootloader fallback as in having to access TWRP via the bootloader. Our regular method is to access form the ROM, but if the ROM is bricked for whatever reason, the fallback is through the bootloader.
Click to expand...
Click to collapse
You mean "factory-reset" right? By either pressing the factory reset buttons (or by choosing from within the ROM) correct?
I was alluding to the scenario if one was to choose method one, installed a ROM, and things got busted badly... Would you even be able to access TWRP with a bad boot partition? I think so, because recovery partition should be self sufficient (I think you proved it by swapping their places by way of method two), it is just getting into recovery by way of bootloader) I don't particularly like.
Click to expand...
Click to collapse
If you install TWRP with method 1 and your boot partition gets corrupt you still be able to reach TWRP by using the factory-reset buttons. But you will loose /data then.
If you install TWRP with method 2 and your boot partition has gone you can not start TWRP anymore because it sits on there.
So you're more bulletproof by choosing method 1 because you would reach TWRP even when the boot partition gets damaged but you will loose /data then! Mentioned in the known issues in the OP.
Had to face that fear last night, and ultimately, TWRP started up fast enough from the bootloader that it seemed like nothing happened, but when i went to dump the log, it could not recognize the sdcard. DD'ing my userdata partition back fixed that issue.
Click to expand...
Click to collapse
When you have TWRP installed with method 1 you will reach TWRP by factory reset buttons and it will DO NOTHING ! Really! It simply starts TWRP because I patched TWRP that way that it will not wipe anything when triggered by the factory-reset command / button!
I can say that for double sure since today because:
1) In one of my tests I had disabled REALLY EVERY wipe option within TWRP - compiled it - installed it and even then /data gets lost!
2) I have installed the BOOT image means KERNEL on the RECOVERY partition today again and then used the factory-reset buttons again (after I restored /data of course)... and /data gets lost AGAIN--?!!
That means even when there is absolutely no custom recovery in place (like TWRP) which would normally handle wiping /data then nevertheless /data gets corrupted! I have tested that twice so I can say now for sure that this has nothing to do with TWRP but it comes from the LG bootloader instead! That bootloader is CRAP. sorry.
I had tested one approach which is build in boot image RAM disk which catches the keys which are pressed and then reboot into recovery. That would work but only as long as you have a working boot image partition. So that is the same good/bad as having TWRP sitting within the boot partition which is much easier to do so I decided to go this way for now.
One last word about the crappy factory-reset by LG: I have tried a lot to find out what really happens to the partition or partition table of /data when those keys are pressed but the only thing I can say is that the superblocks are inaccessible and the same for the backup superblocks. doing a "mke2fs -S" does not work (and wouldn't fix the root cause of the issue) and I have no idea what LG do here. Therefore cannot fix that ..
so I believe we will need to live with one of the 3 methods described in the OP....
Hope that answered some of your questions...
Bad news..
The Desire Z of my wife is completely broken now.
That means I cannot develop anymore..
- I ported and released the latest TWRP version to the F3Q
- I'm able to build AOSP JellyBean (not booting yet though),
- I compiled and released a custom AOSP Kernel (named sediKERNEL)
.... and a lot more..
I have everything I need to continue here in place...
I have the will and the ability to continue...
But no device anymore..
If someone has a F3Q to give away.. then I will continue but I'm not willing to buy a F3Q for developing only. So if you have an idea how we could continue let me know.
Update:
Check out the following link if you want to help http://forum.xda-developers.com/showthread.php?t=2952919
Otherwise that will end here for me unfortunately...
Hopefully not.
Yours
Xdajog.
-----
Sent from my SGH-I927 using XDA Android mobile app
I will update the installation instructions soon!
Because of the new sediKERNEL v2.0 the instructions will be made bullet proof only .. and i try to do it more detailed @Kediil
-----
Sent from my SGH-I927 using XDA Android mobile app