Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader
Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.
XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped
I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here
Glad to hear its working
Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.
superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"
please
how did you fix your phone i almost have same problem
He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks
Related
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Taco991 said:
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Click to expand...
Click to collapse
No worries I would be more than happy to provide one after I get home from work
smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Don't know what you are disappointed about. S-OFF stands for security being off. This may sound bad, but from a developer perspective, it's pretty good. If you have true S-OFF like you claim you do, you can flash ROMs, kernels, radios, etc... in a recovery with no issues at all; regardless of what hboot or custom recovery you have. Unlocked means that you can flash custom recoveries and such using fastboot, which is what you want. To sum it up, S-OFF is good; many devs are trying to get S-OFF, but NONE can figure it out. Just be happy about it.
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Closed Source Project said:
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Click to expand...
Click to collapse
Actually I think since he has s-off I think he can make it say whatever he wants.
Once you get the photo up PM me so I can help you out :laugh:
Taco991 said:
Once you get the photo up PM me so I can help you out :laugh:
Click to expand...
Click to collapse
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Where's the S-OFF lol? And yes I think you can do that. It's PD some numbers IMG.zip..
smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Facepalm. You do NOT have S-OFF, What the hell made you think you did. This is normal... Wow. You need to install a custom recovery to flash zips, by the way.
Hey easy on him, he was just mistaken. OP, do you need me to show you how to go back to stock?
smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
You would do better to change thread title...
Hunt3r.j2 said:
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
Click to expand...
Click to collapse
Look at a couple post above urs he doesn't have soff
Sent from my HTC VLE_U using xda premium
Im guessing i kust bricked my phone but thought id ask for help. I tried my luck at flashing a ROM for my first time on my dinc2 and now its stuck,i guess on the boot..it just says htc and wont do anything. Anyhelp please!!
also
patfussy said:
Im guessing i kust bricked my phone but thought id ask for help. I tried my luck at flashing a ROM for my first time on my dinc2 and now its stuck,i guess on the boot..it just says htc and wont do anything. Anyhelp please!!
Click to expand...
Click to collapse
I created a backup before hand but that does little good when i cant get to recovery,please please anyone gimme some good news
patfussy said:
I created a backup before hand but that does little good when i cant get to recovery,please please anyone gimme some good news
Click to expand...
Click to collapse
Good news: your phone is not bricked, as it's responding, it's just stuck on boot, so there's something wrong with the ROM you flashed (maybe a wrong one?).
Have you tried taking your battery off, waiting for a while, put in back in, and then tried to enter CVM? I'd like to help you further, but I don't own that phone.
Also check the Q&A and General threads at http://forum.xda-developers.com/forumdisplay.php?f=1138 for a similar problem.
patfussy said:
Im guessing i kust bricked my phone but thought id ask for help. I tried my luck at flashing a ROM for my first time on my dinc2 and now its stuck,i guess on the boot..it just says htc and wont do anything. Anyhelp please!!
Click to expand...
Click to collapse
How did you unlock your phone? Did you use HTCDev?
yes
SimonTS said:
How did you unlock your phone? Did you use HTCDev?
Click to expand...
Click to collapse
Yes i used htcdev before i new what i was doing, well i still dont really.I wasnt able to achieve s-off because i kept getting errors while trying to downgrade, but somehow was able to get root. I used a rom that i got from the dinc2 forums i believe it was the blackice rom. I cant get this phone to do anything but read htc and turn off by hold volume up/down and power, but then it turns back on by itself. Any ideas guys? Im freakin out
patfussy said:
Yes i used htcdev before i new what i was doing, well i still dont really.I wasnt able to achieve s-off because i kept getting errors while trying to downgrade, but somehow was able to get root. I used a rom that i got from the dinc2 forums i believe it was the blackice rom. I cant get this phone to do anything but read htc and turn off by hold volume up/down and power, but then it turns back on by itself. Any ideas guys? Im freakin out
Click to expand...
Click to collapse
If you used HTCDev to unlock your phone then you need to flash the boot.img (kernel) every time you install a new custom ROM. Check in the threads for full instructions on it.
i was ....
SimonTS said:
If you used HTCDev to unlock your phone then you need to flash the boot.img (kernel) every time you install a new custom ROM. Check in the threads for full instructions on it.
Click to expand...
Click to collapse
I was going to do that after i flashed the rom, but as soon as i did it rebooted my phone to where i am now. I just need to get this thing back to the astboot menu so i can do a recovery....anyone know how i can do that? Thanks for your speedy replies thus far though.
patfussy said:
I was going to do that after i flashed the rom, but as soon as i did it rebooted my phone to where i am now. I just need to get this thing back to the astboot menu so i can do a recovery....anyone know how i can do that? Thanks for your speedy replies thus far though.
Click to expand...
Click to collapse
Use ADB to get yourself back.
elaborate
SimonTS said:
Use ADB to get yourself back.
Click to expand...
Click to collapse
Can use please elaborate. I have sdk downloaded but im lost on how to use it. When i try to open adb a command prompt opens but then just shuts. Thank you
patfussy said:
Can use please elaborate. I have sdk downloaded but im lost on how to use it. When i try to open adb a command prompt opens but then just shuts. Thank you
Click to expand...
Click to collapse
Thank you,got it. I tried multiple times to get to recovery but it kept saying device not found. I removed battery and powered up and hit hit adb reboot recovery right away and it went. Thank you again. Ill be doing a bit more research before i try this again. Any ideas about getting this thing downgraded so i can get s-off? I keep getting errors that the files arent found but i have everything downloaded that i need.
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK
Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2
Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101
I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL
rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.
igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium
Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes
Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Joeymaz73 said:
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Click to expand...
Click to collapse
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
sfreemanoh said:
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
Click to expand...
Click to collapse
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Joeymaz73 said:
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Click to expand...
Click to collapse
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
sfreemanoh said:
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showthread.php?t=2709976
kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
sfreemanoh said:
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
Click to expand...
Click to collapse
Sorry Guys, I should have told you which ROM I had flashed to.. SKYFALL★| |►1.12.605.11◄|4.4.2|VZW||ODEX/DEODEX||►1.2◄|April.10. I'll follow the directions pointed to in the thread above when I get home.. Still leaves me with "tampered" when I boot into recovery or bootloader.
kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Ok.. That zip file, for the red letters worked great. thank you..
after a bunch of searching.. I found this..http://forum.xda-developers.com/showthread.php?t=2708565
thanks for everyone's help. I appreciate everything you do.
Or you can go here where there are a variety of options including making your phone look like it is still s-on
http://forum.xda-developers.com/showthread.php?t=2710503
Thanks for that tool page. I love learning new things about these phones. 20 years I've just been a PC guy.. learning how to do some of this can be tricky. Thank goodness for this forum and the people on it.
So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?
-MightyMouse- said:
So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?
Click to expand...
Click to collapse
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.
-MightyMouse- said:
Any Ideas?
Click to expand...
Click to collapse
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?
quinejh said:
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.
Click to expand...
Click to collapse
Thanks for answering. I had looked into this, but the only way that you could do that is adb sideloading an ota from google. That can only be done by the recovery which is now borked.
bobby janow said:
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?
Click to expand...
Click to collapse
What makes me really mad is that I never disabled OEM unlock. That being said, I did see that is was disabled in settings and didn't think anything of it. I can't get into recovery at all, even through the bootloader. My guess is I borked the image that the recovery was put on as well as the system and probably a couple others. Something I know I could fix if the boot loader wasn't locked. Well I think I will get the ball rolling on an RMA then.
@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.
bobby janow said:
@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.
Click to expand...
Click to collapse
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
Ok cool. Good luck.
Sent from my Pixel using XDA-Developers Legacy app
-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.
NoobInToto said:
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.
Click to expand...
Click to collapse
The error was something like option unavailable. Went through the RMA process which was surprisingly good. Every time I've gone through it, they never ask more than one or two questions before they ask for my imei and tell me that my device could be replaced, which is great, because if I can't fix it, it just needs to be replaced anyways. In other news I got my third pixel just a couple hours ago so hopefully this one lasts me longer than a day.