Database Users

[MOD] Custom Boot Screen (for Gingerbread ROM's)

Well I had been getting asked a lot lately about the GB ROM's and my original boot screen packages that I had created where I modified a param.lfs to contain no boot image and allowed a script to place whatever image you wanted in it's place for a custom boot logo. In the past I had edited the param.lfs for the AT&T i897 bootloaders which does not work with the GB boot loaders.
This is not the boot animation, nor the kernel logo, but the first logo your phone displays when it's turned on.
Anyhow, I re-wrote the param.lfs to allow a blank for the logo.jpg that Gingerbread calls upon in the bootloader and it works great. So for all of you that used my boot screen package in the past for i897, i9000 and t959 2.1, 2.2 and 2.2.1 ROM's, here it is again for 2.3+ ROM's.
This should also work fine for Vibrant but I will check in case any T959 people are scoping this out.
These will not be compatible with CM7 (due to the proprietary fs used on param.lfs)...
Big thanks to TRusselo for being a BETA tester, tossing in the latest ODIN package and writing the readme as well as contributing the JPEG's offered in the package. I decided to keep the Canadian boot screens for you northern neighbors on the Roger's network up there...
Donations are always welcome but not required, press THANKS, follow me on Twitter or like my cause on FaceBook.
Download the package below...
http://dl.dropbox.com/u/19201431/Files/MobileTechVideos_GB_Boot_i897_t959_i9000.zip

^ Appreciate this....
and good to hear from ya again.

For2ndtwin said:
^ Appreciate this....
and good to hear from ya again.
Click to expand...
Click to collapse
No problem. I'm still really active, here on XDA. Just try to limit my content to my website since they monitor me very heavily...

FROYO VIDEO!!
make sure to read the read me file!!!!
For i897 Froyo/ Ecliar /Gingerbread bootloaders
http://download1073.mediafire.com/teuilo1p1h7g/n3l6527tvt7a4v5/MobileTechVideos_i897_Boot.rar
with images included : http://dl.dropbox.com/u/19201431/Files/i897_Froyo_Gingerbread%20boot%20fix.zip
note: jpg image called logo_ATNT.jpg (even for rogers) READ THE README!!!
For i9000 Gingerbread bootloaders running on captivate
http://dl.dropbox.com/u/19201431/Fil...t959_i9000.zipnote: jpg image called logo.jpg
FOR i896 ROGERS Gingerbread bootloaders
http://dl.dropbox.com/u/19201431/Files/i896_gb_boot_screen.zip
note : final image file called logo.JPG <captial JPG is IMPORTANT> and **not** ATNT like captivate version~!
READ THE README!!!
Here is the GINGERBREAD PICS that are included.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here are some more single images:
fuloplori said:
Thought I'd share some pics that I've used
View attachment 736044View attachment 736045View attachment 736046View attachment 736047
Cheers
Click to expand...
Click to collapse

see above...

Done, soft-bricked (Odin failed) but got back into DL mode and re-flashed. I've got the i896 logo up there now.
Thanks a lot!

yeah odin sometimes does that... the newer odin does that LESS.. lol.
i soft bricked a few times using this.
just keep forcing the params until it passes, no need to go back to stock!
with GB button combos, and the soft brick, i found:
Vol Down + USB = Download mode
Vol Down + Pwr = Soft brick screen.
hope that helps.

Just an fyi to anyone not familiar with it, but you will have to make sure you have your screen active when running the batch file so that you can click Allow to the superuser permission request when it attempts to mount the partition.
This wasn't noted in the readme, someone without much experience might miss it.

Just a question but why are there some screens with "AM HUNG" as the name and not Samsung?

kimchi0400 said:
Done, soft-bricked (Odin failed) but got back into DL mode and re-flashed. I've got the i896 logo up there now.
Thanks a lot!
Click to expand...
Click to collapse
When you soft bricked and reflashed did you have to do the whole rom or just this process in particular?

impulser91 said:
Just an fyi to anyone not familiar with it, but you will have to make sure you have your screen active when running the batch file so that you can click Allow to the superuser permission request when it attempts to mount the partition.
This wasn't noted in the readme, someone without much experience might miss it.
Click to expand...
Click to collapse
thanks i updated the readme in the dropbox link above.
man dropbox is amazing!

jonnyg1097 said:
when you soft bricked and reflashed did you have to do the whole rom or just this process in particular?
Click to expand...
Click to collapse
read the post below that. please.
jonnyg1097 said:
Just a question but why are there some screens with "AM HUNG" as the name and not Samsung?
Click to expand...
Click to collapse
really? why? i need to explain?

OP link updated.
1 new bootlogo added, instructions updated, 2 pictures fixed

OP, you should add that these will not be compatible with CM7 (due to the proprietary fs used on param.lfs).

readme instructions updated. thank you
gotta love drop box!
im hosting the file and maintaining.

tuesday morning bump!!!!!

I
have adb installed and working for at least a year now. However, your program just tells me that adb is not recognized as a command. at the end it does say enjoy your new bootscreen and it gives me a screwed up bootscreen. Yes the file is only 96kb and yes I named it correctly. and yes I have usb debugging on and no the phone isn't mounted. I am using mosaic 1. Any ideas?

jhr5474 said:
have adb installed and working for at least a year now. However, your program just tells me that adb is not recognized as a command. at the end it does say enjoy your new bootscreen and it gives me a screwed up bootscreen. Yes the file is only 96kb and yes I named it correctly. and yes I have usb debugging on and no the phone isn't mounted. I am using mosaic 1. Any ideas?
Click to expand...
Click to collapse
Have you rebooted the PC? ADB is known to get stuck sometimes. Also retry the process but make sure to close all the adb.exe processes using task manager.

connexion2005 said:
Have you rebooted the PC? ADB is known to get stuck sometimes. Also retry the process but make sure to close all the adb.exe processes using task manager.
Click to expand...
Click to collapse
OK I restarted the comp and made sure their were no adb processes running and still your tool does not work it says killing all adb processes and then says adb is not recognized as an internal command. I know adb works because I used cmd:adb devices and it showed my phone. So what is the deal with this program? I am on 7 but I used run as administrator so it should work.

jhr5474 said:
OK I restarted the comp and made sure their were no adb processes running and still your tool does not work it says killing all adb processes and then says adb is not recognized as an internal command. I know adb works because I used cmd:adb devices and it showed my phone. So what is the deal with this program? I am on 7 but I used run as administrator so it should work.
Click to expand...
Click to collapse
It's got to be something with your instance. I use this all the time with Windows 7 x64...

2.37 has been rooted!

I have tested it on my phone, it works perfect!
SORRY FOR MY BAD ENGLISH. I HAVE THE CHINESE WORDS ON MY PHONE, SO I DO NOT KNOW WHAT THE ENGLISH EXACTLY IS. I TRANSLATED THEM ON MYSELF, IF YOU DONOT UNDERSTAND MESSAGE ME.
1, you should FLASH RECOVERY TO YOUR PHONE, and that will not be talked here. lots of threads can tell you how to do it.(I HAVE PLACED ONE WAY TO DO IT ON THE SECOND PAGE)
2, unpack "root.rar" into your DISK C, and the folder must be "root"
3, now mark the "debug mode"( you can find it in application Settings) , connect your phone to your computer( just CHARGING MODE)
4, press win+R on your PC keyboard, and type in "cmd".
5, now we can see dos commond, you should type in the following commond one by one.
CD C:\root
adb shell
reboot recovery
6, now your phone should reboot into recovery. select mounts and storage. there select 3 items( mount /system, mount /data, mount /sdcard)
7, disconnect your phone, and connect it again. then type the following commonds into your PC. NOTE THE SPACE
adb push su /sdcard/su
adb push superuser.apk /sdcard/superuser.apk
adb push psneuter /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
8, if you can see "~#" on your screen, you have made it. I have encountered a error on the 5th commond but it seems like ok, afterall I have been rooted.
9, you still have some commond to type.
cp /sdcard/su /system/bin/
cp /sdcard/Superuser.apk /system/app/
ln -s /system/bin/su /system/xbin/su
chmod 06555 /system/bin/su
10, now on your phone you should still have the recovery, unmount the /system, data, sdcard.
11, reboot your phone, and enjoy it!
Thanks very much for the help of pxw816, without him I still in dark.

is this for real? :\

adkz said:
is this for real? :\
Click to expand...
Click to collapse
Sorry for forgeting to upload the file. It works on the chinese rom, I think all rom can be rooted this way...

Anyone willing to see if this would work on a Telus Desire HD with 2.43?

Anyone tried this ?

I'm quite sure this only works on the Chinese ROM. But I might give it a try

I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.

torkaberry said:
I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.
Click to expand...
Click to collapse
Same problem, booting into recovery just shows this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think this is the second method posted that only works in China

CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Seems like the chinese OTA's have an unpatched exploit, maybe one of the mods would like to change the title of this thread.

hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help

CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Hey guys, you cannot use the official recovery, flash a recovery that is usually used to install a rom...My recovery is 3.0, I don't know if 2.0 is ok....

evanbigfan said:
hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help
Click to expand...
Click to collapse
I'm not quite sure about that, for people who do not have a recovery may place the following file on your TF card( DO NOT PLACE IT INTO ANY FOLDER!), and shut down your phone(I MEAN COMPLETELY OFF, OR YOU CAN PULL OUT YOUR BATTERY). Then try to press the volume down button and the switch button at the same time to start your phone. See if the recovery can be installed automatically or not. if not, I'm afraid you have to downgrade to root and get a S-Off. If you do not know how to downgrade, post here, and see if i can give you any help or not.

This will never work, you will need Root and S-OFF to flash recovery. (thanks hawks556 for pointing that out)
closed.

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.

*reserved*

Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!

Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again

LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.

Hi mrew42,
Thanks a lot! Much appreciated!

Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81

Letama, can you may be make the same for 3.2.81?

Yes, it will come soon...

3.2.81 is up and instructions on first post updated if you upgrade.

Great
http://www.jbmm.fr/?p=27601
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!

Thanks, will try it out soon.

Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.

ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.

I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?

No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.

Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!

hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!

lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

[How To] Root [I9100][ROM 4.1.2] With Stock Recovery

Root FJ10 Without Custom Kernel​
As we all know FJ10 has been released and is floating around the internet, and iv'e decided to share the way i rooted the leak (International SGS II) using stock samsung recovery
Credits
Chainfire CWM-Supersu
Sextape Leak​rwilco12 Continue to hosting leak
What you need
PC/MAC/Linux
ADB
USB Cable
Phone
CWM-SuperSU-v0.97.zip
There is two ways to flash the root package in custom recovery (sorry i keep forgetting the other way)
Thank You Sh4Dy for reminding me
Flash Trough Update
1) Download CWM-SuperSU-v0.97.zip
2) Rename CWM-SuperSU-v0.97.zip > update.zip
3) flash as an update
Instructions
1) Enter Recovery mode by holding power+volume up.
2) Connect USB Cable to the phone and PC
3) Choose Install Update with adb
now
4) Now in your terminal/CMD write adb sideload CWM-SuperSU-v0.97.zip
5) Look at the screen and you will see the update package being installed
Congratulations you got now a rooted FJ10 leak without flashing a custom kernel
Proof
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks, but I get stuck at 3.
I go to search -> cmd and then I type adb sideload CWM-SuperSU-v0.97.zip in it. I think this is wrong but I never worked with ADB.

