I can access the bootloader and twrp recovery for this Sprint HTC one.
My S is set to on
And I can't recover RUU because I have a newer version, it fails midway thru.
I tried to push a rom to load via adp with the all in one options. but nothing works
I cant load/flash a new rom, because I cant see the sdcard on my pc. At this point, I want to give up and just return to stock.
When I tried to flash RUU it wiped my SD card. So I have no rom to load/flash. I cant access Developer mode in OS to disable S to off.
Could s off be blocking my RUU to stock?
If you have any information, links to the appropriate Sprint roms/images file would be appreciated.
I am truly lost.
From recovery follow the guide for 1.31 RUU which I will link below.
Now to RUU follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
You will see this message (failed) ignore it and flash the RUU anyway.
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Sent from my HTCONE using xda app-developers app
Thank you
Konfuzion said:
From recovery follow the guide for 1.31 RUU which I will link below.
Now to RUU follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
You will see this message (failed) ignore it and flash the RUU anyway.
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I will try this as soon as I get home.
Thank you for your time
Related
i accidentally flash my phone to the wrong thing i now have a phone on dark bootloader from GE how can i flash back to stock ? im trying to go back to 1.29.651.100 i am currently on 3.06.1700.00
From recovery, use adb to push the 1.29
adb push the 1.29 hboot to your sdcard.
adb push nameofhboot.nb0 /sdcard/nameofhboot.nb0
adb shell
dd if=/sdcard/nameofhboot.nb0 of=/dev/block/mmcblk0p12
Then reboot to bootloader.
Sent from my HTCONE using XDA Premium 4 mobile app
18th.abn said:
From recovery, use adb to push the 1.29
adb push the 1.29 hboot to your sdcard.
adb push nameofhboot.nb0 /sdcard/nameofhboot.nb0
adb shell
dd if=/sdcard/nameofhboot.nb0 of=/dev/block/mmcblk0p12
Then reboot to bootloader.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How would I do that sorry im new to this and also I can't get my laptop to even read it
seniorblaze said:
How would I do that sorry im new to this and also I can't get my laptop to even read it
Click to expand...
Click to collapse
From recovery follow the guide for 1.31 RUU which I will link below.
Now to RUU follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
You will see this message (failed) ignore it and flash the RUU anyway.
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
Then RUU here click the first link, extract to desktop open and click setup, then follow the prompts.
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Sent from my HTCONE using xda app-developers app
Sent from my HTCONE using xda app-developers app
I did what u said and when I use the ruu it says error image. 158
------------------------------------SOLVED---------------------------------------------------------------------
JUST CARRIED OUT THE COMMANDS IN CWM RECOVERY ....THAT SOLVED ALL PROBLEMS
I have htc j one ...japanese htc one
Hboot is 1.52 and android 4.1.2
I have been able to s off, unlock bootloader using revone
I have flash cwm and rooted phone
Now I need to sim unlock the phone with some adb commands given in the below mentioned website :-
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
You can easily auto translate the above page if u open it in google chrome
Can anyone help me with that ?
Thanks in advance
Sent from my GT-N7000 using xda premium
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
criszz said:
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
Click to expand...
Click to collapse
Thanks for replying
I will download this file and put in adb folder
I shud do
adb push misc.img
( is this commabd correct or do I need to to put / ar back)
Then
Adb shell
It shows $ at the end
So it type
Su
Now it becomes #
Then I shud type
dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
Am I correct ?
Plz help as I am noob in this ...but am trying to learn
Sent from my GT-N7000 using xda premium
The auto-translated instructions are not good enough, and this is a very risky procedure. Fortunately, with code you usually don't need to read the words to understand it. Fortunately, with my Japanese-speaking colleague's help, I understand everything. Some things to know:
- Don't try this unless you are content to risk your phone, because I can tell he made mistakes in his instructions
- To reiterate, you either need to follow his incorrect instructions or you need to listen to me (why would you do that?)
- Look at the code blocks--all that code is meant to be run on your computer while the phone is connected to USB.
- There is only one complicated step, and this is the one with the incorrect instructions.
What he says:
Open misc.img in a hex editor, represent [00001023] as [11] and save. If you are lazy, use the file I modified already. <link>
There are two problems with this statement. First, "00001023" is not a reasonable position in the file. It means "line 10, column 3" (lines start with zero, columns start with zero). But there are 16 bytes per line, so what he really means is "byte 147". (Each pair of hex characters is a byte. The lowest value is 00, the highest value is ff.)
The second problem is that in his "already modified" file, that byte is "00", not "11". This is what I expected, because it's not reasonable for number="11" to mean "unlocked". More likely, "11" is his carrier and "00" is when the phone is unlocked.
What I advise is getting your carrier to unlock the phone, and if that's not possible, proceed only if you are willing to risk your phone. Follow his instructions, but when you get your misc.img file, download his modified version and compare them. If they differ in only one position, install his file to your phone (as per the instructions). If they are very different but the same size, you can try changing byte 147 to 00 (if the surrounding bytes are also all 00). Save the unmodified .img file, because you might be able to use it to rescue your phone if this fails.
Note: this is risky, with or without language barrier issues. At least 10% chance of bricking your phone.
Thanks a lot for your advice.
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Currently am stuck ...
Sent from my GT-N7000 using xda premium
sitanshu91 said:
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Click to expand...
Click to collapse
I think it's probably safe to flash the misc.img file he uploaded and linked to, if (and only if) it is exactly the same as yours, except for that one byte. Low chance of bricking the phone.
But currently can you tell me to how to pull the image coz I havr followed his command ...
Adb shell
It strt with $
Su
Now # come
Then somd dd comand
Here it shows operation cannot complete(will update what is exactly error in few min)
Exit
Adb pull misc.img
Here it shows error device not detected
Can you help me to first pull file so I can compare
Sent from my GT-N7000 using xda premium
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
fenstre said:
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
Click to expand...
Click to collapse
see this is what i get
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ #
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
requesting your help
thanks
sitanshu91 said:
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
Click to expand...
Click to collapse
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
fenstre said:
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
Click to expand...
Click to collapse
so you say i should proceed
see again i did the same
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT35Z******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ # exit
exit
1|[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
now how should i proceed ....please help
Guys requesting help before the new year starts
So I can use my phone in new year
Sent from my GT-N7000 using xda premium
sitanshu91 said:
/misc.img: cannot open for write: Read-only file system
Click to expand...
Click to collapse
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Kasi!995 said:
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Click to expand...
Click to collapse
yes this is unlocked bootloader ...i have done it thru revone
now i have installed busybox
and i can progress
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT3******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
sitanshu91 said:
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
Click to expand...
Click to collapse
what Recovery do you have flashed? TWRP?
Its cwm recovery
Sent from my GT-N7000 using xda premium
Run adb pull outside of adb shell.
1st problem :-
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you tell me where is my mistake
What can I do can you type command
2nd problem
similiarly when i try
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb push misc.img /
failed to copy 'misc.img' to '//misc.img': Permission denied
request you to please help me
thanks and regards
Sent from my GT-N7000 using xda premium
what is your status now?
criszz said:
what is your status now?
Click to expand...
Click to collapse
i am very glad that you asked .....happy new year
Now my status is sim unlocked ....but i can use only to make and receive phone calls and sms ...
now here is the problem
i cant use data (2g/3g) on my phone
do u know how to do that
thanks
sitanshu
hlo...... I used command method to remove tampered and it was gone at first but when I unlocked bootloader using command tampered came again and now it is not going with revine,guru bootloader......helppppp
jaspreet4140 said:
hlo...... I used command method to remove tampered and it was gone at first but when I unlocked bootloader using command tampered came again and now it is not going with revine,guru bootloader......helppppp
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2477792
helpp
hy nykk again.......thx for reply......but I used this method at first only ....now this also not working...
now I got more big trouble...
I m only s-off and bootloader is relocked and have no root so can't flash any recovery......
I I tried unlock_bin token cmd says sending token(0 bytes) successful but bootloader do not show anything........what should I do noww...
jaspreet4140 said:
hy nykk again.......thx for reply......but I used this method at first only ....now this also not working...
now I got more big trouble...
I m only s-off and bootloader is relocked and have no root so can't flash any recovery......
I I tried unlock_bin token cmd says sending token(0 bytes) successful but bootloader do not show anything........what should I do noww...
Click to expand...
Click to collapse
okay, but first, can you please relax!!
after you relax, please post your current "fastboot getvar all" (excluding IMEI and s/n), and if you are S-Off, we'll have you unlocked pretty quickly
but you have to relax!! otherwise you're going to rush things and make a mistake.
re
bootloader 1.54.0000
baseband. 4A.17.3250.14
cpld: none
microp:none
main:2.24.980.3
pvt ship s-off
meid:00000000000000
product:m7_ul
HBOOT-8064
midN0714000
cid:11111111
securityff
jaspreet4140 said:
bootloader 1.54.0000
baseband. 4A.17.3250.14
cpld: none
microp:none
main:2.24.980.3
pvt ship s-off
meid:00000000000000
product:m7_ul
HBOOT-8064
midN0714000
cid:11111111
securityff
Click to expand...
Click to collapse
1- that's not a copy/paste you typed that stuff ... (see screenshot for copy/paste on windows)
2- are you relaxed now?
3- next time, please quote me, or mention me using @nkk71 to get my attention, otherwise I may not read the post
4- are you relaxed now
5- to get unlocked:
Since you are S-Off, use a custom recovery masked in a firwmare package: you can use of these "firmware" packages (m7_u/ul only):
http://www.androidfilehost.com/?w=files&flid=13085
fastboot oem rebootRUU
fastboot flash zip fw_m7ul_TWRP_2.6.3.3_1.26.401.33.zip
fastboot reboot-bootloader
-> enter RECOVERY (should be TWRP or CWM now)
and use @scotty1223's commands in custom recovery http://forum.xda-developers.com/showthread.php?t=2475914 to unlock bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
[SIZE="1"][I][U]Note[/U]
CWM shell prompt usually looks like [B]~#[/B]
TWRP shell prompt usually looks like [B]~ # ←[6n[/B]
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue
[/I][/SIZE]
[I][SIZE="1"]Setting UNLOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
^^ if this doesn't work in your particular version, just select reboot to bootloader in TWRP.
ps: your version-main will now say 1.26.401.33 (reflecting the recovery version 2.6.3.3); it didn't actually change, but version-main always show the last thing flashed in ruu mode.
6- careful on what you flash/install etc. you're doing quite a few mistakes... and rushing things.... so please be careful!!
.
re
ya I m relaxed......thx for concern....
but I can't download ur files using pc.....how to download them I enabled javascript also using mozilla
tnxx
ok done...thxxx nkk71 again greate helpp.........
ree
nkk71 now everything is back to normal except a small thing....TAMPERED is not going I used scotty command ,revone tool and guru bootloader ...none is helpful......others are working good I.e I m able to relock ,unlock,lock bootloader but not tampered.........it worked at first time but when I unlocked it came again n now its not going.....
can u get ur magic sword on this one
jaspreet4140 said:
nkk71 now everything is back to normal except a small thing....TAMPERED is not going I used scotty command ,revone tool and guru bootloader ...none is helpful......others are working good I.e I m able to relock ,unlock,lock bootloader but not tampered.........it worked at first time but when I unlocked it came again n now its not going.....
can u get ur magic sword on this one
Click to expand...
Click to collapse
you need to use @nkk71 (ie @ then nkk71, no spaces) not just nkk71 for me to get notified
and scotty's command should work just fine, maybe you're mistyping them or not in su mode? reboot to custom recovery, then
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
[SIZE="1"][I][U]Note[/U]
CWM shell prompt usually looks like [B]~#[/B]
TWRP shell prompt usually looks like [B]~ # ←[6n[/B]
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue
[/I][/SIZE]
[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
^^ if this doesn't work in your particular version, just select reboot to bootloader in TWRP.
copy/paste (no screenshot, a real copy/paste please) your command prompt output (all of it) if it still fails.
PS: oh and is it going, but coming back or just not going away?
.
rom
can anyone suggest me a latest non sense based ROM for htc one which has some cool features like multi tasking ,double tap or slide up unlock.......
sorry for late replying @nkk71 .my exams were going on..........and tampered was gone for first time only and now it: s not going and I m using scotty cmd with su mode in usb debugging...
jaspreet4140 said:
sorry for late replying @nkk71 .my exams were going on..........and tampered was gone for first time only and now it: s not going and I m using scotty cmd with su mode in usb debugging...
Click to expand...
Click to collapse
try the commands while booted into custom recovery (and there's no need to 'su' in custom recovery as it already should give you a root shell:
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
[SIZE="1"][I][U]Note[/U]
CWM shell prompt usually looks like [B]~#[/B]
TWRP shell prompt usually looks like [B]~ # ←[6n[/B]
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue
[/I][/SIZE]
[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
^^ if this doesn't work in your particular version, just select reboot to bootloader in TWRP.
remember to copy/paste that command, even something as small as an extra/missing <space>, can make it not work.
if it still doesn't work, you'll have to do as @scotty1223 mentioned in his thread (under the section "if this does not work for you"): http://forum.xda-developers.com/showthread.php?t=2477792
don't just say it doesn't work, you need to provide him with:
1) a copy/paste of "fastboot getvar all"
2) a copy/paste of your command prompt output
3) your mmcblk0p7
though I don't think I've ever seen a post that said this doesn't work (unless the command is mistyped)
.
Hi,
as I made a stupid mistake while trying to fix Clockworkmod Recovery boot loop issue and didnt read the guide carefully, I bricked my phone with:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
the phone/mmcblk0p3 is dead now and I'm doing research to unbrick via JTAG (using BusBlaster/BusPirate/Arduino), no Riffbox-like stuff) can someone please send me a copy of the mmcblk0p3 e.g. doing a:
dd if=/dev/block/mmcblk0p3 of=/path/to/copy bs=1
Thank you in advance.
hey gus i have unlocked my 9060 by this method and its pretty easy(Thanks to its creators).........and the best part is that u dont have lose any data from ur phone .................(ur device must be S-off)
this method is imported from my old phone desire 601 ..........credit:
@scotty1223 thanks
u just have to do this .......
first go to this site and do as he say...... and install the adb to ur pc.........credit goes to @Snoop05
and then just open this (adb.zip) and download it ......
extract it to short path like:--- C:\.
now open the command prompt where u have extracted (press the left shift in that extracted folder and right click and click open command prompt) or locate to the folder
Now u just have to unlock ......
type adb shell (in the command prompt)
type su
type or paste echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
****i advice copy and past****
type exit
type exit
type adb reboot bootloader (for checking its position *****unlocked***** )
type fastboot reboot ( to back in os)
hey @rajat ,can u give me the stock systemUI.apk 4.2.2 9060 ,,,,,it's urgent....thanks in advance
thanks for the new method. can i try this with my htc one m7?
goodman_east said:
thanks for the new method. can i try this with my htc one m7?
Click to expand...
Click to collapse
u can but u have to change this line only the main code.........................
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
cause m7 memory partition is different from zara
else is same .............and btw what m7 u have is it china 802t.............
Good
goodman_east said:
thanks for the new method. can i try this with my htc one m7?
Click to expand...
Click to collapse
Great job
rajat836 said:
hey gus i have unlocked my 9060 by this method and its pretty easy(Thanks to its creators).........and the best part is that u dont have lose any data from ur phone .................(ur device must be S-off)
this method is imported from my old phone desire 601 ..........credit:
@scotty1223 thanks
u just have to do this .......
first go to this site and do as he say...... and install the adb to ur pc.........credit goes to @Snoop05
and then just open this (adb.zip) and download it ......
extract it to short path like:--- C:\.
now open the command prompt where u have extracted (press the left shift in that extracted folder and right click and click open command prompt) or locate to the folder
Now u just have to unlock ......
type adb shell (in the command prompt)
type su
type or paste echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
****i advice copy and past****
type exit
type exit
type adb reboot bootloader (for checking its position *****unlocked***** )
type fastboot reboot ( to back in os)
Click to expand...
Click to collapse
What is the use unlock ?
How I can make the S - OFF?
Thanks for the input.