In which directory should i be in to execute the command .... adb sideload (filename.zip)
and which file should i include in the command prompt as the zip file ?? please help me
thanks nexus
Related
Can someone with an S-on unrooted phone please create a file in the root of the sdcard called cw.prop containing the following line
Code:
persist.service.adb.enable=1
then reboot into recovery and try to access the phone via adb. I am exploring the OTA update recovery and /init.rc contains the code to enable adb while /sbin/recovery has a reference to the above file.
PS: if that fails please do the same with /data/cw.prop and /cache/cw.prop
Hi guys, I have a problem.
I'd like to downgrade my Desire S (2.3.5) from hboot 2.00.0002 to 0.98.00000
I connected the phone to pc with USB debug enabled and fastboot mode disabled.
I added adb command following the guide: extracted the folder android-tools in C: than added the string ";C:\android-tools" in: properties -> system -> Advanced system settings -> System Variables -> path
If I launch cmd and type the first command:
adb push zergRush /data/local/tmp
it says:
*daemon not running. starting it now on port 5037*
*daemon started succesfully*
cannot stat 'zergRush': No such file or directory
Than second command and it seems ok.
Third command:
adb shell chmod 777 /data/local/tmp/zergRush
and it says:
unable to chmod /data/local/tmp/zergRush: No such file or directory
I don't think is right...
I use Windows 7 pro 64 bit. I have these file in android-tools:
1) adb
2) AdbWinApi.dll
3) AdbWinUsbApi.dll
4) fastboot
I extracted the two zip file in a folder that I called "downgrade" and putted in C:
There are only files in it, no subfolders. I have:
1) gopt.c
2) gopt.h
3) LICENSE
4) misc_version
5) misc_version.c
6) zergRush.c
I really don't know what to do...
Thank you guys !!!
When enter cmd type "cd ..." (" " don't type, ... stands for directory where zergRush is located), and then keep typing in terminal what you should.
Sorry, I didn't write.... however, I was already doing in that way. I used cd to go in C:\downgrade
Paino101989 said:
6) zergRush.c
!
Click to expand...
Click to collapse
Your adb setup is correct but this is the source code file of zergRush
You need the binary (executable) to do the trick
Follow this guide carefully and you will make it
YEP! I did it! Yes, that was the mistake... But following the link of that guide (I was using that too) I can download only the source code file. I think...
I solved using the zergRush file inside the folder I downloaded from the post 34 in this topic: http://forum.xda-developers.com/showthread.php?t=1443636&page=4
Now I'm ready for revolutionary (I'll cross fingers)
Thanks !!!
hiii
u shud have following files as my screenshot...and try it will work
I moved the 'framework-res.apk' file to sd card and reboot the phone. After that it shows only a black screen while booting. How can I replace or restore the framework-res.apk file from sd card to phone? Please help me..... I installed the android SDK in my w7 PC. Is it possible to use ADB from android SDK to solve the issue? If possible, please describe here how to do that......
Yes.
Put framework in tools folder of android-sdk, then using dos prompt navigate to the tools folder.
Boot into cwm (I am presuming you have it installed) and mount the system partition and do
adb remount
adb push framework-res.apk /system/framework / framework-res.apk
Reboot and all should be well.
Why did you do it in the first place it's an essential file as you can see.
Just type adb at prompt for more help on it.
Not sure what happened during a ROM flashing, however, all in all, I can only boot my phone into Bootloader and recovery...nothing else, it says *error mounting /sdcard*So I can't restore or flash a previous backed up ROM. So I guess it would be called a soft brick. Any way of getting out of this? I tried to adb push, doesn't work. Tried the All in One kit, still nothing.
For anyone who can help me with my phone, I will compensate you for your time and knowledge.
If all else fails, I will just have to call and have the phone replaced.
Thanks in advance.
dont panic try this http://forum.xda-developers.com/showthread.php?t=1630459
I got as far as being able to mount my sdcard, now I can't push any files on to my phone?
put the rom in your adb folder, Use the command
adb push nameofrom.zip /sdcard
then in CWM it should appear
Check here for a full guide http://forum.xda-developers.com/showthread.php?t=1667929
C:\androidsdk\tools>adb push ROM.zip /sdcard/ROM.zip
cannot stat 'ROM.zip': No such file or directory
This is what it says when I try to push the ROM
and the rom is in the tools folder ?
you also naming it right ?
don't add the rom.zip after sdcard
i think that means you are pushing it to a rom.zip folder already on card--not 100% sure though
Thongvilay said:
C:\androidsdk\tools>adb push ROM.zip /sdcard/ROM.zip
cannot stat 'ROM.zip': No such file or directory
This is what it says when I try to push the ROM
Click to expand...
Click to collapse
Could also be you're not typing the path to the file correctly.
Do this, on your PC navigate to the folder where you have the ROM.zip file (in your case the tools folder in androidsdk.
Hold down the SHIFT button while right clicking on the "tools" folder
A drop down menu will appear and chose "Open Command window here"
You should get a CMD window with the correct path.
Also for me it's always "platform-tools" folder that I put my file to be push in.
hey BBF nice to see still around--loving my 1s
sorry for off-topic guys
There is a new downgrade option released for firmware 1.36.970.1 to 1.15.970.1.
However my Japanese is not perfect and my understanding of hacking is very weak.
If there is someone more in the know could understand what the steps to take are that would be great.
Good luck all. I hope someone can make a guide as well to help other out.
I'll try my best as well.
Here is the link.
http://htcsoku.info/htcsokudev-news/au-deluxe-136to115-downgrade/
link to RUU 1.15.970.1 is dead
I have successfully downgraded my J Butterfly based on those instructions. I have simplified it because the original instructions seems to be overly complicated. It involved tricking a system app with root privileges to run an custom command, only to use run_root_shell later anyway.
I also did not use the run_root_shell supplied by the guide, instead I compiled a newer version direct from the source: https://github.com/android-rooting-tools/android_run_root_shell
You'll need
1. revone.dna-0.2.1
http://forum.xda-developers.com/showthread.php?t=2314582
2. A newer build of run_root_shell (attached)
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
https://mega.co.nz/#!jQtQ0BLS!279lf8k4sbKPTmWHTsPg6hbaGDatpq3xGGv4aE8N1h4
4. firmware.zip extracted from OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip:
http://kie.nu/1urK
5. adb and fastboot
6. An HEX editor such as XVI32
THIS WILL WIPE YOUR USER DATA, BACKUP ALL YOUR STUFF FIRST
Steps:
1. Run the following commands in command prompt to push files required by run_root_shell to device:
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
2. Run in command prompt:
adb shell
to access the shell on your device. Run the following commands to run run_root_shell, disregard messages about HTL21 not supported. You will be returned to the command line but with a hash (#) instead of a dollar sign, that means you have temprooted.
cd /data/local/tmp/
chmod 755 *
./run_root_shell
3. Run these commands on device shell:
chmod 666 /dev/msm_acdb
dd if=/dev/block/mmcblk0p21 of=/sdcard/p21
4. Run in another command prompt:
adb pull /sdcard/p21
to pull the file p21 from device, then open it with an HEX editor. Refer to the images on the original Japanese tutorial, change the version number near "ClearAutoImage" to 1.00.000.0 and save the file as p21mod.
5. Push the modified file back to the device by running in command prompt:
adb push p21mod /sdcard/p21mod
6. Back to the device shell, run these commands to write the modifications to the device and reboot into bootloader.
dd if=/sdcard/p21mod of=/dev/block/mmcblk0p21
reboot bootloader
7. Run in command prompt:
fastboot oem rebootRUU
to boot to RUU.
8. Run in command prompt:
fastboot flash zip firmware.zip
and it willl fail with this error: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
9. Run in command prompt:
fastboot flash zip rom.zip
to flash 1.15 ROM. It should take around 6 minutes. This wipes your user data.
10. In command prompt, push run_root_shell to device again. Also push revone.dna-0.2.1 to device.
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
adb push revone.dna-0.2.1 /data/local/tmp/revone.dna
11. Refer to step 2 to temproot again.
12. Run revone.dna on device shell:
./revone.dna -P
and you should see "revone successful - please reboot to continue".
13. Reboot and repeat step 12 again, this time you should see "revone successful - no need to reboot".
14. Run on device shell:
./revone.dna -s 0 -u
and you should see "revone successful".
15. ???
16. PROFIT!
You have now successfully S-OFFed and may proceed to unlocking and SuperCIDing your device as usual.
Corrupted
Phil_123 said:
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
.
Click to expand...
Click to collapse
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?
corrupted
darky4e said:
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?
Click to expand...
Click to collapse
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.
darky4e said:
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.
Click to expand...
Click to collapse
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK
Phil_123 said:
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK
Click to expand...
Click to collapse
Thank you very much! I have succesfully downgraded the phone! Thx for the instructions again!!
run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?
dfani511 said:
run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?
Click to expand...
Click to collapse
This method can only be used for the software version of the 1.36.970.1, I think your software version 1.39.970.1 is not SOFF
i have 1.39.970.3 ?????????????
OTA ??????????
Nice share, im succesfully unlock soff with this way
Sent from my MITO_A10 using XDA Free mobile app
"htl21 1399703 firmware" I want up because it cannot find the file.