This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
{
"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"
}
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here http://forums.team-nocturnal.com/showthread.php/3162
One more for future use
XsMagical said:
One more for future use
Click to expand...
Click to collapse
Appreciate your contrbution
Do this only if you want to change the partition 19 cid. We do not know why HTC has a cid there and we do not know why getprop ro cid shows it.
Right now there is no reason for it.
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
Worked perfect! Thank you sir. So I can go over to the Sprint forums and grab ViperRom per se and flash it to my AT&T version no problem?
Sent from my HTC One using xda app-developers app
Do we reckon this will work on HTC sensation xe??
Sent from my HTC Sensation Z715e using xda app-developers app
Does not work on my AT&T HTC one.....
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
hyelton said:
Does not work on my AT&T HTC one.....
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Click to expand...
Click to collapse
If your S-OFF all I did was boot to the bootloader
plug in phone usb wait for fastboot USB
then from PC where you have fastboot shift/right click cmd window here then run - fastboot oem writecid 11111111
reboot bootloader to see the change.
if you want to revert back to your carrier CID theirs a list of them here -> http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
clsA said:
If your S-OFF all I did was boot to the bootloader
plug in phone usb wait for fastboot USB
then from PC where you have fastboot shift/right click cmd window here then run - fastboot oem writecid 11111111
reboot bootloader to see the change.
if you want to revert back to your carrier CID theirs a list of them here -> http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
Click to expand...
Click to collapse
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
hyelton said:
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
Click to expand...
Click to collapse
this is what I used - I'm at&t
http://forum.xda-developers.com/showthread.php?t=2314582
I have already returned my CID to AT&T stock as I have no intentions of flashing a RUU anytime soon ..just waiting on ARHD 10.2 now
hyelton said:
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
Click to expand...
Click to collapse
The revone method works flawlessly with the AT&T version, that's what I used. Didn't try the other method so I don't know but revone definitely works.
barondebxl said:
The revone method works flawlessly with the AT&T version, that's what I used. Didn't try the other method so I don't know but revone definitely works.
Click to expand...
Click to collapse
Thats what I have been trying for the past HOUR!!!!
It fails everytime!
C:\sdk>adb push revone /data/local/tm
3413 KB/s (646704 bytes in 0.185s)
C:\sdk>cd /data/local/tmp
The system cannot find the path speci
C:\sdk>adb shell
[email protected]:/ # su
su
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod
chmod 755 revone
[email protected]:/data/local/tmp # ./revo
./revone -P
Failed (please reboot and try again!)
revone failed (error code = -6
250|[email protected]:/data/local/tmp #
hyelton said:
Thats what I have been trying for the past HOUR!!!!
I cant get past step 1... I can do ADB shell, Then ADB devices to make sure the device is there and it SHOWS UP, Then I do adb push revone /data/local/tmp/ and BAM no devices found...
SO now what??
Click to expand...
Click to collapse
Here is a video tutorial. Its not the best video around as the guy was trying to do it for the first time as well but it will help you. Make sure you make the youtube video 720p or 1080p full screen otherwise you wont see sh*t. Do the same hing as he does and pause the video when you need to. If you have more question you can pm me.
http://www.youtube.com/watch?v=YYb_Cz5rPIU
hyelton said:
Thats what I have been trying for the past HOUR!!!!
Click to expand...
Click to collapse
are you on a stock kernel ? you can also do it from the device itself
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
hyelton said:
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
Click to expand...
Click to collapse
error -6 means your not on stock kernel ?
hyelton said:
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
Click to expand...
Click to collapse
Keep trying, the tutorial says if it doesn't go through reboot and keep trying. Worked for the 1st attempt for me but others had to try several times.
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
hyelton said:
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
Click to expand...
Click to collapse
Are you SuperCID ?
did you use this script or the fastboot commands ?
hyelton said:
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
Click to expand...
Click to collapse
Congrats! Now get Super CID.
Related
Hello!
So since I had a sensation before the Amaze, I remembered that once we got S-Off, a next step was to obtain SuperCID on the phone. Basically, having SuperCID allows you to flash any ROM, regardless of which carrier it is for. Pretty handy if you have your phone SIM unlocked and wanted to use your Amaze on Wind Mobile or something. Anyway, the steps are from this thread (http://forum.xda-developers.com/showthread.php?t=1192300) and original credit goes to "xl VipeR lx" for the Sensation write up.
The usual warning goes here. I'm not responsible for what you do, use this at your own risk!
Required - You MUST have your phone S-Off from Juopunutbear's method first! Go here for that: http://forum.xda-developers.com/showthread.php?t=1611977
Also, if you've upgraded to ICS, the 1.93.0002 SHP Hboot is required to SuperCID!
--------------------------------------
ATTENTION:
It appears that the ICS update changes the firmware of the phone a bit. This means that using any bootloader other than SHP 1.93.0002 will remove your ability to write SuperCID to your device. This includes the ENG bootloader. It makes no different if you're locked/unlocked and S-OFF, the command doesn't work without being on the proper HBoot. Unfortunately, being on 1.93.0002 also removes your ability to flash partitions directly in Fastboot (ie. fastboot flash recovery, fastboot flash radio, etc) and you must revert to ENG 1.90.2005 in order to use fastboot flash commands.
--------------------------------------
The process is very simple and exactly the same as the Sensation and most S-Off HTC devices:
1. Command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
2. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings)
3. Enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
4. Enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
IF it doesn't you can Manually put the phone in the bootloader/hboot mode
Navigate to fastboot by pressing volume down and pressing power button to select (power off > vol down + power on)
It will take you to the fastboot bootloader screen on your phone
Connect your phone via USB
Your Screen should now read fastboot USB
5. Enter the command "fastboot oem writecid 11111111"
6. Enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
7. Enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
8. Enter the command "fastboot reboot"
9. You can now flash any ROM you like.
{
"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"
}
To remove SuperCID and return to stock CID:
1. Follow steps 1-4 for SuperCID
2. Enter the command "fastboot oem writecid __________" <--- Here you will put either T-MOB010 (T-Mobile), TELUS001 (Telus), GLOBA001 (Wind Mobile Canada)
3. Enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
4. Enter the command "fastboot getvar cid" [it should confirm your CID has changed]
5. Enter the command "fastboot reboot"
6. You are now back on stock CID (for your carrier)
****If you like the automated route, benjamminzIs has provided two batch files, one for SuperCID (for all devices) and one for reverting to stock (T-Mobile only). Place them in your SDK/tools folder and run them!****
I'll write two .bat scripts for you soon
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
I'll write two .bat scripts for you soon
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
If you are on another operator such as wind, you might want to do a "fastboot getvar cid" and take note of what your cid is, or even post it on here as a reference just in case anyone wants to revert.
hhilton said:
If you are on another operator such as wind, you might want to do a "fastboot getvar cid" and take note of what your cid is, or even post it on here as a reference just in case anyone wants to revert.
Click to expand...
Click to collapse
Thanks, updated. If anyone has a Wind device and knows what the CID is, I'll add it for reference.
benjamminzIS said:
done...
here: DOWNLOAD
place these in SDK/tools folder and run them...
Click to expand...
Click to collapse
Thanks, attached to main post with credit
Here are my scripts. No need to put it in the SDK folder. Just extract and run it!
electronicrice said:
Thanks, attached to main post with credit
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
benjamminzIS said:
use this version instead: http://www.mediafire.com/?igjxm0t3xv1u9y7 updated and now no need to extract to a certain folder, different method than hasoon's though as far as the script goes...
Click to expand...
Click to collapse
Basically the same. You just push the .CID rather than writing them.
hasoon2000 said:
Basically the same. You just push the .CID rather than writing them.
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
benjamminzIS said:
use this version instead: http://www.mediafire.com/?igjxm0t3xv1u9y7 updated and now no need to extract to a certain folder, different method than hasoon's though as far as the script goes...
Click to expand...
Click to collapse
That's okay, I'm just using your original batch files with a couple prompt edits, and bundling it with ADB. Should work fine for the majority of people. Otherwise, people can use the other method you have linked as far as automation goes. The manual commands will always work.
electronicrice said:
That's okay, I'm just using your original batch files with a couple prompt edits, and bundling it with ADB. Should work fine for the majority of people. Otherwise, people can use the other method you have linked as far as automation goes. The manual commands will always work.
Click to expand...
Click to collapse
hey, it's your thread, I just figured since I had been making some drag and drop scripts for the splash screen, I may as well make this one just as simple... heh... I wasn't trying to step on anyones toes...
benjamminzIS said:
hey, it's your thread, I just figured since I had been making some drag and drop scripts for the splash screen, I may as well make this one just as simple... heh... I wasn't trying to step on anyones toes...
Click to expand...
Click to collapse
no not at all. everything's great here. we have s-off. mood couldn't be better. =]
Thanks for this post. Just for understanding - what does SuperCID do for the Amaze, that couldn't be done before?
Thanks, for reference
Code:
cid: TELUS001
For reference as well, Wind Mobile Canada
Code:
cid: GLOBA001
Worked like a charm Thanks
Opentang said:
Thanks for this post. Just for understanding - what does SuperCID do for the Amaze, that couldn't be done before?
Click to expand...
Click to collapse
Yeah it's in the OP but basically it allows you to flash to any carrier's official ROM for the Amaze. So if you have a T-Mobile Amaze and you wanted to flash the RUU for Telus or Wind, you can with SuperCID.
In the past, the RUU has to be hacked to allow a flash on a non-carrier specific device, and this allows you to bypass that entirely.
MentalDeath said:
Thanks, for reference
Code:
cid: TELUS001
Click to expand...
Click to collapse
idaggerpwn said:
For reference as well, Wind Mobile Canada
Code:
cid: GLOBA001
Click to expand...
Click to collapse
Great, thanks guys, updated the OP
updated the DnD_SuperCID here: DOWNLOAD. (PLEASE DON'T QUOTE THIS POST!!!)
I give credit to DesignGears for finding this for the HTC One X. So be sure to give him thanks for his find!
SuperCID will allow ruu'ing back and forth from newer to older builds and vice versa.
ADDED- WILL NOT ALLOW FLASHING OF RUU WITH OLDER HBOOT VERSIONS.
Added- great explanation of supercid benefits http://forum.xda-developers.com/showthread.php?t=1548083
Please follow the instructions VERY carefully as any error in the process can and very easily WILL BRICK YOUR DEVICE. I am in no way recommending this procedure and am not responsible for any device damaged from the following guide.
It's not very difficult if you just follow instructions, so don't be discouraged from the warnings, just pay attention
Pre-requisites -
Rooted HTC EVO 4g LTE
Pc with working HTC drivers
Adb and general knowledge of use
Fastboot and general knowledge of
use.
USB debugging enabled
A hex editor on your pc for modifying the partition we are going to pull(HxD is free on cnet)
2ND WARNING-
This procedure will be modifying a partition and pushing it back to device. If modified incorrectly it WILL BRICK your device.
Plug device into pc and select charge only on the device
Open up your command prompt and cd to your folder with adb and fastboot.
Type -
adb shell
Su
You should now see
"[email protected]: #"
Next we are going to take a copy of partition and save to the external sdcard
Type -
dd if=/dev/block/mmcblk0p4 of=/sdcard2/mmcblk0p4
Hit enter, should get a readout of
2+0 records in
2+0 records out
You now have a copy of partition 4 saved on external sd.
Type - exit, then exit again and you should now be in your fastboot/adb dir. In your command prompt. Minimize the window don't close, we'll be right back.
Now mount your phone as disk drive and open your sdcard on your pc. You will see a file on it named mmcblk0p4. Copy and paste a copy to your pc desktop.
Once copied, right click and go to properties, and WRITE DOWN THE SIZE OF THE FILE,
Should be 1,024 bytes.
after we modify the partition the modified one must be IDENTICAL in size or there's 100% chance of brick when push it back to the device.
Now, open the file mmcblk0p4 in your hex editor
Scroll to offset 00000210, you will see
"...SPCS_001XXXX" X's being 4 numbers we arent going to touch.
ANOTHER WARNING-
Here's where you need to be extremely careful,
we are going to change
"SPCS_001" to. "11111111"
best way to do this is highlight ONLY "SPCS_001" then press "1" eight times, so your replacing 8 characters with eight 1's. Now the full line looks like
"...11111111xxxx".
Three dots before the "1" and four numbers after the last "1". Most likely being 9900.
ADDED- Pic of b4 and after hex edit
http://db.tt/ziScPZBl
Now go to >file>save as and name the file mmcblk0p4MOD and save it to desktop.
Open your external sdcard folder again on pc and put a copy of your new mmcblk0p4MOD in there. Right click it, properties and verify it is the same size as the original. Go back and mount phone as charge only.
14th WARNING:
Hope u followed closely, if you made a mistake here's where u brick!
Maximize your command prompt window from earlier and type-
adb shell
Su
You'll be back at the [email protected] command prompt
Type-
dd if=/sdcard2/mmcblk0p4MOD of=/dev/block/mmcblk0p4
Hit enter and you should get the same readout from before-
2+0 records in
2+0 records out
Your all done, now to confirm you have superCID type exit, then exit again then
Adb reboot bootloader
Once in bootloader type-
Fastboot oem readcid
Readout should say
INFOcid: 11111111
Confirmed, you were successful. You SHOULD now be able to run any ruu a available for the device, enjoy and don't forget to hit THANKS
Sorry if all the warnings are annoying but I don't want any "you bricked my phone, help!" Posts
So this would benefit those who took the OTA while they were S-on (on accident) and want to be S-off now?
Sent from my EVO using xda app-developers app
I had 4 dots before the first 1
I haven't followed closely to the new ota problems, but if they can still root after the ota, then yes they should be able to ruu back to the previous firmware.
Good, Bad and EVO
As long as you replace the 8 characters with eight 1's you will be fine. will post a b4 and after pic of the hex edit in OP,
Pic Added!!
Good, Bad and EVO
This is fascinating. Thanks for bringing it to us, I'm sure this will help a couple people out.
This is interesting.
I wonder if this would allow me to RUU back to the 1.13 ROM? The error I got was due to the HBOOT version being too old. Would SuperCID somehow allow this?
I guess there's only one way to find out . . .
This should allow you to ruu, any firmware for the device
Good, Bad and EVO
18th.abn said:
This should allow you to ruu, any firmware for the device
Good, Bad and EVO
Click to expand...
Click to collapse
Well, great instructions & walkthrough. I was able to do this painlessly.
Now I'm trying to flash an RUU. Let's see what happens!
Added a link in op that explains well the benefits of supercid
Good, Bad and EVO
is it wrong that I love you? I had to get a new lte from sprint and the guy there did the ota as part of activation. happy there is a way back
18th.abn said:
Added a link in op that explains well the benefits of supercid
Good, Bad and EVO
Click to expand...
Click to collapse
Well, here's the result:
{
"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"
}
Looks like the 1.15 HBOOT is SuperCID-proof .
It's the same error I got when I tried to flash the PJ75IMG. The main version wasn't an issue, but the HBOOT version apparently prevents the RUU from running.
Dang, sorry its not letting you. Supercid let's all cid verifications pass allowing flashing of any firmware, but I guess if it has a older hboot, it kills the deal. Will edit op that it won't downgrade hboot versions.
Good, Bad and EVO
So if I understand this correctly since we took the ota and have the new hotboot with s-on we still screwed for now. has anyone tried to run the lazy panda after doing this on the post supercid current hotboot
rockin my EVO 4G LTE
Yes, seems that way. Click the link in op about benefits of supercid. It explains it really well.
Good, Bad and EVO
motcher41 said:
So if I understand this correctly since we took the ota and have the new hotboot with s-on we still screwed for now. has anyone tried to run the lazy panda after doing this on the post supercid current hotboot
rockin my EVO 4G LTE
Click to expand...
Click to collapse
That would be me, two posts up.
Captain_Throwback said:
That would be me, two posts up.
Click to expand...
Click to collapse
Didn't see anything about lazypanda saw it was ruu proof still. But I guess that must be a yes we screwed still. I never take ota updates but never thought soff woulda been locked worse then before Thanks for the info
rockin my EVO 4G LTE
Has the new ota hboot blocked lazy panda? Is this confirmed?
{ParanoiA} said:
Has the new ota hboot blocked lazy panda? Is this confirmed?
Click to expand...
Click to collapse
Yes, confirmed. The lazy panda dev's are working on an updated tool.
Once again, this is why you NEVER accept an OTA while rooted or planning to root.
I understand captn took one for the team here, but everyone else shame on you.
:fingerwag:
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if you accidentally unlocked your bootloader after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for warranty purposes,without having to s-on and re-s off.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal rezound.
query:http://www.mediafire.com/download.php?jg8v4ady8nyc8bu
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:http://www.mediafire.com/download.php?il51rl2j1m8417b
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:http://www.mediafire.com/download.php?05ow9uhw540p6jy
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
{
"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"
}
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
If your S-off and run the global RUU , your Hboot will say "locked" and not "relock". That's what mine says anyway.
mclass55 said:
If your S-off and run the global RUU , your Hboot will say "locked" and not "relock". That's what mine says anyway.
Click to expand...
Click to collapse
you were locked in the first place. running ruus does not change the lock status flag. ive run it several times as unlocked(along with may other ruus)
Nice find my friend
Sent from my ADR6425LVW using xda app-developers app
There are several modified (hexedited) HBoots in these forums that you can flash and they can say basically whatever you want them to say. I'm S-Off but mine says S-On Locked, IIRC. Have not been in recovery in a while to look.
Here: http://forum.xda-developers.com/showthread.php?t=1853871
ClockerXP said:
There are several modified (hexedited) HBoots in these forums that you can flash and they can say basically whatever you want them to say. I'm S-Off but mine says S-On Locked, IIRC. Have not been in recovery in a while to look.
Here: http://forum.xda-developers.com/showthread.php?t=1853871
Click to expand...
Click to collapse
Yea, but this is for the people who dont want to change the bootloader and want to keep it stock, but want it locked aswell.
Nice find, imma run it thanks!
Sent from my ADR6425LVW using xda app-developers app
ClockerXP said:
There are several modified (hexedited) HBoots in these forums that you can flash and they can say basically whatever you want them to say. I'm S-Off but mine says S-On Locked, IIRC. Have not been in recovery in a while to look.
Here: http://forum.xda-developers.com/showthread.php?t=1853871
Click to expand...
Click to collapse
using a patched hboot is IMO,a fraudulent way to sent your phone in for warranty. it may make it back out into circulation in this manner,and casue issues for the next users.
patched hboot is fine for a trip to the vzw store if youre paranoid about a vzw empooyee checking your hboot,but its so easy now to to return the phone to 100% out of the box stock i have no idea why anyone would not do it.
I am s-on and back to factory.. But RELOCKED status.. Can I rename the lock zip and flash in bootloader?
Sent from my ADR6425LVW using xda app-developers app
dudebro0325 said:
I am s-on and back to factory.. But RELOCKED status.. Can I rename the lock zip and flash in bootloader?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Unfortunately,no. Mmcblk0p3 is write protected while s on. At this point ,you will need to re-s off(which will also reset the lock flag)
Even if you were s off,this can ONLY be flashed via recovery. Its not something hboot can install.
Sent from my ADR6425LVW using xda app-developers app
scotty1223 said:
you were locked in the first place. running ruus does not change the lock status flag. ive run it several times as unlocked(along with may other ruus)
Click to expand...
Click to collapse
I have unlocked, relocked and run the Global RUU many times and it returns me back to "Locked" also I am S-off and couldn't get that by being locked to start with
mclass55 said:
Take a look at my picture.It says the same thing as yours. I have unlocked, relocked and run the Global RUU many times and it returns me back to "Locked" also I am S-off and couldn't get that by being locked to start with
Click to expand...
Click to collapse
The s off jpbear tool reset your lock flag. Go ahead and unlock,Relock,and run your ruu again.
Running ruus will NOT changed your relocked to locked
Sent from my ADR6425LVW using xda app-developers app
scotty1223 said:
The s off jpbear tool reset your lock flag. Go ahead and unlock,Relock,and run your ruu again.
Running ruus will NOT changed your relocked to locked
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Maybe I am missing something about your post. What's the difference between my Hboot screen and yours? If the jpbear tool resets lock flag, why do we need the fix that was posted? And the only way to get S-off is by using jpbear to start with.
Sorry, not trying to start anything, but I am not seeing the need for this
scotty1223 said:
Unfortunately,no. Mmcblk0p3 is write protected while s on. At this point ,you will need to re-s off(which will also reset the lock flag)
Even if you were s off,this can ONLY be flashed via recovery. Its not something hboot can install.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
mclass55 said:
Maybe I am missing something about your post. What's the difference between my Hboot screen and yours? If the jpbear tool resets lock flag, why do we need the fix that was posted? And the only way to get S-off is by using jpbear to start with.
Sorry, not trying to start anything, but I am not seeing the need for this
Click to expand...
Click to collapse
Because some people have unlocked their bootloader after s-off without realizing there was no need.
mclass55 said:
Maybe I am missing something about your post. What's the difference between my Hboot screen and yours? If the jpbear tool resets lock flag, why do we need the fix that was posted? And the only way to get S-off is by using jpbear to start with.
Sorry, not trying to start anything, but I am not seeing the need for this
Click to expand...
Click to collapse
This tool is for people who have already S-OFF'd and then subsequently unlocked (like me). In the event that I want to sell my Rezound, this makes it easy: I run an RUU, flash this zip, and fastboot oem write secureflag 3 to return to S-ON. Conversely, without this tool, after flashing the RUU I'd have to S-ON, run JuopunutBear S-OFF again (which is just a hassle to have to do more than once, with the paperclip and all), then re-S-ON.
It just makes things a little simpler, and I'm grateful for it. Nice find, scotty.
El Schisne said:
without this tool, after flashing the RUU I'd have to S-ON, run JuopunutBear S-OFF again (which is just a hassle to have to do more than once, with the paperclip and all), then re-S-ON.
Click to expand...
Click to collapse
After S-off and flashing the Global RUU, I have never ever, S-on or rerun the S-off jpbear again , And my Hboot looks the same as the original poster's Hboot
mclass55 said:
After S-off and flashing the Global RUU, I have never ever, S-on or rerun the S-off jpbear again , And my Hboot looks the same as the original poster's Hboot
Click to expand...
Click to collapse
Not sure how to say this any simpler than this: If you run HTCDev unlock after you are S-OFF, you will get the relocked status if you relock your bootloader. If you don't unlock with HTCDev unlock, you won't. This is for people who have HTCDev unlocked after S-OFF
mclass55 said:
After S-off and flashing the Global RUU, I have never ever, S-on or rerun the S-off jpbear again , And my Hboot looks the same as the original poster's Hboot
Click to expand...
Click to collapse
Because jpbeat reset your lock flag for you,and you have not re-unlocked.
Sent from my ADR6425LVW using xda app-developers app
What about the TAMPERED flag?
MajikUF said:
What about the TAMPERED flag?
Click to expand...
Click to collapse
Once you're s off you won't see the tampered banner. Even if you're s on,it will go away naturally when you relock and run a signed ruu
Sent from my HTC Flyer P510e using xda app-developers app
update 6/12:
Windows support added. Check moonshine.io for windows download. Important windows notes:
1.) make sure htc sync is uninstalled
2.) make sure adb and fastboot drivers are working
3.) make sure htc sync is uninstalled
4.) if you are having problems with fastboot, try a usb 2.0 port.
5.) make sure htc sync is uninstalled
6.) make sure other programs that interfere with adb and fastboot are uninstalled (PDANet, Kies, etc.)
7.) make sure htc sync is uninstalled
8.) if you use a third party firewall, be sure to grant access to distiller.exe as it checks for updates
9.) MAKE SURE HTC SYNC IS UNINSTALLED
10.) YOU MUST UNZIP THE ARCHIVE BEFORE RUNNING DISTILLER. DO NOT JUST TRY TO RUN IT FROM THE ARCHIVE.
Welcome to moonshine s-off for the HTC Droid DNA. Developed by Fuses, beaups, and Hyuh. Enjoy.
Downloads available at: http://moonshine.io
You MUST upgrade to 2.06 fw first. To do this, download 2.06 firmware here. https://dl.dropboxusercontent.com/u/9060692/dna2.06firmware.zip Then:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip dna2.06firmware.zip
fastboot reboot-bootloader
IMPORTANT! Then, choose "power off" in fastboot menu
Just ran this. S-OFF ACHIEVED. Thanks so much beaups
Massive Kudos, my friend.
beaups said:
Welcome to moonshine s-off for the HTC Droid DNA. Developed by Fuses, beaups, and Hyuh. Enjoy.
http://moonshine.io
You MUST upgrade to 2.06 fw first. To do this, download 2.06 firmware here. https://dl.dropboxusercontent.com/u/9060692/dna2.06firmware.zip Then:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip dna2.06firmware.zip
fastboot reboot-bootloader
IMPORTANT! Then, choose "power off" in fastboot menu
Click to expand...
Click to collapse
You are the best! Can you comment on revone and it's suspicious release?
Sent from my HTC Droid DNA using xda app-developers app
Outstanding, worked like a charm! Thank you too everyone who worked on this!
Sent from my HTC6435LVW using Tapatalk 4 Beta
nice one!
This is probably the easiest s-off/unlock/root method I've ever used. You literally plus your device in, run the executable, and it does everything for you. Great job on this!
beaups said:
Welcome to moonshine s-off for the HTC Droid DNA. Developed by Fuses, beaups, and Hyuh. Enjoy.
http://moonshine.io
You MUST upgrade to 2.06 fw first. To do this, download 2.06 firmware here. https://dl.dropboxusercontent.com/u/9060692/dna2.06firmware.zip Then:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip dna2.06firmware.zip
fastboot reboot-bootloader
IMPORTANT! Then, choose "power off" in fastboot menu
Click to expand...
Click to collapse
Your are the MAN!!!! All bow to lord beaups!
beaups said:
Welcome to moonshine s-off for the HTC Droid DNA. Developed by Fuses, beaups, and Hyuh. Enjoy.
http://moonshine.io
You MUST upgrade to 2.06 fw first. To do this, download 2.06 firmware here. https://dl.dropboxusercontent.com/u/9060692/dna2.06firmware.zip Then:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip dna2.06firmware.zip
fastboot reboot-bootloader
IMPORTANT! Then, choose "power off" in fastboot menu
Click to expand...
Click to collapse
FYI, a few typos on the instructions page.
e.g. "USB 3.0 ports are know to casue connectivity problems"
I'm a bit new to using a Live CD. The instructions say don't download Moonshine to the Windows drive. Will it install there by default or how should I go about this? Thanks for the help.
Sent from my HTC6435LVW using Tapatalk 2
S-OFF achieved!!! Thank you so much guys!
Just a little heads up - may be good to let people know that this will install SuperSU so they don't try and flash another Superuser/SuperSU JIK.
Backing up with CWM right now... sooooo pretty!
Thanks! Now to go celebrate! Excited to get this working when I get back!
Has anyone tried on 64-bit? I'm about to and was wondering if anyone hit any problems
swimminsurfer256 said:
Has anyone tried on 64-bit? I'm about to and was wondering if anyone hit any problems
Click to expand...
Click to collapse
I'm running it now with 32-bit libraries installed using Ubuntu 12.10 distribution.
EDIT: Just finished. It worked:
{
"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"
}
---------- Post added at 08:04 PM ---------- Previous post was at 07:44 PM ----------
And what I can't figure out is why this thread hasn't been swamped with comments... Kind of eerie given the pre-release buzz. Definitely donating now. Go, team!
gave me a failed notice after trying to gain temp root....any ideas?Test 1: Rebooting into bootloader
Waiting for fastboot (9/60)
Waiting
Test 2: Booting device
Waiting for ADB (18/60)
Device detected.....................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (9/60)
Waiting for ADB (16/60)
Waiting for device
Waiting for device
Launching temproot
Sleeping 10 sec
ERROR: temproot failed
not excellent with linux by any means....
I'm clueless when it comes to Linux how do I execute the distiller? I've double clicked and nothing...
Sent from my HTC6435LVW using xda app-developers app
bring up terminal
cd ~/Downloads
sudo ./distiller
this will ask password enter it now
and blam s-off
an beaups you guys are amazing i will be needing this monday my new dna will be here.
my og dna broke in half sadness 2 weeks no phone...
Just wanted to say thanks again to beaups(facepalm s-offer) for doing what he does. Surely hope most didn't jump ship to the other method (loved the post over there too lol) since hes been so loyal to us, and waded through all the bs posts from people that only listen to their inner child. Everyone join us in truly owning your phone, and please donate to this man, esp if you posted you would. Don't know him personally, but definitely a man I would hug.(notgay)
Droid DNA S-off Viper 1.3 TT2
cstrife999 said:
I'm clueless when it comes to Linux how do I execute the distiller? I've double clicked and nothing...
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Do I need something else installed? Running Ubuntu 32 bit.
---------- Post added at 08:17 PM ---------- Previous post was at 08:15 PM ----------
t1gartist said:
bring up terminal
cd ~/Downloads
sudo ./distiller
this will ask password enter it now
and blam s-off
an beaups you guys are amazing i will be needing this monday my new dna will be here.
my og dna broke in half sadness 2 weeks no phone...
Click to expand...
Click to collapse
I'm sorry in advance but this is the first time I've used linux... lowering my head now... Where is terminal?
Tip here. If your unsure of what your doing wait until someone makes a tutorial for you to follow or a video. Be patient it will happen. It's better than having a bricked device because you don't know what your doing.
Sent from my HTC6435LVW using xda premium
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
EDIT - I sort of solved it myself in post #7
sminki said:
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
Click to expand...
Click to collapse
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
piskr said:
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
Click to expand...
Click to collapse
Not on these. That the first thing I tried. That gives
Code:
FAILED (remote: Command not allowed)
Which is essentially "command not found", as you can pass it any garbage and that's what it gives back.
As I see it, you can't install updates with an unlocked bootloader (unless I'm wrong, or there is something desperately wrong with my phone). With no custom roms (at the moment) this is all we have
EDIT:
Looks like I was wrong about updates on unlocked bootloader. I went back to B100 (UK) then back up to B121
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
t-ph said:
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
Click to expand...
Click to collapse
I haven't retried yet. I was still in my 14 day return period and was undecided if I was going to keep the phone
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried it on B100?
Have you tried it on B140?
Have you tried "oem lock" instead of "oem relock"?
Note: Always mention your model number in your thread title and description. Not all different models behave the same and not all updates give the same error message.
Thank you for opening this thread. We hope to read your answers on the above questions to help you.
kenshiwara said:
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried "oem lock" instead of "oem relock"?
Click to expand...
Click to collapse
I have the EU Version PLK-L01 16GB
..and yes I had, see my second post - lock doesn't seem to be a valid Huawei boot-loader command.
I've had a busy and incredibly boring time trying to sort this out.. Somehow, I re-locked :victory:
{
"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"
}
Unfortunately from the point of view of returning the device to Huawei, Re-locked is not the same as Locked, but it's all I have found.
After TWRP format:
Code:
sudo fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: images signature check fail)[/COLOR][/B]
finished. total time: 1.048s
After B100 Downgrade:
Code:
fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: root type is risk)[/COLOR][/B]
finished. total time: 0.970s
I re-flashed the UserData image from B100, after booting up I got this:
After UserDate Wipe:
Code:
fastboot oem relock 1111111111111111
...
OKAY [ 1.985s]
finished. total time: 1.985s
fastboot oem get-bootinfo
...
(bootloader) [COLOR="Green"]relocked[/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
So basically, I re-locked with a completely fresh, untouched system and a "factory" wiped data partition.
Obviously I have unlocked again and gone back to B140. If someone else want to experiment, feel free to post your results. I'm done with this :silly:
Re-lock your bootloader successfully
Re-lock your Honor 7(PLK-L01)'s bootloader successfully
No matter on which version you are and on which recovery, follow the steps:
1. Extract the B100 "UPDATE.APP" using this tool. Credit goes to its maker. If you wanna make flashable zip from "UPDATE.APP" then use the attached "Profiles.xml" file for HuaweiUpdate Extractor, me and @kenshiwara has added Honor 7 in the list.
2. Now flash "boot.img", "recovery.img", "cache.img", "cust.img", "system.img", "userdata.img" from the extracted B100 "UPDATE.APP" by executing following commands in "Command Prompt"
Make sure you are in the same folder where all these files are then "Right click" inside the folder by holding down "Shift", then select "Open command window here".
For "boot.img"
Code:
fastboot flash boot boot.img
For "recovery.img"
Code:
fastboot flash recovery recovery.img
For "system.img"
Code:
fastboot flash system system.img
For "cache.img"
Code:
fastboot flash cache cache.img
For "cust.img"
Code:
fastboot flash cust cust.img
For "userdata.img"
Code:
fastboot flash userdata userdata.img
Now reboot your device by executing this command
Code:
fastboot reboot
3. Setup your device, then place B100's "UPDATE.APP" in your external SDCARD in "/dload" folder.
4. Now, switch off your device and press the three button combo to flash the B100 "UPDATE.APP", the three button combo is "Vol. Up", "Vol. Down" and "Power Button" press these three simultaneously to flash the B100 "UPDATE.APP".
5. After your device reboots and after you are done setting it up, go to "Settings > Backup & Reset", then select "Factory data reset", tick "Internal Storage" and press "Reset Phone".
6. Again after rebooting, switch off your device then by pressing "Vol. Down" button connect your device with PC.
7. Now, you'll be in "Fastboot&RescueMode" and your device status will be "Phone Unlocked".
8. Execute the following command to relock your device.
Code:
fastboot oem relock *16 digit unlock code*
9. Now, you'll see that your device status is changed to "Phone relocked".
So, you just relocked your Honor 7.
So basically what I said then
sminki said:
So basically what I said then
Click to expand...
Click to collapse
I think you just flashed "userdata.img" of B100 which is not good as it broke your "/userdata" partition, but yea basically that
DigiGoon said:
8. Execute the following command to relock your device.
Code:
fastboot relock *16 digit unlock code*
Click to expand...
Click to collapse
are you sure? i thaught it was
Code:
fastboot [B]oem[/B] relock *16 digit unlock code*
non-toxic said:
are you sure? i thaught it was
Code:
fastboot relock [B]oem[/B] *16 digit unlock code*
Click to expand...
Click to collapse
Thank you for pointing that out.
speaking as the man who has, you're both incorrect
Code:
fastboot oem relock *16 digit unlock code*
sminki said:
speaking as the man who has, you're both incorrect [emoji14]
Code:
fastboot oem relock *16 digit unlock code*
Click to expand...
Click to collapse
You should've checked my answer before stating that I'm incorrect too. And yeah check its last edit too, its not edited after your reply.
Sent from my PLK-L01 using Tapatalk
i'm not well
my humble apologies @DigiGoon
I have try "fastboot oem relock *my code*" and it works. But i had changed nothing on my phone. it was just unlocked.
no root; no TWRP; no other updates
maybe this was the reason why.
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Hello,
i can`t relocked my phone.
FAILED (remote: root type is risk).
My Honor 7 has the Firmware B330.
I think i tried everything but i always have the same error.
What can is the newest solution?
what's the point of relocking the bootloader?
hachuwaka said:
what's the point of relocking the bootloader?
Click to expand...
Click to collapse
I want to know too. Is there any risk to keep unlocked the bootloader on non rooted device?? Except guarantee
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Sandnes74 said:
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Click to expand...
Click to collapse
You will receive updates but do not install them!!!! If you don't listen to me your device will be caught in bootloop
Sent from my PLK-L01 using XDA-Developers mobile app