Develop Bugs

My ONE X doesn't work now!Please Help! :'(

this is my first time to post on the xda,
if i have post in the wrong forum , please help me to move the right forum,thanks!
i have edit the system file to fix camera issue,but i forget to backup file!
Now my phone can't run in to the system.
How can i repair my phone now ?
My phone software version is 1.29.708.9 (HongKong Version) , i think i need the same version RUU....?
Sorry my english is very poor , hope you can know what am i saying

kill0147 said:
i have edit the system file to fix camera issue,but i forget to backup file!
Now my phone can't run in to the system.
How can i repair my phone now ?
My phone software version is 1.29.708.9 (HongKong Version) , i think i need the same version RUU....?
Sorry my english is very poor , hope you can know what am i saying
Click to expand...
Click to collapse
You need to reflash with the original RUU, you can find some RUUs from here: http://www.filefactory.com/f/7cc7b2fbdd03c031/
THIS PROCESS NEEDS A RELOCKED PHONE. (fastboot oem lock).
edit: the RUU for your version isnt published already. You need to wait for the RUU, Why can you use an older version? You can't because the DOWNGRADE isn't posible with S-ON.

If you know what file you modified, maybe extract it from a similar ROM and adb push it?

if youve edited the build.prop without backing it up first then quite simply youre asking for trouble....
ALWAYS Nandroid and back up anything before altering it.
If you can access download mode then your safe, just connect up usb for fastboot and run a downloaded RUU, if youre not sure what rom to get then id try HTC EUROPE ones they first, these are probably the most common ones.

wolfraim said:
You need to reflash with the original RUU, you can find some RUUs from here: *******
THIS PROCESS NEEDS A RELOCKED PHONE. (fastboot oem lock).
edit: the RUU for your version isnt published already. You need to wait for the RUU, Why can you use an older version? You can't because the DOWNGRADE isn't posible with S-ON.
Click to expand...
Click to collapse
Oh....i have try to downgrade when i post this post, but it isn't possbie....(S-ON Now)
Now,the recovery is broken , my phone is hold on the screen on hboot now! I'm not sure can i input power because the phone is always auto reboot in hboot when i connect the power input

graemeg said:
if youve edited the build.prop without backing it up first then quite simply youre asking for trouble....
ALWAYS Nandroid and back up anything before altering it.
If you can access download mode then your safe, just connect up usb for fastboot and run a downloaded RUU, if youre not sure what rom to get then id try HTC EUROPE ones they first, these are probably the most common ones.
Click to expand...
Click to collapse
i will backup the file to PC in next time when i edit any system file...... i have learn a lesson

Yer try not to mess with the build.prop, i know its fun to tinker and see what can be achieved, but there is also a serious risk that comes with it, unfortunatley the file will stop your phone dead if you mess it up, if you save a backup to your pc then worst case you can push it to your phone via adb and overwrite the damaged one.
What CID are u on, eg, htc--001 ??, cidgetter works from market but not much use if you cant boot up, also what firmware are you running now, release, radio and release keys, that way you could extract the boot, recovery and system from the file and just flash them in bootloader.
YOU must relock your bootlock first, the above command in other post was the one to do that, if not, have u tried to flash CWM 5.8.3.1, and install from the recovery youll get both the super su and a custom rom, like android revolution, this way youll be back up and running on a custom rom based on the latest 1.29, you could then download the 1.29 ruu and run it, again after relocking the bootloader and for good measure download and install htcsync, the program delivers a much better driver for the one x, that should get you back to factory, unrooted, stock boot and firmware.
if the ruu isnt avail, find out what your latest ruu is and look for a custom rom based on that.
Keep us informed how you get on, im sorry you learnt the lesson the hard way, i would not wish this to happen to anyone, except for maybe Bill Gates lmao, but then he would just throw it in the bin and go buy another one ha ha.
I hope you get it sorted and remember, before you tinker, READ the guides on XDA, they are good and will really help you and always make a backup of anything you wish to experiment with.
Good luck.

If you still remember the file, try to get it from someone with the same version as you and push it through adb or recovery (if you can go to hboot, surely you can flash cwm again).
Sent from my HTC One X using xda premium

I hope u can read chinese
I had the same problem... and before.. i just flash the RUU again, but after i upgraded to 1.29.. that didn't work...(The RUU I had was 1.26) so with ALOT of searching on the internet.. i found the below Chinese site.. and luckily i can read chinese too...
anyway hope it helps.
Basically what i did was force the recovery to be install on my phone.. but there is a down side.. me alarm doesn't work.. everytime i try to change the alarm sound it just reboot... i am still trying to find a way to fix it... and maybe flash the 1.28 RUU to see if that will work.... but that will have to wait until tonite.
http://bbs.xda.cn/thread-11018720-1-1.html

last night , i had make a fake RUU(basic on 1.28.708.10 HongKong Version RUU,included recovery.img,boot.img,system.img) and flash it ,the result is my phone is recovered , all function is normal and i can get OTA now !!

Return to stock 1.31.651.2 Sprint HTC One after root

OK, So after searching and Searching for a way to go back to complete stock after taking the latest 1.31 update and rooting my HTC One, and not being able to use any current RUU without having to gain S-off. I finally did it. I am 100% stock on an updated software version of 1.31.651.2.
So here is what I did and please feel free to step in and let me know if there was an easier way.
Step 1.
I unlocked my boot-loader to gain root privileges
Step 2.
I flashed TWRP
Step 3.
Created Nand Backup if something fails
Step 4.
I flashed SuperSU
OK, so that got me rooted. but I wanted to go back to stock after playing around with certain roms my phone started acting goofy.
this is the part where it gets a lil tricky.
in order for me to get back to stock on my One to the most current version of 1.31.651.2.
this is what I had done.I installed an app from the market called Rom toolbox lite(FREE) put REVONE in /data/local/temp
gained S-off. installed a stock RUU 1.29.651.7. Now the only problem is that I was S-off and my boot loader shows tampered and unlocked.so I used revone to remove tampered with the -t command and also wanted to lock the boot loader with the -l command. in order to get s-on. booted into the boot loader and selected fastboot and entered fastboot command, fastboot oem writesecureflag 3 to regain s-on.
ok so I am still technically rooted so in order to remove all root instances I ran again the RUU 1.29.651.7. all good so far. I double checked by booting into the boot loader to make sure I am s-on and locked along with no tampered flag. YES!!!!. so now I booted up my phone . skipped all setup processes. and went straight to the check for updates in the phone menu. I updated to the next most recent after the 1.29.651.7 and installed 1.29.651.10. I download and installed the update. again checking to see if there were any changes in the boot loader. NOPE STILL ALL GOOD,YESSSS!!!!
so now it rebooted and again went straight to the HTC update menu and ran a check for updates and it then downloaded the most recent update 1.31.651.2. Installed and I checked the bootloader and I AM NOW 100% STOCK and on the latest software version.

At least a Thank You ??

Thanks for Sharing!
viper1723 said:
At least a Thank You ??
Click to expand...
Click to collapse
I was having the same issues when trying different Roms and screwed up my phone to the point where roms would boot but them restart over and over and over...no matter what rom i loaded and any kind of wiping i did.
so I also returned to stock locking the bootloader and flashing stock RUU as you mention. Just tried going from 1.29 to 1.31 with OTA last night and it wiped my phone and didn't upgrade. So i'm hoping it was just a hiccup and going to try again.
Hope it works this time.

Solartrooper said:
I was having the same issues when trying different Roms and screwed up my phone to the point where roms would boot but them restart over and over and over...no matter what rom i loaded and any kind of wiping i did.
so I also returned to stock locking the bootloader and flashing stock RUU as you mention. Just tried going from 1.29 to 1.31 with OTA last night and it wiped my phone and didn't upgrade. So i'm hoping it was just a hiccup and going to try again.
Hope it works this time.
Click to expand...
Click to collapse
Let me know how it went I'll give u a more detailed method of what I did exactly

That's were I'm at right now.
viper1723 said:
Let me know how it went I'll give u a more detailed method of what I did exactly
Click to expand...
Click to collapse
Okay guys so everything you described is exactly where I'm at. I've tried a million ROMs, process, adb.exe (no devices), etc...... Anyway here's my scenario.... Exactly yours: got my phone, rooted it, had S-On. the phone ran it's updated to 1.31.651.2 so there are no RUUs for this. Any extra details to get me there?
Where should I start? Please let me know if you can help.
Thanks!:cyclops:

[Q] after new ota cant unlock boot loader and adb doesnt see device

Ok so this is what i did
i installed stock recovery and locked bootloader using this TUT http://forum.xda-developers.com/showthread.php?t=2470340&highlight=unlock+bootloader
everything went good had some issue with update and nandroided back to original took the updates everything good to this point now on 4.3
I am still s off boot loader shows locked now my problems started
tried to unlock using same TUT as above won't go
made sure debug was checked
adb does not see my device but fastboot does
tried to fastboot flash recovery no go says remote not allowed
tried to fastboot flash boot image no go says remote not allowed
I think it has to do with boot loader being locked but without adb how do I unlock any help would be appreciated

update
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated

bregga said:
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated
Click to expand...
Click to collapse
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.

another update
I ran ruu and installed rumrunner hboot and flashed a twrp recovery both went fine using fastboot commands and i have a custom recovery again
and root but still cant adb its weird I have never had a issue with adb before

santod040 said:
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.
Click to expand...
Click to collapse
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?

carm01 said:
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?
Click to expand...
Click to collapse
I'm not saying that you can't take the OTA. Obviously you can, I posted roms made from it, right?
I did say there is no need to relock.
I'm not gonna go over it a bunch as to why it's just not a wise idea for the common user.
But you must have noticed the flood of users getting confused, and/or stuck when trying to do so.
It's not that hard to do it successfully, no.
Is it really necessary to go through that, when the same thing can be had by simply flashing the firmware and rooted rom?
I guess my point isn't so much that you can't take the OTA, as much as it is, why? It's a bad habit for a rooted user to get into honestly.
Why go through that? You can flash the stock rooted firmware and rom and not have to do the hokey pokey and turn yourself around.
But maybe I see it differently, I don't know.

santod040
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway

bregga said:
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway
Click to expand...
Click to collapse
I can understand wanting to stay stock.
I was just suggesting flashing a pure stock rooted rom.
As I said though, relocking was not necessary.

[Q] Did some searches, spent more than four hours looking..

Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone

Valkalkas said:
Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Click to expand...
Click to collapse
haha... Love :victory:
Now back to issue.
If you're in the bootloader you don't need USB Debugging enabled, you can still use the fastboot command regardless of USB debugging mode. Check
Code:
fastboot devices
not
Code:
adb devices
.
Make sure all the drivers are still fine on the PC, reinstall if you must.
On a side note, try not to use all-in-one toolkits as you really don't get to learn from using something like that. If you did it manually you'd already have a pretty good understanding on which command gets used in which instance i.e bootloader vs in-system.

I actually didn't use a all-in-one this time around but as soon as I unlocked boot loader and rooted I had issues installing the custom rom. I've used both phil z and twrp but it still gets stuck when I install the sky dragon, or viper for that matter to test and make sure it wasn't just a bad download. Earlier when I did fast boot devices it did show something but now it's just a blank space. I'm in bed now I would double check again to make sure but like I said it's been a few hours and now it's 4:38 am and I'm tired. I'll double check in the morning but I appreciate your response and I'll double check. Drivers should be good from last time but I will double check and make sure. Again thanks for responding!

Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.

Valkalkas said:
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Click to expand...
Click to collapse
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device

ckpv5 said:
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
Click to expand...
Click to collapse
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.

Valkalkas said:
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Click to expand...
Click to collapse
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423

ckpv5 said:
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Alright, thank you for your help. I relocked and I tried the second link you posted, but the ruu messes up after I accept the EULA and just keeps popping up boxes. Downloading the RUU from the first link now and gonna try that. I just run the RUU in fastboot usb right?
Again thanks, I had no idea to check for hboot versions when rooting/flashing in the time I've rooted some devices so guess I'm learning something the hard way.
Edit: Same thing with the first link. I feel like I'm in the wrong place trying to run the RUU in fastboot usb?

Alright, tried running the RUU's again on the black screen with the silver HTC letters as suggested by someone else and the program still acts up after the EULA.

Alright, I was able to find a nandroid backup and restore it through there, so now I'm back in business. Thanks for the help!

Returning to stock issues.

I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!

Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.

I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?

Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.

Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?

Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...

Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.

Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?

Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?

Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!