how it works now? i don't get it also

dajumper said:
how it works now? i don't get it also
Click to expand...
Click to collapse
Works fine here
You need to install adb then cd to the adb directory, then type the command.

Why is it even in dev section?

Spyr0s said:
Works fine here
You need to install adb then cd to the adb directory, then type the command.
Click to expand...
Click to collapse
Will try that tomorrow!
Verstuurd van mijn GT-I9100 met Tapatalk

dajumper said:
how it works now? i don't get it also
Click to expand...
Click to collapse
Make sure you have adb installed on your pc
after that begin with step 1

Doesn't work at 4th step for me, I check devices in adb devices and it shows my device but some large-ass thing comes n it doesn't install the SuperSU zip for some reason

Same thing here

wrong thread. plz delete

ssilviu said:
Same thing here
Click to expand...
Click to collapse
did you also use the supersu provided in op?
Sh4Dy said:
Doesn't work at 4th step for me, I check devices in adb devices and it shows my device but some large-ass thing comes n it doesn't install the SuperSU zip for some reason
Click to expand...
Click to collapse
did you use: http://download.chainfire.eu/267/SuperSU/CWM-SuperSU-v0.97.zip

Hey guys, Just apply the .zip from external card via recovery, the .zip in OP, worked for me
Edit: Yes mate, I used that file only, you copied it from Sprint S2's JB thread? Coz I can see the screenshot is of Oct 11 firmware.

