Moderator note: Please feel very free to move this thread to a more appropriate forum. Thanks -- kmdm
Let's correlate the failures and try to find out what's going on.
You must be using revone v0.2.1
If revone fails for you, please detail the following information (don't clutter this thread or I simply won't bother looking through it ).
revone error code / description / sympton
Your CID (fastboot getvar cid)
Your HBOOT version (fastboot getvar version-bootloader
Your software version (fastboot getvar version-main)
Your kernel version (adb shell uname -r)
If revone fails with error code (-1), the output of running this immediately after that: ./revone -P
Please feel free to include anything else that is obviously relevant but missing from the list.
(You may also post if you create and maintain a google docs spreadsheet of the information )
Thanks,
- kmdm
Hello, I am getting error code -1. Below is all my information. Also attached is the screenshot of the whole process:
CID : H3G__001
HBOOT : 1.44.0000
Software : 1.28.771.6
Kernel :3.4.10-gddcfb8c [email protected]#1 SMP PREEMPT
The output after running the -P command can be seen on the screenshot.
EDIT!!!
I just followed the very same instructions described by wideopen4ever and it worked for me too. I've been trying all day and on after the specific sequence with rebooting in that order worked for me!!!
revone failed (error code = -1)
cid: HTC__001
version-bootloader: 1.44.0000
version-main:
3.4.10-CM-g616ab68
revone successful - no need to reboot.
CID : HTC__622
HBOOT : 1.44.0000
Software : 1.29.708.4
Kernel :3.4.10-ge503309
./revone -s 0 -u
revone failed (error code = -1)
./revone -P
revone successful - no need to reboot
Flinny said:
revone failed (error code = -1)
cid: HTC__001
version-bootloader: 1.44.0000
version-main:
3.4.10-CM-g616ab68
revone successful - no need to reboot.
Click to expand...
Click to collapse
Have you guys tried to reboot after running the "revone - P" command. I notice that it said no need to reboot in cmd but revone instructions said you should reboot before running "revone -s 0 -u"
Sent from my HTC One using xda app-developers app
CID:H3G__001HBOOT:1.44.0000Software Version:1.28.771.6Kernel version:3.4.10
Code:
C:\sdk\platform-tools>adb push revone /data/local/tmp/
2851 KB/s (648208 bytes in 0.222s)
C:\sdk\platform-tools>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $
Hello.
thanks DLX support revone.
I use temproot M7_WLJ (HTC J One) revone.
>adb push revone /data/local/tmp/
>adb shell chmod 755 /datalocal/tmp/revone
>adb shell
$ ~~~~~temproot~~~~
# cd /data/local/tmp
# ./revone -P
>
...M7_WLJ is without permission reboot.
M7_WLJ info
CID:KDDI_801
HBOOT version : 1.52.0000
software : 1.05.970.1
kernel version : 3.4.10
thanks
failure on preparation step : ./revone-0.2.1 -P ==> "[-] Failed to map memory."...
After repeating "-P" command, the step succeed, but when I try "s-off & Unlock" step, I get error code -1.
I tried "-s 0 -u" commands, without reboot AND with Reboot, but same result...
A part of my cmd prompt :
Code:
251|[email protected]:/data/local/tmp $ ./revone-0.2.1 -P
./revone-0.2.1 -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $ ./revone-0.2.1 -P
./revone-0.2.1 -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone-0.2.1 -s 0 -u
./revone-0.2.1 -s 0 -u
revone v0.2.1
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
CID = ORANG202
HBOOT version = 1.44.0000
version-main = 1.28.73.7
kernel version = 3.4.10-gddcfb8c [email protected]#1 SMP PREEMPT
IMPORTANT EDIT :
VICTORYYYYYYYYYY !!!!!........ between each steps with success, I reboot phone with Power off button for 15seconds (soft-reset I think)...
@ kmdm and all the Revolutionary Team ; Thanks again for the good work ......
CID: HTC_044
version bootloader: 1.44.0000
version main: 1.29.707.17
kernel: 3.4.10-g4919859
./revone -s 0 -u
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
./revone -P
revone failed (error code = 2)
CID : VODAP110
HBOOT : 1.44.0000
Software : 1.29.708.4
Kernel :3.4.10-ge503309
revone successful
Here are a few things I learned after getting a some failures...
1. Update to the latest RUU availiable specificly for your variation
2. Unlock your bootloader
3. Flash recovery
4. Root (don't rely on revone built in root)
5. Disable Fast Boot in Power settings
6. Fully power down, boot back up
7. Run revone with su ( ex: su ./revone -P )
After that I have had no problems with the 10 or so I have done.
Thread closed on OP's request.
Any issues please report in the original thread
Related
Trying to downgrade...
C:\Program Files (x86)\Android\android-sdk\platform-tools>crackin.bat
"Copying tools"
cannot stat 'busybox': No such file or directory
cannot stat 'flash_image': No such file or directory
cannot stat 'misc1-2.img': No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/flash_image: No such file or directory
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
/data/local/busybox: not found
/data/local/flash_image: not found
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
PATH: C:\Program Files (x86)\Android\android-sdk\tools
Copied the hack4legend files to C:\Program Files (x86)\Android\android-sdk\platform-tools & C:\Program Files (x86)\Android\android-sdk\tools
Following this guide:
http://forum.xda-developers.com/showthread.php?t=725430
You have your adb and crackin.bat in the folder " /android-sdk/platform-tools"
And it looks like the other files (line 3 - 5) are in another folder.
Assuming you followed the instructions exactly, you probably extracted those files into "/android-sdk/tools"?
If so, just copy all files from "/android-sdk/platform-tools" to "/android-sdk/tools" and it should work.
Also, do i need to root HBOOT first?
New error:
C:\Program Files (x86)\Android\android-sdk\tools>crackin.bat
"Copying tools"
1364 KB/s (698452 bytes in 0.500s)
608 KB/s (76044 bytes in 0.122s)
1438 KB/s (655360 bytes in 0.445s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Mar 9 14:13 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
After that you should be able to run the 1.31 RUU
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# adb push flash_image /data/local/
adb push flash_image /data/local/
adb: not found
#
Edit:
Is this what suppose to happen?
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
# /data/local/flash_image misc /data/local/misc1-2.img
/data/local/flash_image misc /data/local/misc1-2.img
#
kmtse1 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# adb push flash_image /data/local/
adb push flash_image /data/local/
adb: not found
#
Edit:
Is this what suppose to happen?
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
# /data/local/flash_image misc /data/local/misc1-2.img
/data/local/flash_image misc /data/local/misc1-2.img
#
Click to expand...
Click to collapse
From what I remember, yes it is.
You can now continue the guide in your first post from the point where you have to insert your gold card into your phone.
Still the same errors...
kmtse1 said:
Still the same errors...
Click to expand...
Click to collapse
Which errors?
The errors you posted in your first post were from running crackin.bat.
That is not necessary after running the steps I posted.
You can skip to the part where you insert your goldcard into your phone and then run the 1.31 RUU.
I get stuck at step 6 http://theunlockr.com/2010/06/07/how-to-load-a-custom-rom-on-the-htc-legend/
No menus load.
So if I understand correctly, you have now already succesfully downgraded (Link as in your first post) and rooted (Link)your phone? Since the link you gave in your last post is for flashing a custom rom, which is the last step in the process.
Oops, no, not downgraded yet - I lost my patience, I will try properly again.
Azaruc said:
So if I understand correctly, you have now already succesfully downgraded (Link as in your first post) and rooted (Link)your phone? Since the link you gave in your last post is for flashing a custom rom, which is the last step in the process.
Click to expand...
Click to collapse
How do I install the RUU to downgrade? I get an error if I run the .exe on my laptop.
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
@Windows 7 / Server 2008 R2 Service Pack 1 (7601)
IE Version: 8.0.7601.17514
Have you installed HTC Sync v2.0.33 ?
Download here
You need this version of HTC Sync, so if you have a newer version, uninstall that version first.
Once installed, run the RUU again (you might need to run it as admin).
Azaruc said:
Have you installed HTC Sync v2.0.33 ?
Download here
You need this version of HTC Sync, so if you have a newer version, uninstall that version first.
Once installed, run the RUU again (you might need to run it as admin).
Click to expand...
Click to collapse
Yes I have that specific version.
Tried run as admin.
Just to be sure, you still have your phone connected in charge only state right?
If so, are you sure you didn't get any error in the earlier steps?
I downgraded using the exact same method and didn't get this error (recognized all of the others), so I'm not sure what might cause this otherwise.
Azaruc said:
Just to be sure, you still have your phone connected in charge only state right?
If so, are you sure you didn't get any error in the earlier steps?
I downgraded using the exact same method and didn't get this error (recognized all of the others), so I'm not sure what might cause this otherwise.
Click to expand...
Click to collapse
I showed you what I got from following your steps earlier. You said it looked ok, then I went to downgrade with the RUU.
Is the RUU compatible with 64bit Windows 7?
Looking at your other post, it looks like you managed to complete the downgrading?
What turned out to be the problem with the second step?
Azaruc said:
Looking at your other post, it looks like you managed to complete the downgrading?
What turned out to be the problem with the second step?
Click to expand...
Click to collapse
The downgrade guide doesn't work for me - I followed this instead: http://android.modaco.com/content/h...-r4-htc-legend-rooting-guide-now-with-1-31-x/
But now, I still can't delete widgets/apps. http://forum.xda-developers.com/showthread.php?t=987023
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
After that you should be able to run the 1.31 RUU
Click to expand...
Click to collapse
Mate, just wanted to let you know I was having the exact same issues under Win7 x64 and after trying your Visionary+ and manually executing adb commands method, I was able to run RUU successfully.
My Legend is now 1.3.1 and Im performing the root as I type.
Thanks for your help and contritubtion.
Error 170: Usb connection error
Tried to downgrade many time using guides on the forum but when running RUU always get:
ERROR 170: USB CONNECTION ERROR
- downloaded the drivers with HTC SYNC (phone shows up at device manager)
- made the gold card (with two different cards 2GB Kingston, 8GB SanDisc)
- ran ADB ended up with: cr--rw----
- did a temproot, ran adb shell .... su and so on
but still get:
ERROR 170: USB CONNECTION ERROR
Have no clue what to do now whatsoever. Any suggestions?
I'm using CM 7.2 latest, already done partition of sd card by minitool partition (Ext4)
when i type a2sd data in terminal emulation it shows this error message, please reply me as soon as possible what this problem is all about & how can I solve it..
$ export PATH=/data/local/bin:$PATH
$ a2sd datasd
/system/bin/a2sd: line 61: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 65: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 66: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 67: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 68: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 69: /data/dta2sd.log: Permission denied
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
grep: /init.rc: Permission denied
/system/bin/launcha2sd: line 296: /data/.lmdefault: Permission denied
/system/bin/launcha2sd: line 297: /data/.lmdefault: Permission denied
tee: /data/dta2sd.log: Permission denied
__ _____
tee: /data/dta2sd.log: Permission denied
| \ |
tee: /data/dta2sd.log: Permission denied
| | |
tee: /data/dta2sd.log: Permission denied
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 1: Check for SD Card Fix and Implement.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 4: Determine Mount Point.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 5: Set Parameter Variables.
/system/bin/launcha2sd: line 373: /data/dta2sd.log: Permission denied
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 6: Insert CyanogenMod patch.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 8: Resetting Dalvik Cache Partition
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 10: Checking for existence of command parameter
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 11: Check for a2sd help command
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 12: Check for a2sd check command
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 13: Display version information.
/system/bin/launcha2sd: line 538: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 14: Check for filesystem support.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 15: Mount partition.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 17: Mount Swap.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to: 48m
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
tee: /data/dta2sd.log: Permission denied
[ ] Launching Apps2SD Start Program with datasd
/system/bin/launcha2sd: line 820: /data/dta2sd.log: Permission denied
/system/bin/starta2sd: line 18: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD in datasd mode
/system/bin/starta2sd: line 61: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[X] No partition available. Data move not available
/system/bin/starta2sd: line 114: /data/.nodata: Permission denied
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[ ] Setting File System Ready property to 1.
/system/bin/starta2sd: line 1211: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 822: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 71: /data/dta2sd.log: Permission denied
Did you use the command as su or not?
It should be:
Code:
$su [ENTER]
#a2sd data [ENTER]
That's exactly how it will look in terminal. Obviously don't type the dollar or pound signs and [ENTER] just means hit enter.
Edit: Just noticed the '$' in your command there. You need to run the 'a2sd data' command as su. So follow the steps I typed above and you should be as happy as a monkey with a fresh pile of poo.
Thank for your help....
Dear thank you very very much for your help,
I'm beginner so please guide me some more, I just want to transfer my apps in SD card by using a2sd that's it. I've already partitioned my SD card from fat32 to EXT4 by using "mini tools partition wizard" now I'm having FAT32 partition & EXT4 partition in my sdcard.
I can't see EXT4 partition in my samsung galaxy gio but only can see FAT32(showing 1.2 GB) but rest of 600 MB for EXT4 is not been shown.
AFTER USING YOUR INSTRUCTIONS, I GOT THIS MESSAGE...
$ export PATH=/data/local/bin:$PATH
$ su
# a2sd data
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[-] Checkpoint 6: Insert CyanogenMod patch.
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[-] Checkpoint 13: Display version information.
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
[-] Checkpoint 14: Check for filesystem support.
[-] Checkpoint 15: Mount partition.
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
[-] Checkpoint 17: Mount Swap.
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to: 48m
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
[ ] Launching Apps2SD Start Program with data
[ ] Starting Darktremor Apps2SD in data mode
[X] Invalid command: data
[ ] Setting File System Ready property to 1.
#
now tell me what should I do to transfer my apps to SD card EXT4 partition that is hidden even I have tried titanium backup, still can't see my 600 MB
Well your apps data is on the ext partition.
Now try this command:
Code:
$ su [ENTER]
# /system/bin/a2sd reinstall [ENTER]
Your phone should reboot.
Now go back into terminal and type in this:
Code:
$ su [ENTER]
# /system/bin/a2sd cachesd [ENTER]
Again your phone will reboot. You should have a lot more space on your phones internal memory now. You're done.
If you want to check all this and have a GIU to control it with use THIS app.
One thing you'll notice is that it still looks like the apps are on in the internal memory - they're not. You can check that using Titanium Backup or that app I linked you too. You'll notice the internal memory has a lot more free space and the ext partition should be listed.
Waoooo!!!!!
Thank you very very much for your halp....
now I'm having free memory in internal memory, before reading your this comment I watch a video "how to partition sd card" so I partitioned my SDCARD again (don't know CWM partitioned it in EXT3 or EXT4 format as far I know EXT4 is fast) by using Clockworkrecovery to 500MB & there was also an option of SWAP partiton (didn't any idea what it's about) & I partitioned it to 64MB..
after that I got your message, did what you say & it has done well, now a2sdgui showing that apps are in SD card & delvik cache is in sd card as well
but dear tell me one more thing I've check by titanium backup the "google app" like google mail, youtube etc... are still in SD CARD I though this a2sd will transfer all these apps to SD Card's EXT partition??
By the way thank you very very much indeed for helping me
You're welcome!
For those apps go into settings>applications. There should be a tab at the top that will list what apps are on the sdcard. Click on that and check find those apps, make sure they're not check marked or selected. If they are, simply unselect them and they will be moved to the 'internal' memory (your phone thinks the ext partition is part of the internal memory basically). There are 2 types of a2sd, Google's version and the one you're using. They work very differently and those couple apps you mentioned are using Google's version.
Hopefully that helps. PM me if you have any other questions or just post them in this thread.
now I got some idea when you said (your phone think it's internal memory)
thumbs up for you & definitely if there will be any problem, i'll PM you within no time
Thanks for making me happy
Welcome to Facepalm S-Off for the Droid Incredible 4G LTE.
Credits and terms:
Exploit by beaups. Full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - Donate to beaups
jcase - Donate to jcase
dsb9938 - Donate to dsb9938
dr_drache - Donate to dr_drache
Thanks also to mdmower for commissioning Facepalm for this device, and testing.
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
Droid Incredible 4G LTE SuperCID: http://forum.xda-developers.com/showthread.php?t=2214653
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
1.) Download patcher and unzip it in your working directory:
soffbin3.zip
2.) Download the RUU zip below:
http://d-h.st/MOw
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip 2.17.605.2_rom.zip
After 2-3 minutes, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell
su
/data/local/tmp/soffbin3
exit
exit
8.) Wait a few seconds, then:
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
beaups said:
Welcome to Facepalm S-Off for the Droid Incredible 4G LTE.
Credits and terms:
Exploit by beaups. Full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - Donate to beaups
jcase - Donate to jcase
dsb9938 - Donate to dsb9938
dr_drache - Donate to dr_drache
Thanks also to mdmower for commissioning Facepalm for this device, and testing.
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
Droid Incredible 4G LTE SuperCID: http://forum.xda-developers.com/showthread.php?t=2214653
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
1.) Download patcher and unzip it in your working directory:
soffbin3.zip
2.) Download the RUU zip below:
http://d-h.st/MOw
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip 2.17.605.2_rom.zip
After 2-3 minutes, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell
su
/data/local/tmp/soffbin3
exit
exit
8.) Wait a few seconds, then:
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Click to expand...
Click to collapse
wondering if this will survive a ota
jose51197 said:
wondering if this will survive a ota
Click to expand...
Click to collapse
Radio S-off always survives OTA...now whether or not the device survives.....
Sent from my HTC6435LVW using Tapatalk 2
Has anyone been able to get this to work? I've tried several times usually getting error 99: unknown fail while flashing the zip. I have superCID and an unlocked bootloader, fastboot and adb both working. I even returned the phone back to a stock rom at which point I got the zip to flash correctly (giving me error 92) but still get a write protection error trying to run soffbin3. When I retried after that I'm getting error 99 again at flashing the zip. I've tried from 2 different computers Windows 7 64 bit and Windows XP 32 bit same errors on both. Any ideas what could cause this?
mpappas87 said:
Has anyone been able to get this to work? I've tried several times usually getting error 99: unknown fail while flashing the zip. I have superCID and an unlocked bootloader, fastboot and adb both working. I even returned the phone back to a stock rom at which point I got the zip to flash correctly (giving me error 92) but still get a write protection error trying to run soffbin3. When I retried after that I'm getting error 99 again at flashing the zip. I've tried from 2 different computers Windows 7 64 bit and Windows XP 32 bit same errors on both. Any ideas what could cause this?
Click to expand...
Click to collapse
Of course it's been tested
For error99 do a full forced power down (hold power for 30 sec while unplugged or pull battery if you have one), then boot back up holding vol down to get back to bootloader.
Also, confirm you have superCID via fastboot getvar cid
beaups said:
Of course it's been tested
For error99 do a full forced power down (hold power for 30 sec while unplugged or pull battery if you have one), then boot back up holding vol down to get back to bootloader.
Also, confirm you have superCID via fastboot getvar cid
Click to expand...
Click to collapse
what value do you want us to have with super cid.
I unlocked and then reverted back toe the stock cid
dcooterfrog said:
what value do you want us to have with super cid.
I unlocked and then reverted back toe the stock cid
Click to expand...
Click to collapse
I THINK YOU SHOULD REMAIN ON SUPERCID(11111111)til you get s-off then if need be revert back.
dcooterfrog said:
what value do you want us to have with super cid.
I unlocked and then reverted back toe the stock cid
Click to expand...
Click to collapse
Any supercid should do, but 1's and 2's have been tested.
Sent from my HTC6435LVW using Tapatalk 2
Of course you've tested it I meant has anyone who is just a user trying to follow your instructions got it to work yet, I wasn't trying to be sarcastic. Anyway your battery pull instructions work for error 99 however I still keep getting the write protection error. My bootloader is unlocked and I have superCID set to 11111111. I'll copy what I see here so you can look at it
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.072s]
finished. total time: 0.072s
c:\Android>fastboot flash zip 2.17.605.2_rom.zip
sending 'zip' (583416 KB)...
OKAY [ 24.313s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 24.422s
c:\Android>fastboot oem boot
< waiting for device >
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02FA8C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2DB00
(bootloader) TAG:hero panel = 0x4940045
(bootloader) TAG:engineerid = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT26SS300293
(bootloader) commandline from head: console=ttyHSL0,115200,n8
(bootloader) command line length =739
(bootloader) active commandline: poweron_status=1 reset_status=0 board_fi
(bootloader) ghter.disable_uart3=0 diag.enabled=0 board_fighter.debug_uar
(bootloader) t=0 userdata_sel=0 androidboot.emmc=true androidboot.pagesiz
(bootloader) e=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=
(bootloader) 1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.of
(bootloader) s=694 imc_online_log=0 androidboot.efuse_info=FFSL androidb
(bootloader) oot.baseband=1.53.06.0919 androidboot.cid=11111111 androidbo
(bootloader) ot.devicerev=3 androidboot.batt_poweron=good_battery android
(bootloader) boot.carrier=ALL and
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3524), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:9464 msec
FAILED (status read failed (Too many links))
finished. total time: 6.292s
c:\Android>adb push soffbin3 /data/local/tmp/
1078 KB/s (2209 bytes in 0.002s)
c:\Android>adb shell chmod 744 /data/local/tmp/soffbin3
c:\Android>adb shell
[email protected]:/ # su
su
[email protected]:/ # /data/local/tmp/soffbin3
/data/local/tmp/soffbin3
/data/local/tmp/soffbin3[2]: cannot create │╗▒╫÷: Read-only file system
/data/local/tmp/soffbin3[2]: ┴√╓♣î⌠: not found
/data/local/tmp/soffbin3[4]: syntax error: 'ⁿ' unexpected
/data/local/tmp/soffbin3[2]: ╕╚Ç╫⌂idτº╬R░4↔∩N¥U÷Å┘)╘¿j¥&j+ò╩U¿PñF╩≥ÇTAäBÑJÇJôç
►╝D<B}░wYQéäè╘─ï∙╬▄;╗wªnE╟>{ε╣ττ₧{ε╣?τ╣╣┼yM╙╚*ö: not found
/data/local/tmp/soffbin3[2]: ┘ªnc↕♂mè◄←ßî╟Θ: not found
/data/local/tmp/soffbin3[2]: ô♦∞☻─Q└: not found
/data/local/tmp/soffbin3[2]: ª↕Wê2└δ}▄G╗2öó^≡▲ñ√⌐ç♦/│.₧: not found
1|[email protected]:/ # exit
exit
1|[email protected]:/ # exit
exit
c:\Android>adb reboot bootloader
Click to expand...
Click to collapse
I hope you can help me figure this out, I'd really like to have s-off and I do appreciate all your hard work putting this together for us.
Edit:
I tried again this time entering the fastboot oem boot and pressing enter while it was flashing the zip so that it ran as soon as it finished flashing the zip and it rebooted back to the black HTC screen. Is that supposed to happen should I just wait, I waited five minute (I timed it) and it never changed from that screen.
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.075s]
finished. total time: 0.075s
c:\Android>fastboot flash zip 2.17.605.2_rom.zip
sending 'zip' (583416 KB)...
OKAY [ 24.340s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 24.449s
c:\Android>fastboot oem boot
...
FAILED (command write failed (Too many links))
finished. total time: 0.001s
Click to expand...
Click to collapse
Well those are some weird errors you are getting indeed, the soffbin3 is pretty simple, should just return a 1.
Perhaps try on a more stock rom?
And your first method was the correct behavior, not the 2nd.
edit: I see your adb push only pushed 2209 bytes, which is the size of the ZIP file, not the decompressed binary.
The instructions clearly state you need to UNZIP it, not just delete the zip extension from your downloaded file. We zip the file before uploading in order to identify download errors.
Once decompressed the binary is 4751 bytes.
I know you're probably not going to believe me when I tell you this but I did unzip it something must have went wrong with the download/unzipping the first time. I re-downloaded it checked the MD5 and unzipped it and it worked great first try. Thank you so much for your help.
mpappas87 said:
I know you're probably not going to believe me when I tell you this but I did unzip it something must have went wrong with the download/unzipping the first time. I re-downloaded it checked the MD5 and unzipped it and it worked great first try. Thank you so much for your help.
Click to expand...
Click to collapse
no problem, glad you got it sorted.
some more questions
what does step 5 do. will it wipe my device. if used tibu to integrate a lot of apps into the stock rom and debloated a lot.
will it just recopy the stock system
what does the soffbin3 program do.
dcooterfrog said:
some more questions
what does step 5 do. will it wipe my device. if used tibu to integrate a lot of apps into the stock rom and debloated a lot.
will it just recopy the stock system
what does the soffbin3 program do.
Click to expand...
Click to collapse
The process just s-off's your device. If followed properly, there will be no wipe etc.
Sent from my HTC6435LVW using Tapatalk 2
Permission denied when trying to obtain S-OFF
Trouble obtaining S-OFF
Been working on this a while now. I go slowly through each step up to the point where it asks to type in su and hit enter and this is what I see (in command prompt):
FAILED (status read failed (Too many links))
finished. total time: 7.001s
C:\Users\Joe\Desktop\Fireball>adb push soffbin3 /data/local/tmp/
26 KB/s (4751 bytes in 0.173s)
C:\Users\Joe\Desktop\Fireball>adb shell chmod 744 /data/local/tmp/soffbin3
C:\Users\Joe\Desktop\Fireball>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ /data/local/tmp/soffbin3
/data/local/tmp/soffbin3
open: Permission denied
[email protected]:/ $
I'm going to guess that somehow it's not booting back into the stock rooted ROM with write privileges? I've tried going through this procedure 4 times to ensure I didn't type in anything wrong. Also, to confirm, I do have superCID:
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
and I have made sure the soff binary file (is of course unzipped) but also 4751 bytes.
Any ideas what I'm doing wrong here? I really appreciate this detailed write up, I just don't think I'm doing something right. Thanks!
joesee said:
Trouble obtaining S-OFF
Been working on this a while now. I go slowly through each step up to the point where it asks to type in su and hit enter and this is what I see (in command prompt):
FAILED (status read failed (Too many links))
finished. total time: 7.001s
C:\Users\Joe\Desktop\Fireball>adb push soffbin3 /data/local/tmp/
26 KB/s (4751 bytes in 0.173s)
C:\Users\Joe\Desktop\Fireball>adb shell chmod 744 /data/local/tmp/soffbin3
C:\Users\Joe\Desktop\Fireball>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ /data/local/tmp/soffbin3
/data/local/tmp/soffbin3
open: Permission denied
[email protected]:/ $
I'm going to guess that somehow it's not booting back into the stock rooted ROM with write privileges? I've tried going through this procedure 4 times to ensure I didn't type in anything wrong. Also, to confirm, I do have superCID:
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
and I have made sure the soff binary file (is of course unzipped) but also 4751 bytes.
Any ideas what I'm doing wrong here? I really appreciate this detailed write up, I just don't think I'm doing something right. Thanks!
Click to expand...
Click to collapse
You don't seem to have root access when trying to run soffbin3.
when you issue the su command the prompt should go from $ to #
But its staying $. So you either need to redo temp root or flash a custom recovery and flash an su zip.
Sent from my Nexus 7 using xda app-developers app
Incredible
Phenomenal work, thank you! Well written instructions and successful S-OFF of my device. I had no bizarre questions about what exactly a step meant. Lets just say good riddance to bad rubbish that comes from some of our friends.
and btw...Oh my gosh...I didn't need a specially sized microSD card to accomplish this
times_infinity said:
You don't seem to have root access when trying to run soffbin3.
when you issue the su command the prompt should go from $ to #
But its staying $. So you either need to redo temp root or flash a custom recovery and flash an su zip.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't understand temp root? The ROM I'm running is rooted, but when the phone is "temp rooted" I'm assuming you mean the phone lets you run commands as 'su' while running adb commands. If that's correct, that means according to this thread http://forum.xda-developers.com/showthread.php?t=2214653 - I would have to type this in ADB:
adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
then reboot when the command is finished and only THEN I have temp root and can finish with the facepalm instructions right before I go into adb shell?
I have dabbled around with adb commands for a while now but don't understand why I've got su.zip flashed on my phone and have root at the ROM level I have to do this temp root ? Please help me understand?
Right now my phone is stuck in the odd mode where only your notification bar appears and accepts no adb commands but does show up under "adb devices'.
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
times_infinity said:
You don't seem to have root access when trying to run soffbin3.
when you issue the su command the prompt should go from $ to #
But its staying $. So you either need to redo temp root or flash a custom recovery and flash an su zip.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
After running the temproot adb commands shown in my previous post, this is a paste of my command prompt:
C:\Android\Inc4G>adb shell chmod 744 /data/local/tmp/soffbin3
C:\Android\Inc4G>adb shell
[email protected]:/ # su
su
[email protected]:/ # /data/local/tmp/soffbin3
/data/local/tmp/soffbin3
1|[email protected]:/ # exit
exit
1|[email protected]:/ # exit
exit
C:\Android\Inc4G>adb reboot bootloader
That time I did not get permission denied, but there was no pause whatsoever in the command and after rebooting into the bootloader I still have S-ON. Before I try something else I was wondering what might be happening?
---------- Post added 10th June 2013 at 12:09 AM ---------- Previous post was 9th June 2013 at 11:56 PM ----------
joesee said:
I don't understand temp root? The ROM I'm running is rooted, but when the phone is "temp rooted" I'm assuming you mean the phone lets you run commands as 'su' while running adb commands. If that's correct, that means according to this thread http://forum.xda-developers.com/showthread.php?t=2214653 - I would have to type this in ADB:
adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
then reboot when the command is finished and only THEN I have temp root and can finish with the facepalm instructions right before I go into adb shell?
I have dabbled around with adb commands for a while now but don't understand why I've got su.zip flashed on my phone and have root at the ROM level I have to do this temp root ? Please help me understand?
Right now my phone is stuck in the odd mode where only your notification bar appears and accepts no adb commands but does show up under "adb devices'.
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
After running the temproot adb commands shown in my previous post, this is a paste of my command prompt:
C:\Android\Inc4G>adb shell chmod 744 /data/local/tmp/soffbin3
C:\Android\Inc4G>adb shell
[email protected]:/ # su
su
[email protected]:/ # /data/local/tmp/soffbin3
/data/local/tmp/soffbin3
1|[email protected]:/ # exit
exit
1|[email protected]:/ # exit
exit
C:\Android\Inc4G>adb reboot bootloader
That time I did not get permission denied, but there was no pause whatsoever in the command and after rebooting into the bootloader I still have S-ON. Before I try something else I was wondering what might be happening?
Click to expand...
Click to collapse
I just wanted to take a minute and thank everyone for this write up. After running through this process 3 full times, I've FINALLY gotten S-OFF on my Incredible4G. Thanks again for all your hard work!!
I was wondering if I could kindly get some assistance.
I keep getting the following error:
C:\WINDOWS\system32>fastboot flash zip 2.17.605.2_rom.zip
error: cannot load '2.17.605.2_rom.zip'
I am BL unlocked, supercid, running ViperROM.
I am not quite sure what I am doing wrong. I seemed to have followed the instructions to a tee.
Assistance is greatly appreciated!
Moved to troubleshoot forum.
Thread
Sent from my ADR6410LVW using xda app-developers app
What is "EARLY ACCESS PREVIEW"?
We want to give you S-OFF as soon as practically possible so an early access preview release is not a polished product but it does work (mostly). It will:-
* require knowledge of common android tools like adb and/or fastboot
* be a command line tool
* be rough around the edges
* probably crash sometimes
* fail to work everytime or in all cases or on different carrier ROMs - LET US KNOW if you get repeated failure on carrier variants.
* certainly not look pretty.
* despite being "early access" be very unlikely to brick your device (but naturally, this is possible, it's still a hack).
* give you a very good chance of getting S-OFF. Today. Right now.
Status
This version of revone has been successfully tested on Droid DNA 2.04 / 2.06 and Butterfly J 1.29.
Download
* Get the Android SDK for ADB. You may need to update to the latest version of the SDK for jellybean devices.
* Download revone: http://revolutionary.io/revone.dna
Instructions
Use any operating system you like, you only need adb.
1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/
2. Open an adb shell and:
* cd /data/local/tmp
* chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone.dna -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone.dna -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone.dna -t
Credits
revone is brought to you by the Revolutionary dev team.
We've been silent, we're back.
Disclaimer
Revolutionary dev team disclaims all responsibility for your use of revone (and any of our tools): If the world ends, it's not our fault. If your device spontaneously ignites, well, that's not our fault either. You make the choice to use our tool, we don't force it upon you.
Support
Please visit #revolutionary on the Freenode IRC network. We will try to support you in the best way possible, but remember, this is early access, and operators might be asleep or not available at the time you join. Just hang around and wait for someone to answer.
(reserved)
UPDATED revone binary (v0.2.1)
* Safety update: No longer allows -s 3 since this can lead to bricks with custom HBOOTs, use: fastboot oem writesecureflag 3 (which is safer - and checks such things)
* Fix: delusions of grandeur - revone now no longer reports success when it fails.
* Outside chance some previous failures will now be successful but most likely they will just correctly report failure.
* Remove the random reboot feature.
* Vastly reduce the error -6 probability.
Please note that due to the safety update ALL previous versions have been replaced with v0.2.1 and are hence no longer supported.
YOU WILL NOT RECEIVE SUPPORT FOR A VERSION LESS THAN v0.2.1
Download: revone.dna-0.2.1
Use as per OP instructions renaming or name substituting as appropriate.
Reverting to S-ON (updated)
* ./revone -l
* fastboot oem writesecureflag 3
Stuck with error: -1?
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
Redistribution/Bundling revone
Permission is not given to redistribute and/or bundle revone into "one click" utilities (or similar). Please only obtain revone directly from us, this allows us to ensure the most up to date version is available in case of any critical issues.
Many thanks for your understanding.
I'm just going to wait for a video tutorial before I attempt this. Don't want a brick. Thanks
Sent from my HTC6435LVW using xda premium
DELETED
thx~!! revteam!!!
HTC J butterfly 1.29.970.1 S-OFF succsess!!
{
"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"
}
Reserved
Sent from my LG-LS970 using xda app-developers app
AWESOME! going to do this right now and let you know if there were any problems
Yep. Worked great. S-off 2.06 firmware. thankyou guys
Great work! I am running into the following.
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
Success.
revone failed (error code = 2
As I proceed from here, everything shows success, but I am not unlocked. I am running a Droid DNA with
Software Number: 2.06.605.1.710RD
HBOOT-1.33.0001
Let me know if you want anything from my phone.
Works great. Thank you. You have increased the value of DNA to me.
itsmikeyj said:
Great work! I am running into the following.
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
Success.
revone failed (error code = 2
As I proceed from here, everything shows success, but I am not unlocked. I am running a Droid DNA with
Software Number: 2.06.605.1.710RD
HBOOT-1.33.0001
Let me know if you want anything from my phone.
Click to expand...
Click to collapse
Looks like removing the existing script and waiting 2 minutes then repeating worked just fine. Thanks guys!
nice work guys!
Great work!
I'm already s-off but whoooohooooo boy hell yeah good stuff guys very good to see a new method in case I have to replace my phone lol!!!!!
Sent from my HTC6435LVW using Tapatalk 2
Awesome work.. after s-off. What's needed for root?
Sent from my HTC6435LVW using xda app-developers app
Didn't work for me. I didn't get any errors, everything says success but I'm still S-On at the end ....
Stickboy46 said:
Didn't work for me. I didn't get any errors, everything says success but I'm still S-On at the end ....
Click to expand...
Click to collapse
Out of interest - how are you rebooting the device after the prepare stage (-P) ?
kmdm said:
Out of interest - how are you rebooting the device after the prepare stage (-P) ?
Click to expand...
Click to collapse
The Device auto rebooted
Stickboy46 said:
The Device auto rebooted
Click to expand...
Click to collapse
That is not a "success" state for "-P". Sadly. (It is very much an error/hard-crash though.)
Can you try
adb reboot
wait approx 2-3mins (2 mins seemed best for me once the adb wait-for-device returned)
then do ./revone -P ?
auto-reboot = bad.
I just received my replacement Droid DNA and I'm trying to achieve S-OFF by using the Revone method. Every time I use "./revone.dna -s 0 -u" i get the following error:
C:\Users\walter>C:\platform-tools\adb.exe shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone.dna
chmod 755 revone.dna
[email protected]:/data/local/tmp $ ./revone.dna
./revone.dna
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $
C:\Users\walter>C:\platform-tools\adb.exe shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone.dna -s 0 -u
./revone.dna -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $
if someone has any advice i would greatly appreciate it. Also I've tried this on a mac and a pc.
Did you download the revone.dna package from the third post or OP? If OP, download from third post.
I also don't see where you are using the -P command... I keep seeing people say skip that, but I followed the OP step by step and had not one single error or issue.
Phaded said:
Did you download the revone.dna package from the third post or OP? If OP, download from third post.
I also don't see where you are using the -P command... I keep seeing people say skip that, but I followed the OP step by step and had not one single error or issue.
Click to expand...
Click to collapse
They left off the -P in the command.
OP, have you tried using the command with -P implemented? It took me hundreds of tries, with and without the -P to get it to finally work.
I'm having the same issue when I run ./revone.dna -P
I get failed to map memory everytime did you ever get this to work
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I too got similar errors when using RevOne. I ended up using moonshine. Moonshine gave me an error about 2/3 through and said it failed. While moonshine failed to install cwm and custom moonshine hboot, it did get me s off and eng hboot so I was able to install cwm and then custom roms.
Sent from my HTC6435LVW using xda app-developers app
I can't get moonshine to do anything it just keeps prompting me to type yes/no does nothing else
Sent from my HTC6435LVW using XDA Premium 4 mobile app