Hi,
After flashing my M7 and M8 with stock ROM i'm getting this message during initial configuration of the phone saying that "this is a test device....". Can you help me get rid of this message? Thank you
What i've done with my M7 and M8:
-bootloader unlock
-root
-S-OFF
- CID to 11111111
-M7 flash with stock firmware: RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
-M8 flash with stock firmware: RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
-unroot
-bootloader relock
s-off was the reason. I've changed it back to S-on and now it's gone
Can remove Udove.apk I believe and this message will not be there during setup.
karoltom said:
s-off was the reason. I've changed it back to S-on and now it's gone
Click to expand...
Click to collapse
Related
Hi
I am stuck on the bootloader, because:
- I unlocked via htcdev online
- installed CWM recovery
- I tried to install custom roms update-ics-yetki-1.0.zip LeeDrOiD-Flyer-V2.2.0.zip (unfortunately with s-on)
result: black screen on system boot, unable to go further than bootloader or recovery.
after relocking I tried to run :
RUU_Flyer_TMO_DE_2.27.111.1_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204120_signed.exe
some errors on installing like 140, bootloader error
so I am not sure if this is the good RUU
before bricking my Flyer definitely I would like to know how can I know which is right RUU for my device to install?
The only information about my device I can get are those:
Flyer pvt ship S-ON RL
HBOOT 1.11.0011
MICROP - 0950
RADIO-3822.11.08.07M2
eMMC-boot
Oct 25 2011, 16:55:07
the device has (had) a T-Mobile (Germany) branding
cid: T-MOB101
version-main: 3.55.111.1
anyone a clue?
Thank you
You MUST relock bootloader first in order to flash RUU!!!
Go to fastboot and enter: fastboot oem lock. Then try to install RUU. Nice unbricking!
sgarza said:
I wrote
after relocking I tried to run :
RUU_Flyer_TMO_DE_2.27.111.1_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204120_signed.exe
some errors on installing like 140, bootloader error
so I am not sure if this is the good RUU
Click to expand...
Click to collapse
Keioboy said:
You MUST relock bootloader first in order to flash RUU!!!
Go to fastboot and enter: fastboot oem lock. Then try to install RUU. Nice unbricking!
Click to expand...
Click to collapse
Thanks for reply
of course... I relocked it but update utility gives me error 140....
somebody thinks it's because of incompatibility of flashing an older version on a newer one,
I don't know if that has something to do with kernel, radio, baseband or whatsoever....
sgarza said:
Thanks for reply
of course... I relocked it but update utility gives me error 140....
somebody thinks it's because of incompatibility of flashing an older version on a newer one,
I don't know if that has something to do with kernel, radio, baseband or whatsoever....
Click to expand...
Click to collapse
Ok, the only way I found to solve was flashing a
rom.zip retrieved from temporary files after launching the HTC update utility, (RUU.exe)
from RUU_Flyer_HC_S_HTC_TUR_3.62.468.1
I renamed the rom .zip to PG41IMG.zip,
then copied it on a goldcard, prepared before...launched bootloader and so on...
that was the only one without errors that finally worked...
now trying to flash a custom rom, I need phone functions....which rom?...
Hi guys,
Bought a Evo 3D second hand... GSM version.
Got it home, had a custom stock rom on it and had Revolutionary Recovery on it.
I flashed a MIUI rom to it and have been using that fine for a few months, now i have come to install a different rom and it installs fine but won't boot. It either stays on the bootscreen forever or just reboot cycles the phone.
Now the bootloader is unlocked but it doesn't have S-OFF.
I think i need to S-OFF to flash the roms correctly.
Here's whats on it:
Rom: MIUI v2.10.26
Baseband: 11.77.3504.00U_11.25.3504.06_M
HBOOT: 1.53.0007
Recovery: 4EXT recovery
HBOOT says:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.007
eMMC-BOOT
May 22 2012, 01:06:07
Just want to provide as much info as possible...
It would be fantastic if you could help me
Thanks
bump!
I suggest you RUU back to stock and use this guide to get s-off
http://forum.xda-developers.com/showthread.php?t=1743466
EM|NEM said:
I suggest you RUU back to stock and use this guide to get s-off
http://forum.xda-developers.com/showthread.php?t=1743466
Click to expand...
Click to collapse
I have downloaded RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
And i get Error 155 when flashing. I have also downloaded the .zip version and when i try and flash it from recovery it says it cant and the file is bad.
flyboyovyick said:
And i get Error 155 when flashing.
Click to expand...
Click to collapse
Lock your bootloader with the "fastboot oem lock" command and run the RUU again.
ramjet73
ramjet73 said:
Lock your bootloader with the "fastboot oem lock" command and run the RUU again.
ramjet73
Click to expand...
Click to collapse
This is what i get: http://puu.sh/2ndCW
EDIT: Now says relocked in HBOOT gonna flash RUU
Flashed the stock RUU, now i'm trying to unlock the bootloader again via HTCDev.com and when i copy the Identifier Token it says its too short. I am pretty sure i'm copying it correctly
solved... There were spaces in the box
So i am now S-OFF, i need to downgrade my HBOOT still...
How do i do that?
Right, managed to downgrade the HBOOT but still, when i flash AOKP it stays on the splashscreen forever....
http://forum.xda-developers.com/showthread.php?t=1906172
use this hboot. and wipe everything(data and cache) before flashing aokp
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
jimscheltus said:
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
Click to expand...
Click to collapse
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Dr.ripsaw said:
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Click to expand...
Click to collapse
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
jimscheltus said:
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
Click to expand...
Click to collapse
Well When I got my phone I allowed it to update to the latest version of android and so it upgraded my Hboot version. To get the latest version you need to flash the latest firmware. I think restoring a backup that is the newest version of stock will automatically update your Hboot. Don't take my word for it as I've said my Hboot was fully updated before I started Modding.
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
K.AuthoR said:
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Click to expand...
Click to collapse
Have you tried to re s-off?
I believe the firewater and romrunner tools in the int. One forums should be able to s-off that hboot.
I haven't personally gone s-off, but my understanding is that once s-off you can change your sid (super sid maybe?) And run just about any ruu.
Search up on that stuff.
Sent from my HTC One using xda app-developers app
K.AuthoR said:
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Click to expand...
Click to collapse
you will have to s-off to repair the phone or hope for a new GPE RUU
whats the fastboot getvar all results (minus the serial no and IMEI )
I see a few mistakes. First, never go S-On and/or lock the bootloader once they've been unlocked. There's no reason for this unless returning to stock for warranty purposes. And if you do, ensure the phone has the software it's supposed to (AT&T in this case).
Secondly, if you have GPE, you must downgrade to hboot 1.44 first. And to do this, you must be S-Off.
Since the phone is currently S-On, the course of action depends on what is on the phone. If your CID is currently GOOGL001 or 11111111, try flashing the latest GPE RUU to restore the phone to working condition. Then go to HTCDev and unlock the bootloader. After that, you can use Firewater to S-Off.
Assuming all is successful, search for and flash hboot 1.44, then change the CID to CWS__001 (that's two underscores) and flash an AT&T RUU. And whatever you do, don't go S-On or lock the bootloader again. There's nothing to be gained by doing this.
If you're returning the phone to AT&T software because the person didn't like GPE (which I don't blame them), use the Dev Edition. By far the best choice to get the same Sense version of Android without all of the AT&T sh*tware. And things like AT&T Visual Voicemail work, along with any other AT&T app if the person wanted to download it from the Play Store for free.
Good luck.
Hello. I installed Cyanogenmod on my HTC ONE M7 AT&T. I want to revert my phone so I can exchange it because of the purple camera problem. How can I revert my phone back to stock HTC Sense? Before I installed Cyanogenmod, I had android version 4.3.
Gobbling_Monkey said:
Hello. I installed Cyanogenmod on my HTC ONE M7 AT&T. I want to revert my phone so I can exchange it because of the purple camera problem. How can I revert my phone back to stock HTC Sense? Before I installed Cyanogenmod, I had android version 4.3.
Click to expand...
Click to collapse
Are you s-off ?
post a fastboot getvar all (minus you serial no and IMEI)
It is s-on. And how do I post that fastboot thing?
Gobbling_Monkey said:
It is s-on
Click to expand...
Click to collapse
You can follow nkk71's SuperGuide that is in my signature. To remove the "Tampered" banner and to "Locked" instead of "Relocked" you will need S-OFF all of the information is in the guide.
If you don't care about the "Tampered" banner or being "Locked" then you could use RUU 3.17.502.3 to return you back to stock provided your are really 4.3. You can verify this with the fastboot getvar all command. If your version-main is higher than this you will not be able to run this RUU since, you are S-ON you will also need to relock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
majmoz said:
You can follow nkk71's SuperGuide that is in my signature. To remove the "Tampered" banner and to "Locked" instead of "Relocked" you will need S-OFF all of the information is in the guide.
If you don't care about the "Tampered" banner or being "Locked" then you could use RUU 3.17.502.3 to return you back to stock provided your are really 4.3. You can verify this with the fastboot getvar all command. If your version-main is higher than this you will not be able to run this RUU since, you are S-ON you will also need to relock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks, it is now stock again. However, it shows re-locked in the bootloader. Is there any way to fix this so that I can send my phone to HTC for repairs?
Gobbling_Monkey said:
Thanks, it is now stock again. However, it shows re-locked in the bootloader. Is there any way to fix this so that I can send my phone to HTC for repairs?
Click to expand...
Click to collapse
The only way to have it show "Locked" instead of "Relocked" is to obtain S-OFF. In nkk71's guide he shows how to change them and how to achieve S-OFF.