Sh4Dy said:
Hey guys, Just apply the .zip from external card via recovery, the .zip in OP, worked for me
Edit: Yes mate, I used that file only, you copied it from Sprint S2's JB thread? Coz I can see the screenshot is of Oct 11 firmware.
Click to expand...
Click to collapse
yes i did, as i know this will work with it too

Buy mobile odin, flash the rom, then you will get root. Quite simple.
I love new rom.
But it wipe all my data system apps...

bogdan1980 said:
Buy mobile odin, flash the rom, then you will get root. Quite simple.
I love new rom.
But it wipe all my data system apps...
Click to expand...
Click to collapse
that isn't mobile odin problem, its wiped automatically

Yeh man, it should work with this too, but idk, flashing zip did the job for me. Try it yourself

Sh4Dy said:
Hey guys, Just apply the .zip from external card via recovery, the .zip in OP, worked for me
.
Click to expand...
Click to collapse
failed to mount sdcard

Sh4Dy said:
Yeh man, it should work with this too, but idk, flashing zip did the job for me. Try it yourself
Click to expand...
Click to collapse
i added your instructions to OP and added you as credit for reminding me :highfive:

ssilviu said:
failed to mount sdcard
Click to expand...
Click to collapse
This is why adb sideload is powerful (as on sprint we were never able to access sdcard)

