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've seen the Zerg root for the 4G, but after reading some comments about it there's been speculation that the 1.45.1500.2 is Zerg root proof. It there a way to root the Amaze with 1.45.1500.2 software?
On another note... I'm not able to tether with my phone? i'm able to make a hot spot and all yet, I cannot connect any devices to it. The devices seem to not be able to acquire the IP address.
All tips and suggestions are helpful, so please comment as I'm sure you'll be able to help me with my issues one way or another.
Have you unlocked your bootloader?
Sent from my HTC Amaze 4G using xda premium
*edit
What's the complete process in rooting the device with the 1.45.1500.2 software? I'm going to bootload it as soon as it's fully charged.
To unlock your bootloader:
Go to http://htcdev.com/register/ and register an account with them.
Then select "Begin Unlock bootloader"
Follow the steps. It is easy. Just back up your info because when you unlock it, it will require a hard reset.
To do install ClockWorkMod Recovery (CWM), go to this link.
http://forum.xda-developers.com/showthread.php?t=1316855
Follow the instructions that says "Installation from fastboot (hboot only ||Hard Method||):" (It's actually very easy and it worked on the new ROM update)
Download the ClockworkMOD 5.0.2.7 Amaze 4g and not the ClockworkMOD 5.0.2.0 Amaze 4g.
To root, you can install a prerooted Custom ROM or you can download SuperUser (SU) from here
http://www.multiupload.com/TI14RLNE8A
Just boot into CWM and flash the su-2.3.6.3-ef-signed.zip if you want to root it with your stock ROM.
To get WiFi Tethering working, you need root (duh).
Download WiFi Tether for Root Users 3.1-beta9
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_1-beta9.apk
After you install it, press the menu button. Select "Settings". Change the Device Profile to HTC Amaze / HTC Ruby. You are good to go!
Much appreciated, will try this tonight and will get back to you
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
HTC Bootloader unlock
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
RyanB125 said:
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
Click to expand...
Click to collapse
Tardango said:
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
Click to expand...
Click to collapse
Alright, I guess i'll have to try again tomorrow.
The site is down I believe. I tried it for my friend. If it works, let me know!
Zerg not working on my unlocked Amaze
I have unlocked my bootloader and am running 1.43.531.3. I get pretty much the same set of errors every time I run the bat file. I have tried factory resetting it 3 times and trying again, but it always does the same thing. Occasionally it'll also say rm failed: no such file or directory on the adb shell rm /data/local/tmp/*sh command. USB debugging is on.
C:\Zerg>adb wait-for-device
C:\Zerg>adb push zergRush /data/local/
1294 KB/s (21215 bytes in 0.016s)
C:\Zerg>adb shell chmod 777 /data/local/zergRush
C:\Zerg>adb shell rm /data/local/tmp/*sh
C:\Zerg>adb shell /data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sleep 1
C:\Zerg>adb remount
remount failed: Operation not permitted
C:\Zerg>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg>adb install ./androidterm.apk
1969 KB/s (92780 bytes in 0.046s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sync
C:\Zerg>pause
Press any key to continue . . .
Have you installed CWM?
Still getting the same errors as before. :/
edit* is there any report as to when the HTCdev page will be fixed?
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
hasoon2000 said:
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
Click to expand...
Click to collapse
I'm still receiving the same error!
PM me the token ID in a text file attachment. I will see what the issue is.
pepsishine said:
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
Click to expand...
Click to collapse
Assuming you are trying to root, you might try this approach. Worked for me. After the wifi update I had to reset to factory and remove CWM to get the update to install. After the update I did this again and all went well except I got an error during the root process using the file I downloaded from that thread. Thought maybe I was out of luck, but after rebooting the phone it was rooted. Been working fine for the past several days.
hasoon2000 said:
PM me the token ID in a text file attachment. I will see what the issue is.
Click to expand...
Click to collapse
Alright, give me a sec, i'll pm you.
Are you on Telus or Wind mobile? I heard that they didn't give HTC permission to allow the customers to unlock their bootloaders
Sent from my HTC_Amaze_4G using xda premium
I'm with Wind.
Some time ago I rooted with photo torpedo direct v1.1. Then I did a factory reset ..
Now I would like to remove root and go back to "stock"
When running photon torpedo direct and choosing 2. Root Cleaner (unroot) I get the following...
Code:
Sending Torpedo to Phone
1008 KB/s (2817536 bytes in 2.727s)
Setting Permissions
chmod: permission denied
Unpacking Torpedo
/bin/tar: not found
Press any key to continue . . .
Likewise I get the same error when attempting to root.
I tried using adb manually to see if those tools even exist and get the following.
Code:
c:\root>adb.exe shell
$ chmod
chmod
chmod: permission denied
$ /bin/tar
/bin/tar
/bin/tar: not found
$ su
su
# chomd
chomd
chomd: not found
# /bin/tar
/bin/tar
/bin/tar: not found
#
Please help I seem to be stuck in some limbo mode.
I gave up trying to fix the issue and reflashed using this post
Synicasm said:
Some time ago I rooted with photo torpedo direct v1.1. Then I did a factory reset ..
Now I would like to remove root and go back to "stock"
When running photon torpedo direct and choosing 2. Root Cleaner (unroot) I get the following...
Code:
Sending Torpedo to Phone
1008 KB/s (2817536 bytes in 2.727s)
Setting Permissions
chmod: permission denied
Unpacking Torpedo
/bin/tar: not found
Press any key to continue . . .
Likewise I get the same error when attempting to root.
I tried using adb manually to see if those tools even exist and get the following.
Code:
c:\root>adb.exe shell
$ chmod
chmod
chmod: permission denied
$ /bin/tar
/bin/tar
/bin/tar: not found
$ su
su
# chomd
chomd
chomd: not found
# /bin/tar
/bin/tar
/bin/tar: not found
#
Please help I seem to be stuck in some limbo mode.
Click to expand...
Click to collapse
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.
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