WARNING: IN THE EVENT THAT ANYTHING GOES WRONG, I WILL NOT BE HELD ACCOUNTABLE. I CANNOT STRESS THIS ENOUGH!!!
EDIT: I FORGOT, BEFORE CHANGING RECOVERY OR DOING ANYTHING, ALWAYS DO A NANDROID BACKUP!!!
If you have flashed a custom recovery (clockwork, j_r0dd, etc.) but you want to
1) accept OTA updates but cant do so with the custom recovery
2) send your phone for repair and not void your warranty
3) or UNROOT YOUR PHONE,
it should be easy to revert back to your stock recovery that came with your phone.
NOTE: THIS PROCEDURE WILL ONLY WORK IF THERE IS AN AVAILABLE OTA UPDATE FOR YOUR PHONE!!!
YOU WILL HAVE TO RE-ROOT YOUR PHONE IF YOU WANT ROOT ACCESS AFTER UPDATING! DO NOT RE-ROOT IF YOUR PHONE IS TO BE SENT FOR REPAIR!
Step 1) Download the OTA update. (I have a uploaded a sample update zip at
www . sidsoftinc . com / Blur_Version.0.3.9.MB300.Retail.en.03.zip
*remove the spaces)
Step 2) On completion, the phone should reboot and enter recovery mode, using the custom recovery to update. However, this should fail as most custom recoveries prevent original updates. Note the location of the downloaded update (likely at /cache)
Step 3) Power down the phone and enter into recovery mode manually
Step 4) Using ADB, pull the folder containing the update zip to your computer
Code:
adb pull /**storedlocation**/**nameoftheupdate**.zip update.zip
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Step 6) Open up the adb shell and flash the new recovery (recommended)
Code:
adb shell
su
flash_image recovery recovery.img
or you can place it in /system and it will be auto-flashed (not recommended)
Code:
adb push recovery.img /system/recovery.img
Step 7 (if possible) Make it permanent by deleting the custom recovery in /system
Code:
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Step 8) Reboot the phone and if you see a triangle warning sign, reboot your phone again. You should see your homescreen before it reboots to install the update again. This time, the original recovery will be used.
Once finished, your phone will be upgraded, unrooted and your applications and data will still be retained.
If you wish to install your previously used custom rom again, you must flash the custom recovery and install the rom, again
If I made a mistake, please do inform me. Thank you
I'm trying to do this for the Tmo G2 and I have reverted using another technique but the clockworkmod is still there. I thought it would get removed!
I have no idea how to get rid of it. Can you give me alittle help?
Did your clockworkmod recovery flash itself into your nv ram. If so then no one can help you there. If you have an ota update and pulled it to your pc, send me a coy and I'll see if I can help you. If you can, send me your ota update zip to [email protected].
Sent from my Motorola Backflip using the XDA App
I'm honestly unsure if it flashed to the nv-ram. Possibly, basically if I do a system boot (power +vol down) and select recovery, it will load the HTC green text with white background then go into clockword recovery. I'm not exactly sure why it still does this.
I used the method on this FORUM THREAD to un-root and get back to stock (using the available files there and method 1-a). I'm just unsure why the clockwork recovery is still there. I'm hoping I can still get back to stock recovery. Possibly I just need to flash the stock recovery.img??
Also, I had some troubles initially with ADB, which is why I used the VISIONary method of rooting. I'd love to try out the gfree method since I believe my ADB is working correctly now and test out some other roms to see what I like the most.
I know you are probably in a different time zone that is way ahead of mine........but can't I just reflash the stock or update ota recovery.img in fastboot mode.......OR is this a bad Idea???
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
siidheesh said:
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
Click to expand...
Click to collapse
I tried flashing the stock recovery but I'm not sure why it didn't work, I had hboot and flash_image. I used the adb shell way as well. It gave me error in partitions or whatever. I don't know what to do.
do you have Blur_Version.0.3.10.MB300.Retail.en.03.sbf file?
I dont happen to have that file, but i do have Blur_Version.0.3.9.MB300.Retail.en.03.zip
if you need it.
Cockwork Mod
I'm pretty green so this may sound really dumb, but can you flash sbf files to your phone via Clockwork Mod, or does it have to be done via RSD Lite. I cannot get RSD to recognize my device in 4.7 or 4.8. Please help.
do you have a stock image for the huawei ascend for cricket or does anyone here have it?
Unrooting......
I download the RECOVERY file you supplied (thank you)
"Blur_Version.0.3.9.MB300.Retail.en.03.zip"
If I reboot into Recovery and just flashed that zip file, would it work that way to unroot?
Provided you are flashing on a MOTOROLA BACKFLIP, yes. However, you might want to flash the AT&T 2.1 update for the backflip instead, if you reside in the US. Flashing back any official firmware unroots your phone
I'm looking to root and unlock my AT&F Motorola Backflip (MB300).. Any suggestions?
Sent from my NexusHD2 using Tapatalk
OTA for Samsung Galaxy Ace is a CFG file, not ZIP
Hello,
Just for interest, I received an OTA for my Samsung Galaxy Ace but it didn't come as a ZIP file - it came as a CFG file (which is not a ZIP, but actually a proprietary package - which I can't remember the name right now).
However, I did find the stock recovery elsewhere in this forum, and I installed it. But that wasn't enough for the OTA to be installed - it still fails.
Corrupted?
siidheesh said:
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Click to expand...
Click to collapse
I can't find it. I have an Alcatel Pop C1 4015X. Help?
Trying to unroot Xperia Z2
I am trying to unroot using update files from the Sony Xperia Companion. I found the update files (I think). I used Flashtool to decrypt the FILESET, but there is no recovery.img in the decrypted folder. The folder I decrypted is in Xperia Companion/Sony Mobile Update Engine/localstorage/db/13740270 and that is the only folder that has decryptable files. They are named FILE_8977018 and similar before decryption and various .sin .ta files (examples auto-boot.ta, cust-reset.ta, simlock.ta). Am I using the right decryption to get the recovery.img?
Related
Scroll to the bottom for a fix to the newest clockwork recovery flasher...
UPDATING TO DI07
First things first, you must update to the latest firmware and kernel, but in order to do this you must un-root and return to the stock kernel in order to avoid problems.
Simply download the zip here, and run the run.bat inside, after extracting the folder to your desktop.
You must have debugging mode enabled for this to work.
Once that's finished you can update to DI07 using the stock recovery. You do this, like any other update, by renaming the zip (found here, to update.zip on throwing it onto the root of your sdcard.
Then, boot up into the stock recovery (power+camera+volume down) and press home to apply the update.zip.
The update will install and your phone will reboot into DI07.
First boot will take some time, so be patient.
Now onto the fun part, rooting your phone.
OBTAINING ROOT
Just as you obtained root before DI07, you obtain root on DI07, if you have the right tools. Download the one click root here, and once more extract the included folder to you desktop, make sure you have usb debugging enabled, and run the run.bat. Your phone will reboot, and you will have root.
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip here, but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
That's it, three simple steps to updating, obtaining root, and flashing clockwork recovery!
Also, don't forget to check out my ROM coming later today, as well as noobnl's Andromeda Galaxy ROM v1, just released.
great tutorial...and i can use these instructions even if i am using aridons v4 rom and heros overclocked kernel?
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
bubby323 said:
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
Click to expand...
Click to collapse
Well I just ran this and at first glance, it got me right into clockwork. I selected one of my nandroid and restored it. After the phone finished restoring and everything, I wanted to make sure that I still had clockwork but instead it was stock recovery once more.
Since I still had root, I redid the steps starting with entering the commands, then I re-ran the bat file for clockwork. I checked and clockwork is back...unknown as to how long though.
Thank you!!! the remount rw was what I needed to get the clockwork custom recovery to flash!!!
I have another question for you? Is it possible to install the custom recovery without having root? I suspect not? The reason I ask is that I would like to have a nandroid backup of the completely stock rom although I guess I could use the one noobnl has posted
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
mrkrabs said:
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
Click to expand...
Click to collapse
Three options I can think of- if you use adb reboot recovery I believe it will load the stock recovery- the other option is to use odin to go back to complete stock. Finally you could use the option for clockwork in this thread look for the link under "B]Update.zip (for clockwork recovery and includes all the listed apps below)"
EDIT: I can confirm that "adb reboot recovery" loads the stock recovery when you have clockwork
bubby323 said:
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip --- but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
Click to expand...
Click to collapse
Im having a little issue with this. Im running windows 7. Can I do this in windows 7? Also when it says redirect it to your C:/Android---- do I have to change the drive to ex. cd c:/ first or do i just type in the command prompt C:/android-sdk-windows/tools and hit enter and follow the rest of the commands? Sorry extreme noob here..
Thank you for any help!!
I have ClockworkMod Recovery installed, how can I get into the stock recovery to apply this?
Look 2 posts up
Sent from my SPH-D700 using XDA APP
You need to use the DG27 uninstaller instead of the DI07 uninstaller to update to DI07.
The DI07 uninstaller is just to go back to stock DI07 kernel if you already updated
DG27 uninstaller: http://www.sdx-downloads.com/devs/noobnl/one.click.stock.&.root.uninstallerv1.0.1.zip
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Thanks a lot, I appreciate step-by-step tutorials like this for noobs like myself ... this made things a lot easier since some of the stuff (files, instructions, etc.) was all over the place.
would seem that way because I removed the alarmclock to start and when i try to run update.zip from sd it fails when checking current system @ /system/app/AlarmClock.odex
i tried rerooting and reinstalling alarm clock using the backup from titanium. says it is successful but i do not find it in my apps drawer. it still fails there too..
WisdomWolf said:
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Click to expand...
Click to collapse
Titanium backup does not restore apps in /system. You have to restore those by hand.
Im officially struggling, undid the root then copy/paste the update to the sdcard, renamed it. It unzips but says its failed to open /sdcard/update.zip(no such file or directory)...suggestions?
I know that in the step it said to copy it to the root on the sd but im am very green to this stuff, and didnt see a folder marked that, therefore I just copied it to the sd card
I can't get Clockwork to flash now. I walked through the steps...I did the remount crap and ran the bat and it rebooted the phone but when i reboot into recovery it goes to the normal recovery screen. Now if I try to redo it it does not recognize the remount rw and i can't get anywhere with it and i'm stuck with no clockwork.
but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Click to expand...
Click to collapse
This part is unnecessary because the recovery zip comes with adb built in
is there a manual way to push this to the phone? These one clicks never seem to work for me ever it's just easier to do it myself.
Whosdaman said:
This part is unnecessary because the recovery zip comes with adb built in
Click to expand...
Click to collapse
No you must do this in order to get clockwork.
Rooted my Transform and went in to the superuser APK.... I'm disappointed that it has very limited content vs. my buddies HTC EVO. I'm new to Androids, but anyone know if there would be a way to port the superuser APK from the HTC EVO to the Samsung Transfrom, or is it even Feasible?
Can you go into more detail on how you rooted your Samsung Transform. I have tried SuperOneClick but the root never sticks. I would lose superuser randomly.
I just rooted with Super One Click, now, i dont know what to do with it lol. It sticks with me though.
No need for a superuser port. Just download from the market after rooting
via skeeterslint sdx:
Heres is a one click recovery installer for people that don't want to do it by hand.
http://www.mediafire.com/?jl21knp1d0lbf17
This is a still beta but working version of SDX Recovery version 3.1.1.
Things known to work.
Backups and restores.
Clearing dalvik cache.
Clearing cache partition.
Flashing kernel zImages.
Flashing zip files.
Adb works in recovery.
Also mounting the sdcard to your computer works.
Anything else in the options is still in need of testing I am not responsible if your phone gets bricked.
THIS MAY BRICK ALL PHONE MODS YOU DO AT YOUR OWN RISK!
OK now that thats out of the way heres the files needed.
1. http://www.mediafire.com/?862j3wlzftenwef This is the recovery image.
2. http://www.mediafire.com/?67an7lkm9qtmf5b until there is a custom recovery you will need this program to flash recovery. Its called flash_image.
3. http://www.mediafire.com/?5dcv3r14sjvsfdq rage.bin temporary exploit to get root.
4. You will also need the Android SDK so you have a working adb to be able to push files over to your phone.
If you are flashing this from a phone running my rooted kernel you can skip steps 4 and 7 and just su over to a root prompt.
OK these are the steps to install this recovery.
1. Make sure adb is installed and working there are how to's on the forum to get this setup or just use google.
2 adb push recovery.bin /data/local/tmp to move the kernel to the phone.
3 adb push flash_image /data/local/tmp to move flash_image onto the phone.
4 adb push rage.bin /data/local/tmp to move rage.bin onto the phone.
5. Run adb shell to get to a shell prompt on the phone.
6. Run chmod 755 on flash_image and rage.bin chmod 755 rage.bin chmod 755 flash_image.
7. Run ./rage.bin and let it go run through untill it exits you out of adb.
8. adb shell you should now have a root shell on the phone.
9. Run ./flash_image recovery recovery.bin to install the kernel.
Once its installed to get into recovery use Volume down Camera and power to get into recovery.
Volume up and down scroll through the option.
Menu should be the enter key.
Back button is back.
Search key is delete.
You will need to create the directorys on your sdcard that recovery needs to flash zip files make backup and flash kernel and recovery from.
Create directory called sdx on the root of the sdcard and inside it create 3 folders zips update and backup.
At this time it seems that factory restore is not working correctly and anyone else can confirm please let me know.
And for better recovery via vampirefo on sdx:
his is my first recovery, I made the change to the first screen to show that this is a transform recovery rather than a moment recovery. Also I got console to work in recovery, it wont rotate but works just fine.
http://www.4shared.com/file/bBTlN7UZ/recoveryrfs.html
You can flash this via swupdate, or if you already have skeeters recovery installed, just extract recovery.tar to /sdcard/sdx/updates
boot to recovery
Scroll down to
Backup, Restore, Flash
Scroll down to
Flash Recovery
After flash is complete
press back button
Under Reboot options choose Reboot to Recovery to see new recovery
Call me what ever you want, but it's too late...
I have a US WiFi Zoom and I accidentally deleted the "framework-res.apk" in /system/framework/, but I do have a backup in /mnt/sdcard/
Fastboot is still working, but I can no longer boot in recovery (I have/had CWM installed).
The normal startup get stuck on the boot screen.
As far as I understand you cannot flash a file directly from fastboot, but need a .zip file made in Linux for this purpose.
As I do not have skills, nor a Linux OS to build this, I would very much appreciate if someone could help out here, or direct me how to flash a file directly from fastboot.
Thanks in advance,
arc
Get wifi system image and fastboot flash system system.img
Or if you have USB debugging enabled, just use adb to copy the framework-res
Thanks, sangreal06,
I believe the USB debugging is only getting me into the /mnt/ folder.
But, if I understand you right, I can grab roebeet's root-prepped and updated HRI66 system.img here:
http://forum.xda-developers.com/showthread.php?t=995785
and flash it by:
Code:
fastboot flash system system.hri66.rootprepped.img
fastboot reboot
After the device reboot, you will need adb to fix su permissions:
Code:
adb remount
adb shell chmod 6755 /system/bin/su
is this correct?
Yes, but that file is for 3G. It is not compatible with wifi model
Thanks, sangreal06, for catching that one, it probably saved me a lot of grief. I guess the one to use will be Scourge1024's:
Stock MZ604 (Xoom Wi-Fi) recovery.img
or, am I better way of waiting for the stock SBF, announced to arrive within short?
Also, will this require that I re-root?
Thanks in advance,
arc
Boot into clockworkmod and flash the zip below.
How to get back into recovery: http://forum.xda-developers.com/showthread.php?t=1041192
File: http://dl.dropbox.com/u/18315605/XDA/Framework.zip
Thanks so much bwcorvus,
I'll d/l the recovery.img at [RECOVERY] ClockworkMod Recovery v3.0.2.5
and....
It worked perfectly, I'm back! I guess that's a mistake I wont do again. I really owe you one, put it on my tab.
arc
Hello,
I am stuck with rooting process. I tried rooting, unrooting before but this time, for some odd reason. I am unable to proceed
I followed this procedure from unlockr website to root the nexus S. Could not post the exact link because of restrictions
Phone is unlocked , USB debugging is ON. ADB mode is working, I can use other commands. But its giving me the following error on step 6 . Line 3
Mount : Operation Not permitted
Attaching image !
When I boot using volume up & Power button and go to Recovery, It gives me exclamation mark & Android Sign... So I cant unroot it either.
I always tried to unroot so I can go back to original state and restart the process. If I flash through recovery.img I can go into recovery but after few steps, I am stuck
Yeah that's normal. The mount command requires root permission (which you don't have yet)
Generally what you have to do after flashing the (right version of) custom recovery is:
copy the su.zip to your SD card
reboot into custom recovery
choose apply zip from SD card and select the su.zip
reboot
That's it.
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Then it sounds like your recovery reverted back to stock. Did you rename the .sh file that rewrites the recovery on reboot? If not, do that using root explorer or any other method you find in the guide. Then flash the recovery again and it will stick.
Sent from my Nexus S using Tapatalk
No I didnot renamed. I was just following the process. I tried to unroot but cant do it either. I am stuck
ahaseeb said:
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Click to expand...
Click to collapse
If su is installed correctly then for the "Mount : Operation Not permitted" problem, you just have to type su in adb shell (there may be a Superuser permission popup on the phone, just allow it) -- the prompt should change from $ to #, which means you are now root. After that the mount command should work.
To make custom recovery stick on every boot, rename /system/etc/install-recovery.sh to other name e.g. install-recovery.sh.disabled
When I typed su it said Permission denied !
Just because you have superuser in your app drawer does not mean you're rooted. You can downloaded from the market on any phone/rom.
You are not rooted.
Flash custom recovery via fastboot
Boot directly into recovery etc.
ahaseeb said:
When I typed su it said Permission denied !
Click to expand...
Click to collapse
Then I suggest you re-install Superuser from Android Market. Normally it shouldn't just say permission denied, there should be a Superuser popup asking for permission.
Or better, try to redo everything following this guide instead.
Again YOU HAVE TO FLASH SU FROM CUSTOM RECOVERY.
Do not install from market. Hell don't even boot up the OS. Flash recovery. Boot directly into recovery and flash su.zip from your phones internal storage/sdcsrd in recovery. The you're rooted.
Now you can update delete/rename the script to make the custom recovery stick. Update su in market or whatever else you want to do.
.
I believe i got it fixed. When ever the phone used to boot after installation of SU, dialogue box to ask for unlock. That dialogue box disappear very quickly. It took me time to figure it out. Thanks, I guess I am good now.
Thanks every one
Hi.. I installed ICS on my Tab but i receive an wifi error... disconnect unexpectly... After factory reset I tried to instal again ICS stock using Odin but won't boot... My tab is using root... Please help my... I can't use my tab and i'm dead
Catalinq said:
Hi.. I installed ICS on my Tab but i receive an wifi error... disconnect unexpectly... After factory reset I tried to instal again ICS stock using Odin but won't boot... My tab is using root... Please help my... I can't use my tab and i'm dead
Click to expand...
Click to collapse
If you are stuck on the splash screen, the first thing to try is to wipe the cache and dalvik-cache from the recovery menu. A full wipe may also be required, although I would not recommend it until you try the suggestions below.
Use ADB (first install SDK)
HTML:
adb devices
HTML:
adb reboot
P6200
Doesn't start...What to do? I tried to instal a custon rom but same problem... Logo image appear and dead. I can acces download mode and CM6... How to fix this ugly problem?? Thanks
Catalinq said:
Doesn't start...What to do? I tried to instal a custon rom but same problem... Logo image appear and dead. I can acces download mode and CM6... How to fix this ugly problem?? Thanks
Click to expand...
Click to collapse
Bootloops are mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.*To find the cause of a bootloop you have to think about what you did before getting the bootloop.Choose one of the following reasons that caused the bootloop for you and try out its solution.- After flashing a new rom*If you flash a new (base)rom with odin your /data will be kept. This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:1. Start your phone in CWM Recovery2. Go to Advanced3. Choose "Wipe dalvik-cache"4. Now go to "Mounts & Storage"5. Choose "Wipe /cache"6. Reboot your phoneif the problems still exists after doing that and you're sure it's not related to the rom, then you need to do this:1. Start your phone in CWM Recovery2. Now go to "Mounts & Storage"3. Choose "Wipe /data"4. Choose "Wipe /cache"5. Reboot your phone.
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the samsung logo.*The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is just after the Galaxy logo, so just when the bootanimation starts. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
Using the original cwm zip is the easiest way, since the zip is already created for you, you only need to replace the files with the original rom files. You can get those files from the deodex packages for baseroms which are posted on the forums. If you are using an odexed ROM, you can get your files from system.img.ext4 (open the baserom: *.tar.md5 with Winrar and extract system.img.ext4)Now you can open system.img.ext4 with "DiskInternals Linux Reader". browse to the app/framework directory and extract the needed files from the image file.Once you got the same files as present in the original CWM zip you can easily drag em into the archive, then choose "store" as compression level. Now finally you need to put it on your sdcard and install it.If you don't have an external sdcard or you can't reach your internal sdcard (which is very likely when you have a bootloop), you can use ADB to push the zip to your phone, read about how to use ADB ..
HTML:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb push mycwmfix.zip /sdcard/mycwmfix.zip
adb reboot recovery
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made.
screen
Screen here
Catalinq said:
Screen here
Click to expand...
Click to collapse
How to fix it?
tab 2
Catalinq said:
How to fix it?
Click to expand...
Click to collapse
we have the same problem did u fix ung tab can u share with me thanks