If you want, I can give proof, I'm currently restoring apps from Ti Backup Pro

[Utility] Desktop Rom Flasher!! (Drag Drop & Flash!)

Hello everyone, so I developed a small application called Desktop Flasher. All you need to do is drag the zip you want to flash and it'll automatically push it to your phone, write the appropriate script, and reboot you into recovery, and perform the flashing procedure. I hope to add new features (wireless support) as time goes on. Try it out and tell me what you think
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Drag Drop and Flash
Wipe Cache/Dalvik and Data
Changelog:
1.0
Initial Release
1.1
Minor Bug Fixes
Incorporated Silent Updater
1.2
Fixed Permission Issue
1.3
Created First Time Run Program to avoid any setup issues
Auto renames zips with spaces in their title
1.4
Small adjustment
Confirmed working on TWRP and CWM, I have not tested any other recovery, but it still should work the same. Please report back your findings.
Download and Extract the attached zip, and run Desktop Flasher.exe to launch,
When Launching the App for the very first time, I highly recommend that you update it to avoid any potential problems.
To Update the App just open it, and close it (via the usual x or exit button).
Source code: https://dl.dropboxusercontent.com/u/9134840/Desktop Flasher/Desktop Flasher.zip

FAQ
I get a failed to push script/or during the first run program it can't detect my device in recovery mode!
You probably don't have the drivers installed for adb in recovery mode. It's easy though! Follow this quick guide here: http://forum.xda-developers.com/showthread.php?t=1379875
Okay, so the program says "Great your Phone will do the rest" and my phone reboots into recovery, but nothing happens...wth??
Most likely the issue is that you're using a recovery that doesn't support openrecoveryscripting. (The official version of CWM and TWRP do)

How to connect device ? ... is debug mode?

phamtlsoft said:
How to connect device ? ... is debug mode?
Click to expand...
Click to collapse
Yes, just make sure USB debugging is on, and your drivers are already installed.

will it work with a Galaxy Note
Custom Rom and cwm
I made a few themes and had always to copy over the zips and flash them via phone
so I would be really happy if it will work on my device
sent from my G-Note

hara74 said:
will it work with a Galaxy Note
Custom Rom and cwm
I made a few themes and had always to copy over the zips and flash them via phone
so I would be really happy if it will work on my device
sent from my G-Note
Click to expand...
Click to collapse
Cool. Yeah this should work on any device, I and any recovery with Openscript available (TWRP and CWM). I haven't tested cwm but I can confirm that it works on TWRP.

filmaker said:
Cool. Yeah this should work on any device, I and any recovery with Openscript available (TWRP and CWM). I haven't tested cwm but I can confirm that it works on TWRP.
Click to expand...
Click to collapse
ok, thanks for ur answer
I'll give it a try and report the result
sent from my G-Note

when I drag&drop a zip,
it comes that massage: "Failed to Push Zip to SDcard"

hara74 said:
when I drag&drop a zip,
it comes that massage: "Failed to Push Zip to SDcard"
Click to expand...
Click to collapse
Hmmm...alright. Your phone is connected and USB debugging is enabled?

filmaker said:
Hmmm...alright. Your phone is connected and USB debugging is enabled?
Click to expand...
Click to collapse
yes
sent from my G-Note

hara74 said:
yes
sent from my G-Note
Click to expand...
Click to collapse
Alright, I think I figured it out. Does the location you're dropping from or the zip itself happen to have any "spaces" in the name? E.X. D:\documents\my rom\rom.zip

the zip definitely not,
but I look at folder on pc tomorrow,
now it's off already
will report then
sent from my G-Note

Alright Cool.
Released a new update, it'll fix possible flash errors in recovery.

jup, it was the spaces in the zip :good:
but now it shows: Failed to push Script
the files are copied to phone correctly

hara74 said:
jup, it was the spaces in the zip :good:
but now it shows: Failed to push Script
the files are copied to phone correctly
Click to expand...
Click to collapse
Okay, I just released an update that'll fix it. To update the program just open it, then hit the exit button, and it'll update. The problem was with some devices you can't push to /cache unless you're in recovery. When I'm running sense it works fine, but whenever I switch to AOSP, I would run into that issue. Fixed now

I used the new one v1.1
sorry, I just saw there's a 1.2
will try it again
sent from my G-Note
---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------
I just tried it with the new 1.2,
but unfortunately it booted into recovery without doing anything else,
it´s like I would boot into recovery manually
then after a few seconds it pops up again: Failed to push Script :crying: :crying: :crying:

hara74 said:
I used the new one v1.1
sorry, I just saw there's a 1.2
will try it again
sent from my G-Note
---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------
I just tried it with the new 1.2,
but unfortunately it booted into recovery without doing anything else,
it´s like I would boot into recovery manually
then after a few seconds it pops up again: Failed to push Script :crying: :crying: :crying:
Click to expand...
Click to collapse
Hmmm...alright. Lol thanks for being my only dignified tester haha. Okay, can you do me a favor. Download the zip I attached to this post, and run the recovery.bat file. (It'll reboot your device into recovery and attempt to push a file to your cache after a 25 second delay) and can you tell me the output. (Whether it pushes or gives a permission error) Thanks.

no problem m8,
I'm lucky to test a tool which helps me later
I'll test it later, bcs I have to watch a horror movie right now,
order from boss (my wife)
sent from my G-Note

I downloaded ur zip, extracted it and run the bat, but that´s the result:
it didn´t anything with my phone

hara74 said:
I downloaded ur zip, extracted it and run the bat, but that´s the result:
View attachment 2163004View attachment 2163005
it didn´t anything with my phone
Click to expand...
Click to collapse
Ooops, sorry forgot to throw in adb. Now try it.