Hi everyone. I used builder.clockworkmod.com together with ausdim's recovery image to build the newest version (currently 6.0.1.5) as a touch version. I used graphics.c from the CM I9300 git repo, and it seems to do the job. The home button seems to have no effect, but the menu and back touch buttons work. So do the volume keys.
I've used a modified recovery.fstab in order to include the internal sdcard as well as the external one. Haven't tested the .tar.md5 files in ODIN, since I used:
Code:
dd if=inputfile.img of=/dev/block/mmcblk0p9
... while in recovery through adb.
I'll include both .tar.md5 files and img files for your convenience.
Proceed with caution, I am not responsible if something goes wrong. The touch one (flashing the img file) worked on mine. Make a backup on your SD card before trying and be careful to use mmcblk0p9 (recovery partition on the I9305). My first attempt overwrote the system partition, luckily I had a backup.
ODIN file
CWM touch: recovery-clockworkmod-touch-i9305.tar.md5
IMG file (for use with dd)
CWM touch: recovery-clockworkmod-touch-i9305.img
Edit: Backup function is reported not to work properly. Use at your own risk.
MD5's are invalid for ODIN
Bummer. I'm actually not sure how to package them. I'll try again tomorrow. Meanwhile, the img files work with dd when using adb shell in recovery mode.
Sent from my GT-I9305 using Tapatalk 2
zyonee said:
Bummer. I'm actually not sure how to package them. I'll try again tomorrow. Meanwhile, the img files work with dd when using adb shell in recovery mode.
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
not a clue how to do that mate.... otherwise i would have, guide?
Did it on a hackintosh. Maybe the tar or md5 output isn't compatible. Will try it in an Ubuntu VM tomorrow. I did use a guide, actually.
Sent from my GT-I9305 using Tapatalk 2
zyonee said:
Did it on a hackintosh. Maybe the tar or md5 output isn't compatible. Will try it in an Ubuntu VM tomorrow. I did use a guide, actually.
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
what do you mean by invalid? Odin allows for MD5.. do you mean it doesn't flash properly?
btemtd said:
what do you mean by invalid? Odin allows for MD5.. do you mean it doesn't flash properly?
Click to expand...
Click to collapse
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> recovery-clockworkmod-touch-i9305.tar.md5 is invalid.
<OSM> End...
Not working for me ?
Getting the same error as above using ODIN so tried the dd if/of method too and it copies successfully (i.e. no errors) but when rebooting back into CWM I'm still back on 5.5.0.4 non-touch ?
Will wait for a working .tar/md5 and try the ODIN way I guess ?
Code:
dd if=inputfile.img of=/dev/block/nncblk0p9
... while in recovery through adb.
Do you have to be in recovery mode? cant you just do it from a terminal whilst your in the phone, and then reboot into recovery to check
btemtd said:
Code:
dd if=inputfile.img of=/dev/block/nncblk0p9
... while in recovery through adb.
Do you have to be in recovery mode? cant you just do it from a terminal whilst your in the phone, and then reboot into recovery to check
Click to expand...
Click to collapse
Method I used:
1. Copy the recovery.img file to the phone.
2. Boot phone into recovery (current CWM 5.5.0.4 non-touch)
3. Plug phone into the pc and wait for it to be picked up.
3. On the phone, go to Mounts & Storage, mount SDCard.
4. on pc "adb shell"
5. Will have connected with SU rights (as can be seen with #), then type (on pc):
dd if=/sdcard/recovery-clockworkmod-touch-i9305.img of=/dev/block/nncblk0p9
6. Should copy over in just a second or two and give you file size counts etc.
7. On pc type "reboot recovery"
I then end up back in the 5.5.0.4 non-touch recovery ? probably me doing it wrong but I can remember back in the day doing the same on my trusty G1 and it working
NOTE: To OP, is the mount point correct ? i.e. should it be "mmcblk0p9" not "nncblk0p9", which is what is in the OP ???
CharlesW123 said:
Method I used:
1. Copy the recovery.img file to the phone.
2. Boot phone into recovery (current CWM 5.5.0.4 non-touch)
3. Plug phone into the pc and wait for it to be picked up.
3. On the phone, go to Mounts & Storage, mount SDCard.
4. on pc "adb shell"
5. Will have connected with SU rights (as can be seen with #), then type (on pc):
dd if=/sdcard/recovery-clockworkmod-touch-i9305.img of=/dev/block/nncblk0p9
6. Should copy over in just a second or two and give you file size counts etc.
7. On pc type "reboot recovery"
I then end up back in the 5.5.0.4 non-touch recovery ? probably me doing it wrong but I can remember back in the day doing the same on my trusty G1 and it working
NOTE: To OP, is the mount point correct ? i.e. should it be "mmcblk0p9" not "nncblk0p9", which is what is in the OP ???
Click to expand...
Click to collapse
your 100% right
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
OP must of made a mistake can you test and report back i will try it your way
---------- Post added at 02:18 AM ---------- Previous post was at 01:58 AM ----------
where can i get adb shell
Success
btemtd said:
your 100% right
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
OP must of made a mistake can you test and report back i will try it your way
---------- Post added at 02:18 AM ---------- Previous post was at 01:58 AM ----------
where can i get adb shell
Click to expand...
Click to collapse
I usually am lol
Can confirm it works Now have CWM touch v6.0.1.5.
Nice one OP, tut tut for typo though lol
So just to re-confirm the dd if/of line should be :
dd if=/sdcard/recovery-clockworkmod-touch-i9305.img of=/dev/block/mmcblk0p9
Fixed the typo, thanks for noticing.
Sent from my GT-I9305 using Tapatalk 2
CharlesW123 said:
I usually am lol
Can confirm it works Now have CWM touch v6.0.1.5.
Nice one OP, tut tut for typo though lol
So just to re-confirm the dd if/of line should be :
dd if=/sdcard/recovery-clockworkmod-touch-i9305.img of=/dev/block/mmcblk0p9
Click to expand...
Click to collapse
dont run away yet lool where do i get adb shell i cannot find the ***** and i heard the the new CWM has an option to create a nand the old fashion way without the blobs folder please confirm
btemtd said:
dont run away yet lool where do i get adb shell i cannot find the ***** and i heard the the new CWM has an option to create a nand the old fashion way without the blobs folder please confirm
Click to expand...
Click to collapse
Just need adb setting up, here's a quick n easy tutorial:
http://forum.xda-developers.com/showthread.php?t=1272595
GOT IT
Ok for who ever wants to make this happen MAKE SURE IF YOU HAVE AN EXT SD CARD COPY IT TO THERE NOT THE INTERNAL BECAUSE WHEN YOU MOUNT SD CARD ITS ACTUALLY MOUNTiNG The EXternAL ONE
---------- Post added at 03:57 AM ---------- Previous post was at 03:26 AM ----------
I Like this recovery and was finally exited it has an option to create the TAR backup But i did it as a test and was dissappointed to see it doesnt actually back up your data & apps and most likely not your tweaks aswell. DAM it the chainfire still is the best in that regards as its better for the people who flash test roms and if they dont like it just press restore and reboot and you have EVERYTHING the way it was without having to reset it.
I am going to talk to the creater and ask him why he still hasnt added the full nandroid option back like it used to be
It uses incremental backups if I'm not mistaken. Are you saying backup is broken or simply not backing up entire partitions each time? I haven't had time to try it myself.
Sent from my GT-I9305 using Tapatalk 2
zyonee said:
It uses incremental backups if I'm not mistaken. Are you saying backup is broken or simply not backing up entire partitions each time? I haven't had time to try it myself.
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
No it works fine so far its actually the best one since chainfire's because if give you an option of increment way OR Tar way which is entire backup MINUS your data, Appz, Tweaks, Its like a blank fresh base with what ever system apps you had and your modem, before there was no tar option and you know how long it used to take to transfer your nandroid backup to your computer? Not because of the size because of the thousands upon thousand of small blob files. Was a major headache i never used to copy it i left it on the phone.
But I reverted back to chainfires once again and ill tell you why:
The way the other CWM was is when you create a backup it creates an ENTIRE CLONE of the WHOLE phone data,sms,tweaks,even folders you created and wifi settings . the way your widgets and screens were setup. EVERYTHING. this makes it easier when you flash roms to test but you dont like it you just have to flash your one back with one button and you dont have to set anything else. Maybe the creater of CWM should see this i dont think he realises how much better the other backup way was,
btemtd said:
No it works fine so far its actually the best one since chainfire's because if give you an option of increment way OR Tar way which is entire backup MINUS your data, Appz, Tweaks, Its like a blank fresh base with what ever system apps you had and your modem, before there was no tar option and you know how long it used to take to transfer your nandroid backup to your computer? Not because of the size because of the thousands upon thousand of small blob files. Was a major headache i never used to copy it i left it on the phone.
But I reverted back to chainfires once again and ill tell you why:
The way the other CWM was is when you create a backup it creates an ENTIRE CLONE of the WHOLE phone data,sms,tweaks,even folders you created and wifi settings . the way your widgets and screens were setup. EVERYTHING. this makes it easier when you flash roms to test but you dont like it you just have to flash your one back with one button and you dont have to set anything else. Maybe the creater of CWM should see this i dont think he realises how much better the other backup way was,
Click to expand...
Click to collapse
For the one who frequently makes backups, the incremental version is better and for those who want to transfer full backups, the older one is preferable. I think there's a way by putting some kind of configuration file in the cwm directory to choose the full backup, but I'm not sure about this...
Sent from my GT-I9305 using Tapatalk 2
success
Related
Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)
Now I am stuck @ finding a proper file host to upload the files.
waiting for this!
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.
Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2
UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.
Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.
So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Nice work! Thanks!
Sent from my GT-I9103
nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.
This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts
So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app
My goal: Root my old skyrocket so that I can run apps from Google Play that require root. I do not want to flash a custom ROM.
These are the instructions I am following, I am currently trying to figure out step 5:
1. Start ODIN
2. Put phone into download mode
3. Download(USE FIREFOX!) CWM 5.5.0.4 OR TWRP 2.2.2.0 TAR FILE "recovery.tar.md5" , do not change the filename, and select it in PDA section of ODIN
4. Hit the START button in odin, wait until it finishes.
5. Udate CWM from HERE or TWRP from HERE or with the TWRP 2.4.1.0 Flashable Zip
6. You're done.
Click to expand...
Click to collapse
Since I have CWM installed, I clicked the 'HERE' link on step 5, which sends me here http://forum.xda-developers.com/showthread.php?t=1777970
This is what that link tells me to do:
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
-I have no ****ing clue what this is telling me to do.
-I have put updater.sh on my sdcard
-What the **** is adb. I don't even know if that's a phone or PC application, or some file manager, or what.
-What does completing step 5 accomplish? Will this have rooted me pursuant to my goal at the top of this post? I have literally no clue what these insturctions are trying to do nor when they have given me what I want.
Thanks.
Leave. Skyrocket is i727. Also don't cuss. People are more likely to help someone who doesn't seem *****y. And Google searches would have helped you. Adb. Is that hard to put in Google?
Sent from my GS4 running CM11 Kandy Kane
Moved to SkyRocket Q&A section
Make sure your phone is a i727 skyrocket
Download
http://d-h.st/KMT
And flash in recovery. This will update your recovery.
Reboot your phone
Download this http://d-h.st/fOD
Go back to recovery and flash the file you just downloaded. If it fails flash again.
Reboot your phone
Open the SuperSU app that will now be in your app drawer and update the binary when it prompts.
You are rooted.
You do not need to update your recovery but I highly recommend it
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 01:05 PM ---------- Previous post was at 12:57 PM ----------
Oh yeah and thank vincom
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I have a 8013. I need to put in a different recovery and I like twrp. has anyone flashed it from goomanager? I see that there is one on there I just dont want to mess something up.
Already rooted.
I would search for this but I cant find a search button. Really not in the app or on the website.
Sent from my GT-N8013 using xda app-developers app
Let me see...
eggwardo said:
I have a 8013. I need to put in a different recovery and I like twrp. has anyone flashed it from goomanager? I see that there is one on there I just dont want to mess something up.
Already rooted.
I would search for this but I cant find a search button. Really not in the app or on the website.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Hmm... When I read here: Goomanager so there is function for flash recovery. But if I don't get wrong, so this recovery files must be on www.goo.im server. Theoretically all ROMs, MODs and RECOVERY files lying on goo.im server
you can download to your device and flash it!
But for me and if I want to flash something, the best way is: Flashify
Here is it TOP 11:
1 - Flash boot and recovery .img without even needing to go to recovery.
2 - Flash zip files. Option to wipe cache, dalvik and data when using TWRP or Philz recovery.
3 - Download and flash CWM, Philz, TWRP, Gapps, Franco Kernel, Stock Nexus Kernel (premium), and Stock Nexus Recovery (premium).
4 - Automatic Loki Patch when needed.
5 - Full nandroid backups/restores when using TWRP or Philz recovery.
6 - Backup/Restore kernel and recovery using Sdcard or cloud (Dropbox, Box (premium) or Google Drive (premium)).
7 - Automatic cloud synchronisation of backups between devices and desktops.
8 - Keep track of recently flashed items.
9 - Flash multiple files and build your flash queue.
11 - Flash from anywhere! Do you want to flash from your favorite File Explorer or Email app? No biggie, that also works together with Flashify.
More at links above!
Have great Flashing :victory: Peter
I have an 8013 as well that I acquired used. it was pre-rooted, but the custom recovery on it didn't work for newer roms. I looked into installing TWRP and found that although the official TWRP instructions said you could install it from GooManager, when I tried to, it didn't find a recovery for the device.
I did successfully get TWRP installed quite easily using their alternate instructions, though. here's a quick breakdown, especially since their instructions are a bit vague.
1. download the .img file for the recovery from here: http ://teamw.in /project/ twrp2/110 (remove the spaces; I can't post outside links yet.)
2. in either terminal emultor or through adb shell, run the command shown below, replacing the bracketed sections with the path and filename of the .img file:
dd if=/<File path>/<filename>.img of=/dev/block/mmcblk0p6
For example, say you save it in your downloads folder on the internal sd card. The path is probably something along the lines of /storage/sdcard0/Download/openrecovery-twrp-2.7.0.0-gt-n8013.img
If you get the path or filename wrong when you runthis command, it will just tell you that it could not find the file you told it to write. if you get the second part wrong, however, you could brick your device, so make sure you double and triple check that part.
Another good check to do before running the command is to ensure that your download is not corrupt by checking the md5 checksum. To do this, make sure you copy that when you download the file and then check using a file browser that supports it. I use Explorer (by Speed Software) to check the md5. To see it, long press the file and click properties. If the one given when you downloaded it and and the one you get from the file do not match, your download likely got corrupted and you should try again until they do match. It's rare, but you don't want to flash a corrupted recovery, so do check it.
The command itself can either be run from an app like terminal emulator or over adb (android debug bridge) from your computer using the command:
adb shell <command>
I followed this basic procedure and now have a fully functioning TWRP recovery on my 8013. Best of luck to you in getting yours working. :good:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21
Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this
Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...
sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.
Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.
I built using official p500 armv6 repo
They should fix the device recovery size in that case!!
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.
So here you come. To read and perform this tutorial, you obviously need a first hand experience on flashing a ROM and/or kernels. Otherwise this tutorial and my efforts to get you a device with two OSes running might end up giving you a bricked device. So, if you're hearing the terms "flashing" or 'kernels' for the first time and thinking it's kinda good food, then bro, just go and taste those first.
Something's to remind before we gonna dig deep into this tutorial->
Noone but you will be responsible for what you end up with.
The warranty of your device will be voided after this if it isn't already after rooting. For MI users, the good news is that you can reclaim it by just flashing the fastboot ROM for your device.
Enough lectures. Bro let's get to work.
Things you'll be needing =>
One working Windows PC(because I doesn't know any replacement of bootimg.exe on any other OS. If you know, then let me).
ADB, fastboot and the device drivers (easily found in XDA)
Any custom CWM based recovery installed.(since TWRP is most popular, I will demonstrate using it. You can use any other you want overall process will be the same)
A custom ROM and kernel for your phone(the second os)
A class 10 memory card ( I recommend 32GB for the spaces)
PART 1: MODIFYING THE BOOT
At first, how does your device boots up? What are the partitions called /data and /system? The answer is quite simple. It's your kernel that points out the location from where the OS should be picked up. So for booting into the second OS we need some modifications to it at first.
Search and download bootimg.exe on XDA, I'll post a link later. Create two folders. Name them "Internal OS" and "External OS" respectively. Put the zip file of the OS you're currently using to the first one and the OS you're gonna use on the external storage to the second one. Rename the second OS to originalExternalOS.zip. Extract originalExternalOS.zip. Pick the boot.img file from the root of the extracted folder and move it to a new folder named "boot2". Extract the IMG using bootimg.exe. Navigate to the initrd folder and you will get a file named 'fstab".
Basically it's the file that tells the kernel which partition does the OS resides in.
Open the file in your favourite text editor.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
Save the file without giving any extension to it. Repack it using the same tool. You'll have boot-new.img and boot-old.img. Rename boot-new.img to boot.img and replace the one in the root folder with this. Basically what we're doing here is replacing the old boot.img with the modified one.
For your knowledge, blocks are the partitions of any storage you have on your device. For example, your internal storage is partitioned to near about 30 different blocks each starting with prefix "mmcblk0p". We here just told the kernel to load the OS from the blocks mentioned. We'll be creating these blocks in the external SD card next.
PART 2: PARTITIONING THE SD CARD
Connect your device with the memory card inserted to your PC. If you haven't installed fastboot, ADB, and the drivers, do it now.
READ THE FOLLOWING CAREFULLY
Reboot the device to recovery mode. Type the commands in cmd:
Code:
adb shell
parted
unit MB
print
quit
umount external_sd
Read and store the minimum and maximum capacity of your card. Since different cards will have different capacities I will point it as variable MIN_SIZE and MAX_SIZE. You'll need to calculate and put the values in the commands. Now type the following commands on cmd:
Code:
parted /dev/block/mmcblk1
rm 1
//START_BLOCK = MAX_SIZE - 5000
mkpartfs primary fat32 MIN_SIZE START_BLOCK
//SYS_START = START_BLOCK+1
//SYS_END = SYS_START + 1200
mkpartfs primary ext2 SYS_START SYS_END
//DATA_START = SYS_END+1
//DATA_END = DATA_START + 3500
mkpartfs primary ext2 DATA_START DATA_END
//CACHE_START = DATA_END + 1
mkpartfs primary ext2 CACHE_START MAX_SIZE
//We have partitioned the memory card. Let's format them. Ignore all "Do you wish to continue" question in the next commands as we're already mentioning yes.
mkfs yes 1 fat32
mkfs yes 2 ext2
mkfs yes 3 ext2
mkfs yes 4 ext2
quit
//Now they are almost ready. Just make the newly created blocks readable by the OS.
make_ext4fs /dev/block/mmcblk1p2
make_ext4fs /dev/block/mmcblk1p3
make_ext4fs /dev/block/mmcblk1p4
//Now you get where does the blocks come in the kernel right?
exit
//You've covered up the hardest part. Let's get some coffee.
PART 3: MODIFYING THE NEW OS
You've left the OS extracted in the "External OS" folder right? It's time to do some magic in it. We're gonna tell the OS to be installed in the blocks we created just like the kernel. But wait, where does the OS know before installing where it should get installed? Well, the answer hides in the updater-script in the folder META-INF > com > google > android. Navigate yourself in it. Open the updater-script file in your favourite editor ( I use notepad++ ) and modify it in the same way as the boot.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
Leave the /dev/block/bootdevice/by-name/boot as it's the fundamental block and we can't replicate it. Don't think for the /cache partition as we've already done that in the boot.img file. Now navigate to the root of the folder where you extracted the External OS. Select all files, add them to a zip file using WinRAR. Name the file to newOS.zip. Open newOs.zip and originalExternalOS.zip with WinRAR and compare them if you find any change in the folder tree. They must and they should be exactly the same. You're 80% done.
PART 4: MODIFYING THE RECOVERY
We often flash many zips including very popular Xposed and other mods to our OS right? They also look for the /system partition. So what are we gonna do? Modifying each of them? Nah. Let's modify where they get which one the /system is. The recovery. Extract the img of the recovery you're using with the same bootimg.exe. Modify exactly the same things. I.e.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
in the following files : initrd/fstab.qcom
initrd/etc/recovery.fstab
initrd/etc/twrp.fstab(For TWRP only)
Save them. Repack. And you got your recovery-new.img and recovery-old.img. Put recovery-new.img and newOS.zip in the same folder. Now wake up, it's time for some action.
PART 5 : INSTALLING THE OS
Open cmd in the folder where newOS.zip resides. Reboot the device in fastboot mode. Type the following commands:
Code:
adb push newOS.zip external_sd
fastboot flash recovery recovery-new.img
fastboot boot recovery
Now your device should boot up in recovery mode. To check if everything has gone fine mount system using TWRP. Use twrp's built in file manager and navigate to system folder. It's empty? Yup. You've done a great job. Now flash the newOS.zip using TWRP and your device should boot up in the new OS. To cross check again remove the SD card and try to boot. If you're headed towards recovery or bootloop after that then it's a win. Put the SD card back again and watch the new OS to boot.
PART 6: SWITCHING BETWEEN THE TWO
Extract the boot.img from the "Internal OS" zip file and put it together with recovery-old.img. To check if your old system is untouched type the following commands in fastboot mode:
Code:
fastboot flash recovery recovery-old.img
fastboot flash boot boot.img
fastboot boot system
Your device should take you back to the old one. Surprised? Now let's make a switch between the two. There are two methods.
METHOD 1: USING FLASHIFY
Create two folders in your SD card. Put boot.img and recovery-old.img to one and boot-new.img and recovery-new.img to the other. To switch to the external OS, just flash boot-new.img as boot and recovery-new.img using flashify. Ignore reboot now dialog and reboot directly to the system. To go back, first install flashify in the new OS and flash boot.img and recovery-old.img. Easy right?
METHOD 2: USING ZIPS
I'm gonna tell you that tomorrow as I can write no more today.
More to come....
CREDITS:
justzzshadz from MIUI forum for this revolutionary concept. @iamsubhranil for adding TWRP, Flashify support and completely rewriting the tutorial.
Thank u so much for ur efforts... It helps me a lot
I don't understand members on xda ...why they don't give thnaks on thread ..they only see the thread and go away...
Sry 4 my english ..
Thanks again
---------- Post added at 08:07 AM ---------- Previous post was at 07:48 AM ----------
Pls lemme know that if i can use dsixda's kitchen for modifying boot.img (kernal ) ???
Coz i didn't find bootimg.exe tool... If u have then pls give me the link.
Thanks
yes you can use android kitchen
When You Will Continue Writing The Thread Im Really Interested in trying it
Faisal Z Ahmad said:
When You Will Continue Writing The Thread Im Really Interested in trying it
Click to expand...
Click to collapse
I will after a while as I'm having final exams you can still try with flashify bro
sc123001.11 said:
Thank u so much for ur efforts... It helps me a lot
I don't understand members on xda ...why they don't give thnaks on thread ..they only see the thread and go away...
Sry 4 my english ..
Thanks again
---------- Post added at 08:07 AM ---------- Previous post was at 07:48 AM ----------
Pls lemme know that if i can use dsixda's kitchen for modifying boot.img (kernal ) ???
Coz i didn't find bootimg.exe tool... If u have then pls give me the link.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-1s/general/guide-unpack-repack-kernel-t2908458
Most comfortable
iamsubhranil said:
I will after a while as I'm having final exams you can still try with flashify bro
Click to expand...
Click to collapse
Yeah I Know I Can Try But i Need To Know Method 2 To Switch ROMS Because Second One Is Faster Using Zips Otherwise Great Post And Guide ,Thank You
Good Luck With Your Exams
Nice tutorial.
Dual boot for Mediatek devices is so easy to me. But I don't have any idea for Other devices like Samsung or Sony.
When I bought some SD Card, I'll try this one.
Keep it up!
Faisal Z Ahmad said:
Yeah I Know I Can Try But i Need To Know Method 2 To Switch ROMS Because Second One Is Faster Using Zips Otherwise Great Post And Guide ,Thank You
Good Luck With Your Exams
Click to expand...
Click to collapse
Thanx a lot
BTW flashify is also very convenient method
1)Just choose boot image from the option
2)Find and select the internal or external boot image to boot
3)Have a normal reboot
jbliz said:
Nice tutorial.
Dual boot for Mediatek devices is so easy to me. But I don't have any idea for Other devices like Samsung or Sony.
When I bought some SD Card, I'll try this one.
Keep it up!
Click to expand...
Click to collapse
This one is universal bro
iamsubhranil said:
This one is universal bro
Click to expand...
Click to collapse
I did not see you make any modification to boot.img.
Sry My bad. I didn't read at the top.
iamsubhranil said:
Thanx a lot
BTW flashify is also very convenient method
1)Just choose boot image from the option
2)Find and select the internal or external boot image to boot
3)Have a normal reboot
Click to expand...
Click to collapse
I am gonna try this anyway, maybe tomorrow
Because i want two ROMS mainly, one for CM cuz i love it, daily drivers and everday usage, second one mainly focused on battery life (when i don't use my device much)
Another Question ,How do I Flash Zips (from recovery) To A Specific ROM?
And I Have CM 12.1 And Im Using M5 Kernel so Where Do the Edit Goes?
Faisal Z Ahmad said:
Another Question ,How do I Flash Zips (from recovery) To A Specific ROM?
And I Have CM 12.1 And Im Using M5 Kernel so Where Do the Edit Goes?
Click to expand...
Click to collapse
The edit goes to the recovery. At the end of the process you'll have two different recovery files for two OSes. Flashing any zips via modified recovery will flash them straight to the new os. Switch between those recoveries as required. Read the TUT carefully.