im confused about this o.0
{
"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"
}
Head over to the development section and help us out with unlocking all the s-on devices
Sent from my HTC Sensation 4G using XDA Premium App
Are you trying to root your phone or what?
@op, check your PM's please.
Holy ****. S-off with 1.17bootloader with the stock bootloader...
I'm envious to say the least, where did this phone come from? Network? Supplier?
Would you mind dumping your hboot and uploading it to a dropbox/upload site?
Code:
cd c:\adb
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
It would be useful to have this hboot version.
Evil-Dragon said:
I'm envious to say the least, where did this phone come from? Network? Supplier?
Click to expand...
Click to collapse
i got my sensation from HTC before launch and i get off work at 6 so ill try and help after that
Any luck pulling that HBOOT?
Evil-Dragon said:
Would you mind dumping your hboot and uploading it to a dropbox/upload site?
Code:
cd c:\adb
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
It would be useful to have this hboot version.
Click to expand...
Click to collapse
yeah but i dont know why i didnt reaply back to this. sorry haha.
it didnt work. it said no device found then some other error
iPrevailed YDG said:
it didnt work. it said no device found then some other error
Click to expand...
Click to collapse
You'll need to install the android sdk, download the google usb drivers from it and get your phone set up as a ADB Composite Interface. Then make sure USB debugging is enabled on your phone and you'll be able to run the above commands.
Evil-Dragon said:
You'll need to install the android sdk, download the google usb drivers from it and get your phone set up as a ADB Composite Interface. Then make sure USB debugging is enabled on your phone and you'll be able to run the above commands.
Click to expand...
Click to collapse
"Permission not allowed"
iPrevailed YDG said:
"Permission not allowed"
Click to expand...
Click to collapse
You shouldn't be getting a root denial from that command. It looks like HTC *really* bolted it down. Out of curiosity, have you tried downloading Superuser from market? If you have an unlocked boot loader, there is a very very VERY slight chance that you might be able to su out of the box. Doubtful but its worth a try.
just updated everything and got this also SU didnt work ]:
Code:
C:\Users\********>cd c:\sdk\tools
c:\SDK\tools>adb devices
List of devices attached
HT15HT****** device
c:\SDK\tools>adb shell
$ dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
/dev/block/mmcblk0p12: cannot open for read: Permission denied
$
Related
Hi,
My name is Joe aka AndroidSamurai..
I have recently made some business acquisitions and will be starting up a new Android Learning series.. Stay tuned for updates..
Thanks again,
AndroidSamurai
Android4D Inc
I thought some people might appreciate the instructions to get adb working over WiFi too and this seems like a good place to put it:
Type this in your terminal emulator on your Android device:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Then check it with this:
Code:
getprop service.adb.tcp.port
If it doesn't return "5555" and you're rooted, then do a "su" command and try again. You shouldn't need to be rooted for adb over wifi to work, but I haven't tried every device:
Code:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Then check it:
Code:
getprop service.adb.tcp.port
When it returns "5555" then run this command in the terminal (or command prompt) on your computer:
Code:
adb connect 192.168.0.151
(Obviously enter your device's IP address. You must be on the same network as the computer that has the Android SDK installed.)
And you should be connected!
To tell the Android device to listen for adb on the USB port instead of TCP again, enter this into the terminal emulator:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
(again, might need "su" on your device)
Or just reboot the Android device.
And to tell your computer to use USB for adb instead of TCP:
Code:
adb usb
Now, keep in mind, when your Android device is listening for adb via WiFi, it's wide open... anybody that that the Android SDK installed and knows your device's IP address can access it without a password.
HTH,
Billy
PS - Your
{
"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"
}
are appreciated!
Updating Soon!
Pleased to announce that I will be updating my Full guide within the next few business days along with an E-book version and a Video Guide...
If my guide has helped you please help fund my college, donate.
Thanks for your help guys...
Moved My Guide!
Hey All,
I am pleased to announce that an updated version of my guide and soon to be All in one android E-book is on my website...
Link is in the first post, thanks to all at XDA over the yrs that have used my guide...
Cool, thanks. I plan on using this pretty soon. I really need to get better.
Sent from my SAMSUNG-SGH-I897 using XDA App
Moved my guide!
Hey All,
Sorry to inform you, but my guide has been moved to another site... I can not advertise because it is just not moral...
Click the link to take you to my new guide...
had a question
hi i was wondering if u could help with with a problem im having...i flashed my Tp2 over to boost and it was working fine..except for the web..so i changed the ppp cong and it rebooted..now i have a blue circle with a line through it..and when i try to connect i get a message that says" The process com.android phone has stopped unexpectedly. Please try again"....and theres no longer a connection for the usb in my contron planel......just tossing it out there to see if u had any ideas..thanks S
Updated..
My guide is now even more userfriendly...
Had to make a few revision changes to simplify the process...
Hi,
I'm new here, so I don't know how to put this...
I have a HTC Legend 2.2 Froyo with HBoot 1.01 and I want to downgrade and root it so I can put CM7 on it. Can anyone tell me how to do this?
Thanks!
DM779
@DMasta779 read this ---> [GUIDE] How To Root HBOOT 1.01
i4o said:
@DMasta779 read this ---> [GUIDE] How To Root HBOOT 1.01
Click to expand...
Click to collapse
Thanks, but at the first step, where I type ''adb shell'' it
says:''adb: permission denied''.
What do I have to do?
On linux, make sure adb is executable. On windows, make sure you run cmd as an administrator
Help?
I always did it on my phone with Terminal Emulator(Temprooted). When I type in ''adb shell'' it gives ''adb: permission denied''. When I try it on my PC(Windows) With only charge and USB debugging on, adb doesn't find my phone.(This is also in fastboot mode)
It gives: ''error: device not found''. What on earth am I doing wrong?
Adb isn't executed on the phone, it's on the pc. The phone should be running normally when you run it (with usb debugging enabled)
Also install htc sync to get the correct drivers
Rehash: start the phone normally. Ensure usb debugging is enabled. Plug the gizmo into your pc. Run adb shell in the command prompt as administrator
Sent from my GT-P1000 using XDA App
http ://i55.tinypic.com/f35a2q.png
This is where I get stucked right now. Anyone?
(delete the space in the URL)
The things that've deleted, are the CID's.
DMasta779 said:
http ://i55.tinypic.com/f35a2q.png
This is where I get stucked right now. Anyone?
(delete the space in the URL)
The things that've deleted, are the CID's.
Click to expand...
Click to collapse
Adb is not a valid binary on the phone.
When you issue adb shell you're dropped in to the shell on the phone. Any commands entered there execute on the phone. Type exit to get out of the shell before executing the push commands
Sent from my GT-P1000 using XDA App
Oh OK, I see, but when I type in just ''push goldcard.img /data/local/'' after adb shell, it says: ''push: permission denied''. (running as admin in windows and temprooted phone)
Exit out of the phone's shell, them the command is
Code:
adb push goldcard.img /data/local
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think it didn't push the file completely. I get this every time when I am trying to push something.
EDIT: I did ignore it and advanced to the next steps and by this command I get stuck:
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I can't backup/write the misc
So recently I've been messing around my Sensation, adding custom bootanimations and splash screens.
I've backed up the old one using
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
So to restore it I'd thought I'd do the opposite
Code:
dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p1
Bad news, the phone is dead.
I can't boot into recovery or anything. So... is there a cure?
Matt1408 said:
So recently I've been messing around my Sensation, adding custom bootanimations and splash screens.
I've backed up the old one using
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
So to restore it I'd thought I'd do the opposite
Code:
dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p1
Bad news, the phone is dead.
I can't boot into recovery or anything. So... is there a cure?
Click to expand...
Click to collapse
If that second line is the actual one you used, then you pushed the splash screen img file to mmcblk0p1 instead of mmcblk0p19.
Crap, looks like I made a typo and messed it up.
{
"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"
}
have you tried flashing stock RUU to restore?
Forgive me for asking, but where is this RUU.exe?
Oh no! good luck matt.
Matt1408 said:
Forgive me for asking, but where is this RUU.exe?
Click to expand...
Click to collapse
depends on your model, but i can help ya
is it unbranded? or bell/tmobile etc?
It's the Bell version
and you cant get into bootloader at all?
have you tried pulling the battery for 5-10sec, put it back in, then old VOL.DOWN + POWER?
I've tried pulling the battery, and booting into recovery, but to no avail.
However, when I plug in the phone to my computer, I get something about "qhsusb_dload." But thats about all that happens. Adb doesn't work, and such.
thats actually a really good sign!
do you have ADB on your computer? you WILL need that for sure, if not ill get ya a link
Of course I do, what do you think got me in trouble in the first place
hahaha oh yeah, just looked at first page
ok so go into cmd, connect phone via usb and type - adb devices
edit* also, just noticed your name is matt and you live in toronto, as is/am i
also, sorry im doing a million things at once cuz im at work, so some posts might be short 1-2 steps
Code:
C:\Users\Matt\Desktop\New folder>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
No devices show up.
are you running cmd as admin? thats important
Yup. No dice.
can you check battery discharge? i just wanna see what level of control you have.
enter
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
it will say "CHARGING" or "DISCHARGE"
As I said, adb doesn't detect the phone.
But the phone was about 90% when I killed it.
ok well it seems thats its in download/recovery mode from you're earlier post, so lets try fastboot
fastboot reboot
OR
fastboot reboot-bootloader
EDIT* also, are you rooted, superCID or anything special like that?
<waiting for device>
... nothing
since s-off has the power to change anything, is there anyway to make the boatloader report locked instead relocked?
i know this is not necessary for doing anything at all since it is already s-off, but i'm just wondering what keeping this locking flag/status...
found this:
http://forum.xda-developers.com/showthread.php?t=1970252
http://forum.xda-developers.com/showthread.php?t=2168578
i have dumped the mmcblk0p3, and found the same "HTCU" (unlocked) or "HTCL" (relocked) string at 8404 address. so i went to modify it to x00 x00 x00 x00 and viola, it become "LOCKED" now.
here is the command that i used:
adb shell
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3
exit
exit
adb pull /sdcard/mmcblk0p3
copy mmcblk0p3 mmcblk0p3mod
hexalter mmcblk0p3mod 0x8404=0x00,0x00,0x00,0x00
adb push mmcblk0p3mod /sdcard/mmcblk0p3mod
adb shell
su
dd if=/sdcard/mmcblk0p3mod of=/dev/block/mmcblk0p3
exit
exit
so in summary, we can quickly jump from lock to unlocked, or unlocked to relocked/locked without using the token...
i found :
{
"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"
}
Code:
[COLOR="Red"]This build is for development purposes only.
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action.[/COLOR]
in : hboot_signedbyaa.img
Do you think we use hexalter to remove "Disclaimer on HTC Splash Screen" ?
Not sure about that, I have not see the flag to control that yet... I think you can change that, but finding the right location for that flag might be difficult...
For this lock/relock/unlock flag, people is able to find it by comparing the rom during before and after, validate the result using other phone, and confirm the finding with other users...
If you don't have other phone to use as experiment and other people to confirm your finding, I afraid it is going to be very hard, you are just like walking in the dark...
Sent from my HTC Butterfly using Tapatalk 2
gbear said:
Not sure about that, I have not see the flag to control that yet... I think you can change that, but finding the right location for that flag might be difficult...
For this lock/relock/unlock flag, people is able to find it by comparing the rom during before and after, validate the result using other phone, and confirm the finding with other users...
If you don't have other phone to use as experiment and other people to confirm your finding, I afraid it is going to be very hard, you are just like walking in the dark...
Sent from my HTC Butterfly using Tapatalk 2
Click to expand...
Click to collapse
But I think we cant do that, coz hboot ship is sign hboot, we will brick our phone! So flashing eng boot with that hex editor to remove will help, but i dont wana to take that risk..
? Killx Kernel ?
Hi guys. I have a small problem. I did it with the root method @ Miche1asso and I wanted to backup partition TA. When I start this script http://forum.xda-developers.com/showthread.php?t=2292598 me from error and the procedure does not go abuon end. I am attaching the screen errors that from me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I believe that it can not back up because located 2 device. My cell phone and the emulator. In fact, if I give the command 'adb devices' me from this.
Should I disable the emulator but do not know how to do. Could you help me?
Try to run first
adb connect <id of your phone>
All following adb commands should be directed to your phone, ignoring the other device(s). Not sure where that emulator thing comes from, though. I've never had that issue.
Miche1asso said:
Try to run first
adb connect <id of your phone>
All following adb commands should be directed to your phone, ignoring the other device(s). Not sure where that emulator thing comes from, though. I've never had that issue.
Click to expand...
Click to collapse
It does not work
nunu00 said:
It does not work
Click to expand...
Click to collapse
Sorry, my fault. "adb connect" only works with the TCP/IP adb connections. As in adb help for "adb -s" you should set
Code:
set ANDROID_SERIAL=<specific device>
You get to choose <specific device> of your phone from the "adb devices" list. I am not sure about the syntax in Windows but I believe the one above should work.
Miche1asso said:
Sorry, my fault. "adb connect" only works with the TCP/IP adb connections. As in adb help for "adb -s" you should set
Code:
set ANDROID_SERIAL=<specific device>
You get to choose <specific device> of your phone from the "adb devices" list. I am not sure about the syntax in Windows but I believe the one above should work.
Click to expand...
Click to collapse
Thanks anyway, but I solved in another way
Inviato dal mio D2303 utilizzando Tapatalk
nunu00 said:
Thanks anyway, but I solved in another way
Click to expand...
Click to collapse
Which is? Why was the emulator enabled? Did you disable it? How?
Miche1asso said:
Which is? Why was the emulator enabled? Did you disable it? How?
Click to expand...
Click to collapse
I do not know because the emulator is enabled but I could not disabillitarlo. I solved it by changing the script Backup-TA-9.11. I added "-d" after "adb.exe". I attach a screen to better understand