Related
Hi , greeting everyone !
Before appearing ICS, I made a small update custom, including small changes in the original firmware 3.2.79.
This release is permanently ROOT, busybox is installed proper and is unique , Su and Superuser is up to date ! At the bottom you have Update of this version (activated vibrator and fixed adb command).
Included : 24/01/12
- new boot animation;
- battery percentage, and other new Icon;
- several applications in addition ( office free, flashplayer 11,adobe air.....+++);
- windows animations;
- Sony Ericsson Xperia Arc sound and other stuff.....
Now we have latest update of Su binary v3.0.3.2 , Superuser v3.0.7(41), unique busybox v1.19.3 installed into system/xbin ;
There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/
Also included some tweaks : - increase sdcard speed, - managemant ram memory....and increase reaction speed !
These are the files you need for install this Custom Rom :
- archos.ext4 => http://www.4shared.com/archive/tOxGcPqa/archos.html , http://hotfile.com/dl/143897684/d5edc5d/archos.7z.html
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html ; http://hotfile.com/dl/144036333/e7d0e75/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/zip/HnEobpnG/initramfscpiogz.html
How install :
- because the file structure is changed , you need perform a clean installation : Recovery -> Format System -> Reformat Devices...-> I Understand -> ok -> copy firmware_archos_it4.aos into new driver -> ok. After reboot copy archos.ext4 into Internal Storage ( data/media/), reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all ....now you have clean install custom rom
Solved - md5sum into superuser when you try to update the su binary , now check md5sum OK!
I did not managed any version of .squashfs because android compiler can't install busybox into system/xbin ( .squashf is NOT RW ), this is why I presented only version of ext4 ...Good Luck !
****************************************************************
Update : 27/01/12
- now >adb shell - fixed and enabel vibrator
- archos.ext4 => http://www.4shared.com/zip/dOscQIvA/archos_up.html ; http://hotfile.com/dl/143982123/b452656/archos_up.zip.html
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Quinny899 said:
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Hi! ...I just increase free ram , lol !
surdu_petru said:
Hi! ...I just increase free ram , lol !
Click to expand...
Click to collapse
Ok
Sent from my ARCHOS 80G9 using xda premium
good job tomorrow i try it (multumesc )
Maryanos25 said:
good job tomorrow i try it (multumesc )
Click to expand...
Click to collapse
..cu placere ....incearca-l nu vei regreta !
with pleasure ...try it...you'll no regret !
Nu ama avut rabdare si l-am instalat. Merge ok. Merci mult.
Y dont have patience and y instaled. Its ok. Thanks.
Sent from my ARCHOS 80G9 using xda premium
Quick question, and I appologize if this is the wrong place for this, I'm currently running your 3.2.78 (ext4). Do I need to update the stock firmware directly from archos first or can I just flash this 3.2.79 rom over what I currently have. Also I "removed android kernel" earlier to always boot rooted if that matters. So what's the best way of going about this?
surdu_petru said:
I did not managed an version of .squashfs because I can't install busybox into system/xbin ( .squashf is R/O ), this is why I presented only version of ext4 ...Good Luck !
Click to expand...
Click to collapse
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
First custom rom i've seen. Great ! Thank you very much. I will try it later
First thank you surdu_petru Every new rooted/modified rom, I need to start tablet with "original" rom to copy the ext rom into the tablet, and every time, restarting for the first time after the update from sde with the "new" rom, I have SuperUser with empty list (and I have to re-add all the programs in my list). Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
hitman72 said:
Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
Click to expand...
Click to collapse
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
gen_scheisskopf said:
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
Click to expand...
Click to collapse
OK thanks !....but do not want to complicate ... I let the compiler to perform, if he says he can not because I have not rw rights !...I left it ..... I know that there are solutions, but leave it in for users !
ro4sho said:
First custom rom i've seen. Great ! Thank you very much. I will try it later
Click to expand...
Click to collapse
Thanks , lol....
gegabit said:
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
Click to expand...
Click to collapse
Sure, you can change what you want, system is RW, but attention ! do it carefully !
gen_scheisskopf said:
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
Click to expand...
Click to collapse
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
letama said:
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
Click to expand...
Click to collapse
Ok I know what you mean...and yes ! for Stock firmware_3.2.79 (files.ext4/squqsh).update exist into initramfs, but because I made some changes in directory structure into Custom Rom , now .update it's not perform .
Ok it's very good idea , for future I'll rename (archos.ext4/squashfs).update
Thanks for your advice !
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
philmein said:
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
Click to expand...
Click to collapse
Hi!
This custom rom it's work for G9 tablett 80/101 but I don't know if it is supported for HDD.....maybe @letama or or another endorsed person will answer.....for you !
Krabappel2548 and cpasjuste are proud to presents:
This is DooMLoRD's recovery, just added scripts to make it work on locked bootloader, all credits for recovery should go to him!
CWM recovery for locked bootloaders!
WORKING:
- I think All functions should be working, haven't tested all of them though.
NOT WORKING:
Phone hangs when cleaning cache?
Just leave it for a few minutes, it's needs some time to clean cache
Click to expand...
Click to collapse
- Let me know
HOW TO ENTER RECOVERY:
- Press volume up or down when green LED is on while booting
REQUIREMENTS:
- Locked bootloader
- Root
- Windows pc with adb drivers
INSTALLATION:
- Download the package and extract it to your pc.
- Run the script to install the recovery
- Enjoy it!
Error with creating file for faster backup?
This isn't a problem, it always gives an error if the file already exists, so it means you have the file already
Click to expand...
Click to collapse
Please don't mirror my download links or steal my work!
DOWNLOAD:
CWM 6.0.2.8 for locked bootloader v4
CREDITS:
- My dear friend DooMLorD for tips and some recovery files, "sbin/recovery" itself actually
- Cxpher for edit of run.sh script
- cpasjuste for his great and usefull help
INFO FOR ROM CHEFS:
1. Rename /system/bin/chargemon to /system/bin/chargemon.stock
2. Put the following files in /system/bin:
- recovery.tar
- charger
- chargemon
- ric
3. Add these lines to updater-script to set permissions:
Code:
set_perm(0, 2000, 0644, "/system/bin/recovery.tar");
set_perm(0, 2000, 0755, "/system/bin/ric");
set_perm(0, 2000, 0755, "/system/bin/charger");
set_perm(0, 2000, 0755, "/system/bin/chargemon");
CHANGELOG for CWM 6.0.2.8 v4:
- Updated run.sh script
CHANGELOG for CWM 6.0.2.8 v3:
- fixed slow backup problem
CHANGELOG for CWM 6.0.2.8 v2:
- Fixed adb
- Fixed /system problem
CHANGELOG for CWM 6.0.2.8:
- First release for locked bootloaders.
krabappel2548 said:
SOURCES:
Device configuration files: android_device_sony_yuga
Xperia Z TWRP sources: twrp_sony_yuga
CHANGELOG for 2.4.3.0 unreleased version:
- Fixed settings => screen: brightness changing is working now.
CHANGELOG for 2.4.3.0 stable:
- Fixed internal storage
- Fixed layout (may be small errors, but I needed to create a complete new mayout for 1080x1920)
- Fixed cache issue
- Fixed backup issue, won't backup internal storage data anymore
- Fully functional and working as it should
CHANGELOG for 2.4.3.0 beta 1.1:
- Partially fixed layout
CHANGELOG for 2.4.3.0 beta 1:
- First release for Xperia Z
- All basic functions are working
- Layout isn't ok yet.
- Internal storage isn't working yet
Click to expand...
Click to collapse
You ROCK DUDE!!!!!!!
trying now, just to clarify???
once installed i should be able to nandroid backup and flash mods as i would with an unlocked bootloader?
Процесс идет нормально, но в большинстве rekoveri не идет.
xl VipeR lx said:
You ROCK DUDE!!!!!!!
trying now, just to clarify???
once installed i should be able to nandroid backup and flash mods as i would with an unlocked bootloader?
Click to expand...
Click to collapse
If it works you can flash stock based roms, mods and take backups yes
Let's hope it works!
barbik said:
Процесс идет нормально, но в большинстве rekoveri не идет.
Click to expand...
Click to collapse
English please. I uploaded test 1.1, fixed the flashing script.
xl VipeR lx said:
You ROCK DUDE!!!!!!!
trying now, just to clarify???
once installed i should be able to nandroid backup and flash mods as i would with an unlocked bootloader?
Click to expand...
Click to collapse
I get the following error: Cannot stat sh, no such file or directory, is it meant to be sh? or su?
EDIT: Flashing the new test file
krabappel2548 said:
If it works you can flash stock based roms, mods and take backups yes
Let's hope it works!
English please. I uploaded test 1.1, fixed the flashing script.
Click to expand...
Click to collapse
Also cooked rom?
Thanks Also you are great developer
Thanks for your work.
xl VipeR lx said:
I get the following error: Cannot stat sh, no such file or directory, is it meant to be sh? or su?
EDIT: Flashing the new test file
Click to expand...
Click to collapse
Ok, let me know how that one went
tanoxxx said:
Also cooked rom?
Thanks Also you are great developer
Thanks for your work.
Click to expand...
Click to collapse
Yes, as long as the rom is stock based and the developer says it should work, it should work
Only thing is that recovery needs to be included in the rom or it will be lost, but I'll add instructions for rom cookers when I know the recovery works
tanoxxx said:
Also cooked rom?
Thanks Also you are great developer
Thanks for your work.
Click to expand...
Click to collapse
Still not working, now i get the following error
xl VipeR lx said:
Still not working, now i get the following error
Click to expand...
Click to collapse
ok, I'll check the script again, scripts isn't really my thing
krabappel2548 said:
damn that means I deleted the wrong line from my script
Click to expand...
Click to collapse
lol its ok, paitently waiting im reading the bat file to see if i can make out anything
are you supposed to have the -C in adb shell "su -c /data/local/tmp/twrp/step3.sh"
if i remove it i just get UNKNOWN ID in the error
krabappel2548 said:
Ok, let me know how that one went
Yes, as long as the rom is stock based and the developer says it should work, it should work
Only thing is that recovery needs to be included in the rom or it will be lost, but I'll add instructions for rom cookers when I know the recovery works
Click to expand...
Click to collapse
Thanks
Sorry finished my daily Thanks
Re: [Locked Bootloader]TWRP Touch recovery 2.4.3.0 for locked bootloaders - test1 [12
Do i have to connect my phone in flash Mode to install it? Thanks
"Swyped" From My X10Mini Running SevenBean Stable3
pongnamu said:
Do i have to connect my phone in flash Mode to install it? Thanks
"Swyped" From My X10Mini Running SevenBean Stable3
Click to expand...
Click to collapse
NO, same way as you rooted the locked bootloader, just connect while its on.
ITs currently not working, krabappel is working on it
Have no problem with installation I think, but i will not come into recovery with vol up and so on.
Witch buttons should I push?
xl VipeR lx said:
lol its ok, paitently waiting im reading the bat file to see if i can make out anything
are you supposed to have the -C in adb shell "su -c /data/local/tmp/twrp/step3.sh"
if i remove it i just get UNKNOWN ID in the error
Click to expand...
Click to collapse
I found the problem forgot to add one line and one file
Reuploading now
tanoxxx said:
Thanks
Sorry finished my daily Thanks
Click to expand...
Click to collapse
no prob
pongnamu said:
Do i have to connect my phone in flash Mode to install it? Thanks
"Swyped" From My X10Mini Running SevenBean Stable3
Click to expand...
Click to collapse
no, just usb, with usd-debuggin and unknown sources active
eagle1977 said:
Have no problem with installation I think, but i will not come into recovery with vol up and so on.
Witch buttons should I push?
Click to expand...
Click to collapse
installation couldn't be succesfull, one file was missing and script wasn't ok, new test file is up
Flashing works, no more errors in the script, it is possible be that you can't enter recovery yet. I've never made recovery for locked bootloaders
krabappel2548 said:
installation couldn't be succesfull, one file was missing and script wasn't ok, new test file is up
Flashing works, no more errors in the script, it is possible be that you can't enter recovery yet. I've never made recovery for locked bootloaders
Click to expand...
Click to collapse
I was actually thinking there was no sh file to push yet we chmod sh? lol it has flashed, testing now
My phone is now broke, everytime i try and boot up, it just gives me a battery icon, nothing else?!?!?
Im stuck in a boot loop
xl VipeR lx said:
I was actually thinking there was no sh file to push yet we chmod sh? lol it has flashed, testing now
My phone is now broke, everytime i try and boot up, it just gives me a battery icon, nothing else?!?!?
Im stuck in a boot loop
Click to expand...
Click to collapse
Confirmed
xl VipeR lx said:
I was actually thinking there was no sh file to push yet we chmod sh? lol it has flashed, testing now
My phone is now broke, everytime i try and boot up, it just gives me a battery icon, nothing else?!?!?
Click to expand...
Click to collapse
ok, I'll remove download link for now, need to fix that first. You'll need to flash an .ftf then, you can uncheck the wipe data and cache etc to restore to stock fw.
Sorry guys. I'll try to fix it asap.
TWRP Recovery
For Galaxy Mini
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
LIVE SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
chraso: For his precious help.
Me: For compiling it for Galaxy Mini.
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.upload.ee/files/3992673/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
What to test in latest build?:
-NOTHING. IT IS STABLE NOW.
Reserved
Will test it the moment I get home. Which is about 4 hours from now...
Tapatalk-kal küldve az én GT-S5570-el
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
+1
arpitkh96 said:
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
Click to expand...
Click to collapse
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Bhargav97 said:
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Click to expand...
Click to collapse
terminal method doesnt works either.here is the log
arpitkh96 said:
terminal method doesnt works either.here is the log
Click to expand...
Click to collapse
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Bhargav97 said:
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Click to expand...
Click to collapse
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
arpitkh96 said:
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will be back after a re-compile.(15-20 min)
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Bhargav97 said:
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Click to expand...
Click to collapse
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
hard bricked
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
sushil888 said:
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
Click to expand...
Click to collapse
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
ast00 said:
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
Click to expand...
Click to collapse
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Bhargav97 said:
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Click to expand...
Click to collapse
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
ast00 said:
It's vibrating non stop and it only stops if I reboot.
Tapatalk-kal küldve az én GT-S5570-el
Click to expand...
Click to collapse
For me its not vibrating continuously but duration of vibration on a click or touch is really large.
One bug I noticed is that progress bars are not resized.
While backing up a ROM the indeterminate progress bar is fine but the blue one showing exact progress is not resized.
Its width is larger (it goes out of screen on rhs) and height is smaller than that of indeterminate progress bar so it doesn't actually appears as an overlay.I don't have camera now to show you a pic.I will show you pic after 2hrs
Sent from my GT-S5570 using XDA Premium 4 mobile app
ast00 said:
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
Click to expand...
Click to collapse
Logs look fine.
@arpitkh96 says it's not vibrating non-stop but duration of vibration is long. I think, that can be managed somehow.
About the other report you gave of error when installing zip:
Your zip file's update-binary is old. You will need to update it. Replace /META-INF/com/google/android/update-binary file from cm11 or omni4.4 zip. You will need to do it in ANY zip that doesn't install. This is the way it works. KitKat has changed many a things, this is one of them.
Please try this and give result.
And, cm11 or omni or any other ROMs are installing or not?
Also, what do you mean by "mounting-unmounting partitions doesn't do anything." If the partitions are not mounted, your log would have errors but there are no errors.
@arpitkh96,
I know about that progress bar bug. Its theme related. I would fix it after fixing major recovery problems.
You can use any 240x320 twrp theme uptil then. It would work just fine.
For more info on Themes for TWRP, visit here:
http://forum.xda-developers.com/nexus-4/themes-apps/twrp-theme-collection-thread-t2035234
Ok guys here is a custom recovery for the metro 2016 variant of the Galaxy J700t1 (Metro PCS) Flash with FlashFire or with Odin. Custom recovery but it won't mount the internal sd yet. Can't flash or backup.. so its still a work in progress, but its a working recovery other than that lol. Must be rooted first. Make sure that you download root file explorer and ensure you have a copy of su and busybox in your /system/bin and /system/xbin folders. Make sure you have USB debugging on, OEM on, and unknown sources on in System-Developer options. Thanks to Paco for the root exploit! But we needed a recovery for this fine device. Enjoy!
EDIT: SOME CLARITY FOR EVERYONE... ok, so here's the deal. In marshmallow the system is write protected after you trip KNOX 0x1. The system will persist and will lose integrity if the stock kernel's "CASHE" gets changed. hmmm.... so. this is what you need your system to be at if you want to flash a custom kernel or recovery with flashfire or flashify: After you root with Paco's method, you should be on stock rooted rom with stock recovery. when you flash with flashfire DO NOT WIPE CASHE OR DALVIK CASHE OR FORMAT CASHE in ANY WAY ... IT WILL SEND YOU INTO THE "RESET MODE"... NO worries tho. If this happens to you , ODIN this stock kernel CASHE that i'm posting below and you should boot back up. Keep in mind what you're doing as well... if for some reason you hit the "RESET" SCREEN, don't flip... just ODIN the partition you changed back to stock whether it be the kernel or in this case the RECOVERY. ... also, try not to use ever root in flashify/ flashfire because it lowers the permissions for the SU binaries and removes SU from some of the system folders.
INSTRUCTIONS:
1. start from stock if you can.
2.root via paco's method HERE
3.I would make sure you have a stock copy of the stock firmware (ROM KERNEL RECOVERY) on your computer just in case
HERE
4.download my cwm port for the j700t1 below and put it on the root of your drive or anywhere on your phones internal memory (not your external sd card)
5. Download root browser from the playstore as well as flashfire or flashify or both.
6.rename the cwm.img to recovery.img with root browser and ensure that you have SU and Busybox in /system/bin , /system/xbin , and it wouldn't hurt to have it in ~#/sbin as well..... AND check the permissions with root browser to make sure the permissions are set to 0777 (rwrwrwrw)
7. In "Flashfire" click the "+" symbol - click "Flash firmware package" -- Go to the cwm "recovery" file you put on your internal sd card and select the file. Fireflash will bring a screen up saying "Partitions" at the top showing the package. Click the check mark at the top right. FlashFire will go back to the "Actions" screen. Click"reboot" toward the bottom. Under the "reboot" screen, click recovery to boot directly into your new recovery after the flash. Uncheck Preserve recovery- click the check mark at the top right again. Click "Flash" at the bottom. --- wait. Device will reboot... flashfire will take over and your loading screen willl flash by... phone will boot back up into CWM....
To Flash ODIN tars --- Rename the perspective tar to the partition it goes to before trying to odin. Example: rename "cwm.recovery.img." to just "recovery.img" ... Same with the stock kernel tar below. . rename to "boot.img" then ODIN.
Sideload apps or ROMS or ZIPS just don't wipe any cashe partitions until we can get a good custom kernel. I could use the help with the kernel I will be honest. I can get it done but with a lot of trial and error. Anyone who can remove the SELinux write protection from the kernel please contact me.. I'm working on it. I was able to get a custom kernel to boot. but still no r/w mount for the USB yet. Just keep the CASHE lol. One more thing.. if your'e testing kernels, everytime you have to odin a stock kernel you will LOSE ROOT, so go ahead and re-root again.
https://drive.google.com/file/d/0B_WsJ57QBykaQ3ROeFZnajNzbmc/view?usp=sharing --- CWM img
CWM.TAR-- (new
--Stock Kernel CASHE.tar
Stock KERNEL
Team Rejectz
removed as it was reported not working by @timmetal6669
messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
thank you!! the one I sent you? will flash right away
timmetal6669 said:
thank you!! the one I sent you? will flash right away
Click to expand...
Click to collapse
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
not working...
do not flash this
Here is an odin flashable copy of the j700t1 stock kernel to get you booting again. just go into download mode, open odin and flash this if you happened to flash one of the kernels above
https://drive.google.com/open?id=0B_WsJ57QBykaSDRlQXlXSnpSd28
messi2050 said:
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
Click to expand...
Click to collapse
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
timmetal6669 said:
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
Click to expand...
Click to collapse
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
Sent me into a loop... but I'm the metro pcs variant
Oh update... If anyone uses that odin flashable stock boot.img .. remember it IS a stock boot img. you will lose root. but you won't lose your system and your apps.. so just re root using paco's CF autroot exploit.
messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
might just be what i'll have to do.. the boot image is its own source
So no progress on the recovery to backup or flash yet?
Krumplife4400 said:
So no progress on the recovery to backup or flash yet?
Click to expand...
Click to collapse
Im working on it. the recovery is flashable and it works... just won't mount the SD right now... I have to right a script or look for a work around.. give me a bit...might take a few days. I'm a single dad and im' in school. I do this cuz i love it and I just bought this phone... Don't worry.,.. I'll be making ROMs before you know it... lol... mods everything... look up my threads lol
Thanks keep up the good work
Are you able to mount USB-OTG?? I am about to leave work so I haven't had a chance to play yet!
I can confirm it boots on j700t as well. I haven't flashed anything but it's there. I got twrp to boot and stay for roughly 5 minutes but still cannot mount anything either.
Sent from my SM-J700T using XDA-Developers mobile app
Verification Failed
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
!Led*Eyes! said:
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
Click to expand...
Click to collapse
Start over.
Set up phone like day one
Re-root with cf auto root
Update su binaries
Install BusyBox
Install flashify
Download IMG from op
After download, tap on IMG file should bring up flashify as an option
Flash IMG and reboot
Profit.
- I see you're good but no cwm? Skip start over root part and use flashify.
-sent from this device using this app.
So flashify over flashfire ? Ill give it a shot. Thanks
!Led*Eyes! said:
So flashify over flashfire ? Ill give it a shot. Thanks
Click to expand...
Click to collapse
No problem
sent from the interwebs using dis here application an m'digits....
I decided to just try it with flashify without reverting everything back to stock and voila! I chose the google drive option when searching for the file so it did download it again.... i re member reading something a while back about about a similar issue with not being able to mount the sdcard because the fs was encrypted and the recovery couldnt read it. I think they overcame by formatting the sdcard but i do not know .. i realize that simply formatting the sd in recovery and trying to mount would be fruitless but could the trouble be in the "expected recovery key" ? Just a thought. Thanks again timmetal6669 & OriginalShinken1 for the beta and the help. You guys are so close!
Has anyone tried to sideload a ROM yet since we can't flash?
CTR Recovery for Galaxy A5
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands