Related
Used Regaw root
TWRP as recovery
Viper ROM
google wallet not working even though I cleared it reset to factory before rooting. So I started to unroot followin QBKING77's video on relocking before unroot now I'm stuck in fastboot
\
And this is in development, why? Why don't you post this on to the Regaw thread?
shook187 said:
And this is in development, why? Why don't you post this on to the Regaw thread?
Click to expand...
Click to collapse
Well captain Obvious I am not sure if its the Regaw, Viper Rom, TWRP or if QGking77 has anything to do with it! and Obviously you don't either thanks for the ignorant reply
shook187 said:
And this is in development, why? Why don't you post this on to the Regaw thread?
Click to expand...
Click to collapse
Why don't you stop bein' obnoxious in every post you make? If you don't want to answer him don't. Report the post for being in the wrong section and leave it at that.
str3tchnut5 said:
Well captain Obvious I am not sure if its the Regaw, Viper Rom, TWRP or if QGking77 has anything to do with it! and Obviously you don't either thanks for the ignorant reply
Click to expand...
Click to collapse
Ignore him.
What do you mean you're stuck in fastboot? Did you get a RUU installed? When you hold the power button for 10 seconds, what does it do on the reboot?
Yes I did the RUU when I did all of the root, recovery and the Viper mod. Followed up with th eRUU the wallet never syncronized! Figured I would Unroot follwed QGkings video to relock before unroot now no matter what I do stuck in fastboot
str3tchnut5 said:
Yes I did the RUU when I did all of the root, recovery and the Viper mod. Followed up with th eRUU the wallet never syncronized! Figured I would Unroot follwed QGkings video to relock before unroot now no matter what I do stuck in fastboot
Click to expand...
Click to collapse
Ok. So if you reboot the phone right now, what happens? Does it boot into fastboot? Does it bootloop?
smw6180 said:
Ok. So if you reboot the phone right now, what happens? Does it boot into fastboot? Does it bootloop?
Click to expand...
Click to collapse
goes into fast boot screen
it says Tampered
Relocked
Security warning
at the top of the screen
str3tchnut5 said:
it says Tampered
Relocked
Security warning
at the top of the screen
Click to expand...
Click to collapse
Ok. You need to run the RUU or something. Sounds like there IS a ROM on there because it wouldn't show tampered if the filesystem didn't have root.
Have you tried using the htcdev unlock again on it?
You'll need to either run a RUU or unlock and flash a stock recovery and boot image. The security warning is because you have S-ON and are using a modified kernel/recovery.
Yes the S-on is active Tried RUU get error 140. dont know what HTC Dev other than Regraw. that doesnt work either! Keeps saying not Evo 4g lte
The 140 error, I believe, is from having a bad connection. You may need to reinstall and then uninstall htc sync to get the proper drivers before it'll work.
i have the same problem any answers
Install the generic HTC drivers and check under devices that its detecting your phone
sent from my EVO LTE
nope
i did a new install of htc driver the same ver to root. and no good under devices it shows andriod- htc but i can get to it under the c drive
my phone is stuck in a boot loop, any help?
Ok first off my phone just started a boot loop but only with the first htc quietly brilliant screen, noting more. It then restarts and does it all over again. I tried the factory reset a few times and got nothing. So i decided now would be a good time to root so I unlocked with htvdev. Then, using the twrp stuff, i did the fastboot devices cmd and it recognizes the phone. So i did the rest the jewel stuff and it said okay. Then did the cache erase. After getting back to hboot screen i select recovery and it starts with the htc quietly brilliant screen with the red writing under it. After a few seconds the phone restarts and the htc quietly brilliant screen is back but without the red writing under it and it starts the boot cycle all over again. I have no access the the twrp recovery, just the fastboot and bootloader stuff. I am fairly new to this stuff and have searched all over the place but cant find what im looking for. Maybe not looking for the right stuff. Any direction would be great. Thanks
Ok So now I got it to loop the splash screen but with the writing under it. I forced a couple roms and found one that did brick it. Got it back through ubuntu but thats about it, still looping.
Sounds like you're S-on & you need to install the kernel separately from the ROM for your phone to boot. Click the link in my sig for more info.
Also, your phone isn't bricked
Sent from my EVO using xda premium
I cant get into twrp. Its installed but I cant access it and i cant seem to figure out how to flash a kernal or rom or anything. Im running hboot 2.09 unfortunately. I dont know what rom or kernal to flash anyway. The dirtyracun stuff says to boot into recovery for part of it and I cant get into recovery.
Can you access your bootloader screen?
Sent from my EVO using xda premium
FinZ28 said:
Can you access your bootloader screen?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yes
enolive said:
Yes
Click to expand...
Click to collapse
What happens when you try to access recovery from the bootloader screen?
Sent from my EVO using xda premium
FinZ28 said:
What happens when you try to access recovery from the bootloader screen?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It shows the splash screen with the htc writing, sits there for 30 secs or so then the screen goes black and then the splash screen comes back up. I keeps doing that over and over. I should clarify that the twrp install was the next step that I was trying to get to. After typing "fastboot flash recovery openrecovery-twrp-2.5.0.0-jewel.img" then selecting recovery. Mind you that the boot cycle was already happening in the very beginning and thats what prompted the root. Kind of a "nothing to lose" deal.
I also just tried to see if adb is still reading my phone and now its showing the "list of devices attached" with nothing listed. Im not sure if the developer options could have been reset to off or something, dont even know if that matters at this point.
You need to get into the bootloader and plug your phone up to it. Make sure it's connected via Fastboot USB highlighted in red, then try fastboot flashing the recovery again. Make sure the recovery file is in your ADB tools folder or it won't work. Once you get recovery working I suggest using the mount option, then you can transfer files to your phone from your computer. I suggest using a ROM that has an S-on kernel installer, like MeanBean. Just follow the instructions for flashing the ROM.
Sent from my EVO using xda premium
FinZ28 said:
You need to get into the bootloader and plug your phone up to it. Make sure it's connected via Fastboot USB highlighted in red, then try fastboot flashing the recovery again. Make sure the recovery file is in your ADB tools folder or it won't work. Once you get recovery working I suggest using the mount option, then you can transfer files to your phone from your computer. I suggest using a ROM that has an S-on kernel installer, like MeanBean. Just follow the instructions for flashing the ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The phone is plugged into the computer and connected via fastboot usb in red like you said. The recovery file is in the adb folder. It says
C:\Users\Adam\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-twrp
-2.5.0.0-jewel.img
sending 'recovery' (8196 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 2.000s]
finished. total time: 3.020s
Thats the problem, when i select recovery, in the bootloader menu, it just keeps rebooting. I let it go for awhile, like 2 hrs, and thats all it did.
Would a messed up sdcard cause this? Should I try mounting file the the sdcard and then putting it back in the phone? I'm not against going with the s-off but I cant get that to work till i get into the recovery, right?
That's weird. You should be able to get to recovery now. Try and install an older version of TWRP, like version 2.41. It's on their site.
Sent from my EVO using xda premium
FinZ28 said:
Did you try to fastboot flash the recovery to your phone from your computer like I said to do in my previous post? Or are you just trying to boot straight into recovery from the bootloader?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Fastboot flash from the computer? Isnt that what I was doing or am i doing it wrong? I type it all in on the cmd prompt. If thats not right I dont know how else to do it. Is there another way to boot the recovery other then from the bootloader?
Try "fastboot reboot recovery " from the command window.
I'm not 100% positive about that command but it should be good
SENT FROM MY LTEVO
corcgaigh said:
Try "fastboot reboot recovery " from the command window.
I'm not 100% positive about that command but it should be good
SENT FROM MY LTEVO
Click to expand...
Click to collapse
Just tried it and it gave me a list of commands to try. I just copied the twrp file "pj75img.zip" to the sdcard via another phone. Problem is that the battery is to low right now so its gonna wait till tomorrow.
enolive said:
Just tried it and it gave me a list of commands to try. I just copied the twrp file "pj75img.zip" to the sdcard via another phone. Problem is that the battery is to low right now so its gonna wait till tomorrow.
Click to expand...
Click to collapse
You won't be able to flash a PJ75IMG.zip file unless you are S-OFF
Open a cmd window from android-sdk/platform-tools folder and type adb reboot recovery and press enter
that should take you to twrp
bigdaddy619 said:
You won't be able to flash a PJ75IMG.zip file unless you are S-OFF
Open a cmd window from android-sdk/platform-tools folder and type adb reboot recovery and press enter
that should take you to twrp
Click to expand...
Click to collapse
Well now it says "error:device not found". When I type "adb devices" i get the blank list of devices but if i type "fastboot devices" it gives me the number. I think at some point I tried fastbooting a rom didn't work and actually bricked the phone, blank screen that wont turn on. Then fixed that via ubuntu and got it back to the bootloop. As I stated in the beginning it wasnt booting with the red writing at the bottom of the splash screen to start but then went away on the second reboot and kept rebooting without it. After fastbooted twrp again it now shows the red writing on every reboot. Also I cant get the battery to charge because i cant shut it off so it says battery low when i try the flash recovery command. The battery charge led is blinking slowly for about a minute after a simulated battery pull but thats it.
I guess its not fixable.
enolive said:
I guess its not fixable.
Click to expand...
Click to collapse
It's fixable, bro. Check your PM
Sent from my EVO using xda premium
hi guys im a total noob bought a droid dna on craigslist that was rooted. i tried to set back to stock with ruu got message error 158. i then tried hboot method and when i put cmd fastboot oem writeflagsecure 3 my phone now says tampered ,relocked, security warning and when you reboot just keeps going to fast boot menu.again im new to this and dont know what im doing so maybe i shouldnt have dabbled with it...ill attach a pic of the screen its a red employee edition droid dna... thanks for any help you can offer
Leave it alone! Go to recovery and delete data and reboot the phone.
Sent from my HTC6435LVW using XDA Premium HD app
ifi try recovery or anything just brings me back to the same screen
worm1977 said:
hi guys im a total noob bought a droid dna on craigslist that was rooted. i tried to set back to stock with ruu got message error 158. i then tried hboot method and when i put cmd fastboot oem writeflagsecure 3 my phone now says tampered ,relocked, security warning and when you reboot just keeps going to fast boot menu.again im new to this and dont know what im doing so maybe i shouldnt have dabbled with it...ill attach a pic of the screen its a red employee edition droid dna... thanks for any help you can offer
Click to expand...
Click to collapse
Did you know if it had an Engineer's HBOOT before? Writeflagsecure 3 is to remove S-OFF. You didn't need to do that to go stock.
Try flashing a recovery?
If this for insurance purposes? Just wondering what you're trying to do with your phone since it was working when you got it.
karn101 said:
Did you know if it had an Engineer's HBOOT before? Writeflagsecure 3 is to remove S-OFF. You didn't need to do that to go stock.
Try flashing a recovery?
If this for insurance purposes? Just wondering what you're trying to do with your phone since it was working when you got it.
Click to expand...
Click to collapse
i think i tried to flash recovery. i just want to get it to work so i can use it or sell it. when it poered up normally it had the red writing on the bottom that said for htc developer purposes also instead of the dna boot up it said htc one
worm1977 said:
i think i tried to flash recovery.
Click to expand...
Click to collapse
That isn't a good sign. What steps did you take to flash a recovery?
karn101 said:
That isn't a good sign. What steps did you take to flash a recovery?
Click to expand...
Click to collapse
tried recovery then reboot on phone just takes me to the same screen. also believe i tried fastboot-flash recovery
worm1977 said:
tried recovery then reboot on phone just takes me to the same screen. also believe i tried fastboot-flash recovery
Click to expand...
Click to collapse
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
EDIT:
Follow these directions and then select RECOVERY from your bootloader. Let us know what happens please.
http://forum.xda-developers.com/showthread.php?t=1994662
karn101 said:
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
Click to expand...
Click to collapse
It had clock work mod on it.no offense taken im just new to this and its kind if confusing to me.since it wouldnt boot thru ruu thats when I tried the hboot method.i dont quite understand the cmd's and flashing I guess.
karn101 said:
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
EDIT:
Follow these directions and then select RECOVERY from your bootloader. Let us know what happens please.
http://forum.xda-developers.com/showthread.php?t=1994662
Click to expand...
Click to collapse
ok after i download do i just try to flash thru the adb commands?
worm1977 said:
It had clock work mod on it.no offense taken im just new to this and its kind if confusing to me.since it wouldnt boot thru ruu thats when I tried the hboot method.i dont quite understand the cmd's and flashing I guess.
Click to expand...
Click to collapse
I hear you, it can be overwhelming at first. I've been flashing since the WM 6.5 days and still don't know as much as some of the people here!
When you select RECOVERY, it's bringing you back to the BOOTLOADER screen, right?
If that's the case, the RECOVERY may have been removed, which is why I'm saying to flash a new one in. Did you follow the instructions on that thread I linked to?
---------- Post added at 04:04 AM ---------- Previous post was at 03:53 AM ----------
worm1977 said:
ok after i download do i just try to flash thru the adb commands?
Click to expand...
Click to collapse
Just saw this. No, you should be using fastboot commands, not ADB
fastboot flash recovery recovery.img
To begin, do you have the Android SDK installed on your computer? (Platform Tools)
You save the TWRP .img file in that folder.
Shift+Right Click on the folder and click Open Command Prompt Here
The phone should be connected to the PC
From the BOOTLOADER, go to FASTBOOT
It should say FASTBOOT USB
You can double check by typing 'fastboot devices'
Then run 'fastboot flash recovery recovery.img'
recovery.img will be named whatever your TWRP file is named
Then for good measure do 'fastboot reboot'
Now, you should be back in BOOTLOADER
Go to RECOVERY, and what do you see?
karn101 said:
I hear you, it can be overwhelming at first. I've been flashing since the WM 6.5 days and still don't know as much as some of the people here!
When you select RECOVERY, it's bringing you back to the BOOTLOADER screen, right?
If that's the case, the RECOVERY may have been removed, which is why I'm saying to flash a new one in. Did you follow the instructions on that thread I linked to?
---------- Post added at 04:04 AM ---------- Previous post was at 03:53 AM ----------
Just saw this. No, you should be using fastboot commands, not ADB
fastboot flash recovery recovery.img
yeah fastboot sorry. im at work now ill try it when i get home in 2 hours i have the sdk downloaded
To begin, do you have the Android SDK installed on your computer? (Platform Tools)
You save the TWRP .img file in that folder.
Shift+Right Click on the folder and click Open Command Prompt Here
The phone should be connected to the PC
From the BOOTLOADER, go to FASTBOOT
It should say FASTBOOT USB
You can double check by typing 'fastboot devices'
Then run 'fastboot flash recovery recovery.img'
recovery.img will be named whatever your TWRP file is named
Then for good measure do 'fastboot reboot'
Now, you should be back in BOOTLOADER
Go to RECOVERY, and what do you see?
Click to expand...
Click to collapse
i get home in 2 hours ill try then. i have sdk installed and was using fastboot commands
worm1977 said:
i get home in 2 hours ill try then. i have sdk installed and was using fastboot commands
Click to expand...
Click to collapse
Cool. Same here. I work 2300-0700 hours.
karn101 said:
Cool. Same here. I work 2300-0700 hours.
Click to expand...
Click to collapse
down loaded that goo manager tried fastboot flash recovery GooManager_2.1.2.img said unknown error cant load GooManager
worm1977 said:
down loaded that goo manager tried fastboot flash recovery GooManager_2.1.2.img said unknown error cant load GooManager
Click to expand...
Click to collapse
You need to flash a recovery twrp is probably the best one. Goomanager is a app use to download and install ROMs.
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
You need to flash a recovery twrp is probably the best one. Goomanager is a app use to download and install ROMs.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
What he said ^^
Here are the direct links.
http://techerrata.com/browse/twrp2/dlx
I'd suggest downloading 2.5 as 2.6 gave me issues.
karn101 said:
What he said ^^
Here are the direct links.
http://techerrata.com/browse/twrp2/dlx
I'd suggest downloading 2.5 as 2.6 gave me issues.
Click to expand...
Click to collapse
I've had no problems with 2.6 personally but either one will work. Once your in
Recovery you can download a ROM on your computer and on adb use.
adb push "C:\Documents and Settings\Josh\My Documents\Downloads\ViperDNA_1.3.5.zip" sdcard
Clearly that's how I would do it via my computer after you type adb push you can hit the space bar and drag the file to the command prompt and drop it there that will do the dirty work lol then you just hit space and tell it to install on the sdcard.
Dont let your phone or computer go to sleep or the push will corrupt the file it can take up to 10 mins to transfer the file and once you hit enter it won't acknowledge its actually transferring Dont worry it is. It will tell you when its done how long it took and how much it transfered. After that you can flash the ROM and you should be golden man!
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
I've had no problems with 2.6 personally but either one will work. Once your in
Recovery you can download a ROM on your computer and on adb use.
adb push "C:\Documents and Settings\Josh\My Documents\Downloads\ViperDNA_1.3.5.zip" sdcard
Clearly that's how I would do it via my computer after you type adb push you can hit the space bar and drag the file to the command prompt and drop it there that will do the dirty work lol then you just hit space and tell it to install on the sdcard.
Dont let your phone or computer go to sleep or the push will corrupt the file it can take up to 10 mins to transfer the file and once you hit enter it won't acknowledge its actually transferring Dont worry it is. It will tell you when its done how long it took and how much it transfered. After that you can flash the ROM and you should be golden man!
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
thanks guys im going to try it when i get home in the morning...lol i got alot to learn!!
worm1977 said:
thanks guys im going to try it when i get home in the morning...lol i got alot to learn!!
Click to expand...
Click to collapse
Not a problem man I hope this helped let me know if your still having issues I'm no dev but I have gathered a plethora of knowledge over the years playing with stuff.
Sent from my HTC6435LVW using Tapatalk 2
@worm1977 any luck man?
Sent from my HTC6435LVW using Tapatalk 2
I am trying to help a friend who brought me his phone yesterday, I've searched everywhere and can't find anything that works. His phone is stock no root, it is locked and tampered with a security warning on 2.06. The RUU doesn't work because of 2.06. I can't get moonshine to work either. I can't get to recovery and I can push a recovery image either through adb. I'm out of ideas and figured the best place to go for help is the community. I can get fastboot and fastboot usb up but that's about as far as I can get. Does anyone have any ideas?
Sent from my Nexus 10 using XDA Premium HD app
Have you tried to boot into recovery through adb? Command would go like "adb reboot recovery". Or maybe I'm not understanding??? Does the phone boot like normal?
xhunter187 said:
Have you tried to boot into recovery through adb? Command would go like "adb reboot recovery". Or maybe I'm not understanding??? Does the phone boot like normal?
Click to expand...
Click to collapse
Thank you for the reply. The device only boots to the white bootloader screen. Selecting factory reset or recovery simply takes me back to bootloader. If i try to just boot into the device it stays at the htc splash screen. Adb shows no devices attached but I can still issue fast boot commands through terminal. I've tried pushing a recovery to it without success.
edjm711 said:
Thank you for the reply. The device only boots to the white bootloader screen. Selecting factory reset or recovery simply takes me back to bootloader. If i try to just boot into the device it stays at the htc splash screen. Adb shows no devices attached but I can still issue fast boot commands through terminal. I've tried pushing a recovery to it without success.
Click to expand...
Click to collapse
What did you type and what was the output when you tried to flash a recovery with fastboot?
crpalmer said:
What did you type and what was the output when you tried to flash a recovery with fastboot?
Click to expand...
Click to collapse
Fastboot flash recovery recovery.img
It sends then says
FAILED (remote signature verify fail)
edjm711 said:
Fastboot flash recovery recovery.img
It sends then says
FAILED (remote signature verify fail)
Click to expand...
Click to collapse
Of course it does, I forgot that you were locked when I posted that...
How was the phone unlocked? If it was facepalm then I believe that the token that was emailed from htcdev should still unlock the phone.
crpalmer said:
Of course it does, I forgot that you were locked when I posted that...
How was the phone unlocked? If it was facepalm then I believe that the token that was emailed from htcdev should still unlock the phone.
Click to expand...
Click to collapse
That's the problem. He doesn't know. All I was told when I got it is that it was updating ota and booted this way. I don't know how that's possible but I took it anyway thinking it would be an easy fix. I s-offed my dna when it first came out so I had no issue. If I can't get a token is he sol? At least until a ruu ( maybe) comes out for 2.06
crpalmer said:
Of course it does, I forgot that you were locked when I posted that...
How was the phone unlocked? If it was facepalm then I believe that the token that was emailed from htcdev should still unlock the phone.
Click to expand...
Click to collapse
Can he contact whomever he bought the phone from to see if they have a token the he could use to unlock it? Any idea how he broke the phone in the first place? It should be pretty hard to do so if he wasn't rooted and it was locked...
I don't know of anything else to try other than someone once claimed that Verizon stores could RUU. I highly doubt it, but you could always ask and see.
crpalmer said:
Can he contact whomever he bought the phone from to see if they have a token the he could use to unlock it? Any idea how he broke the phone in the first place? It should be pretty hard to do so if he wasn't rooted and it was locked...
I don't know of anything else to try other than someone once claimed that Verizon stores could RUU. I highly doubt it, but you could always ask and see.
Click to expand...
Click to collapse
Thanks! I work at verizon so I know we can't because our computers don't have recovery options any longer. I'll ask and see if I can get a token.
Team,
I've searched and tried to relock the bootloader with fastboot oem lock on my MAC and windows through the command prompt and the command is not recognized. I need to reset this damn DNA tonight before I send it back in to Verizon. Please give me a little assistance here. I have the RUU on my desktop also, I just dont know wtf is wrong with the command fastboot oem lock...
Yes I am restarting and chosing fastboot with the phone plugged in..
OverrideJones said:
Team,
I've searched and tried to relock the bootloader with fastboot oem lock on my MAC and windows through the command prompt and the command is not recognized. I need to reset this damn DNA tonight before I send it back in to Verizon. Please give me a little assistance here. I have the RUU on my desktop also, I just dont know wtf is wrong with the command fastboot oem lock...
Yes I am restarting and chosing fastboot with the phone plugged in..
Click to expand...
Click to collapse
Any love?
OverrideJones said:
Any love?
Click to expand...
Click to collapse
there is a thread in the dna android deveolpement forum that has all the info u need.
mopartonyg said:
there is a thread in the dna android deveolpement forum that has all the info u need.
Click to expand...
Click to collapse
There are many threads that I have read through...
when I fastbooted and so forth... I typed in the command box fastboot oem lock and that did nothing.
From what I read, you need to flash the lock boot loader zip to lock it.. Fastboot oem lock command won't work apparently if you have S-offed.
Sent from my DNA
Uzephi said:
From what I read, you need to flash the lock boot loader zip to lock it.. Fastboot oem lock command won't work apparently if you have S-offed.
Sent from my DNA
Click to expand...
Click to collapse
Thanks a lot and where is the lockbootloader zip located at along with the other files?
OverrideJones said:
There are many threads that I have read through...
when I fastbooted and so forth... I typed in the command box fastboot oem lock and that did nothing.
Click to expand...
Click to collapse
Read through this entire guide before you start any of them to make sure you follow the proper one.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my dlx using XDA Premium HD app
.torrented said:
Read through this entire guide before you start any of them to make sure you follow the proper one.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my dlx using XDA Premium HD app
Click to expand...
Click to collapse
Read this...
what does this mean?
Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice
Whos internal storage? SD card on the phone?
OverrideJones said:
Read this...
what does this mean?
Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice
Whos internal storage? SD card on the phone?
Click to expand...
Click to collapse
Yes. Flash it in a custom recovery
Sent from my Rezound
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Are there any places around maryland or northern va who can assist...? I would love to learn the terminology but it took me 4 days to learn how to code on a MAC to perform the dang root lol and not I cant image how long it would take to reverse it.
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Which process did u use to achieve s-off and unlock?
Sent from my dlx using xda app-developers app
jaymazz13 said:
Which process did u use to achieve s-off and unlock?
Sent from my dlx using xda app-developers app
Click to expand...
Click to collapse
Mine got given to me s-off.
Sent from my Rezound
What does your hboot say when you boot into bootloader?
Phaded said:
What does your hboot say when you boot into bootloader?
Click to expand...
Click to collapse
It says S-OFF unlocked ...
I do not know the process... I need to be walked through it to be fair. Not to sound incompetent lol
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Also, I am using clockwork mod...
What does the ENTIRE thing say?
Phaded said:
What does the ENTIRE thing say?
Click to expand...
Click to collapse
No worries now guys, I suppose now I have to give Verizon a damn good reason as to why my phone was rooted as hell. I have a decent alibi created.
Flash the lock boot loader zip as you would if flashing a ROM.
After that, do the RUU instructions, then s-on (fastboot OEM write secure flag 3). It is pretty simple.
Sent from my Rezound
Uzephi said:
Flash the lock boot loader zip as you would if flashing a ROM.
After that, do the RUU instructions, then s-on (fastboot OEM write secure flag 3). It is pretty simple.
Sent from my Rezound
Click to expand...
Click to collapse
Phone is gone now, however, what I did was...
restart phone, hold down volume blah...
boot loader fast boot and so forth, when fastboot USB popped up on phone on the windows computer open command up and type fastboot oem lock
some sort of error popped up.. so that is where I was. Pardon the english and grammar, had a few Jamesons'
OverrideJones said:
Phone is gone now, however, what I did was...
restart phone, hold down volume blah...
boot loader fast boot and so forth, when fastboot USB popped up on phone on the windows computer open command up and type fastboot oem lock
some sort of error popped up.. so that is where I was. Pardon the english and grammar, had a few Jamesons'
Click to expand...
Click to collapse
You can't lock the boot loader by fastboot commands, you needed to lock it by flashing the lock zip in recovery.
Sent from my Rezound