Related
how do i relock my bootloader on my amaze 4g
AndroidKing said:
how do i relock my bootloader on my amaze 4g
Click to expand...
Click to collapse
did you try:
fastboot oem lock
command?
Bootloader "Relocked"
I need to send Amaze in for warranty replacement, but bootloader shows as "Relocked." Do any of the legendary android dev heroes know if its possible to restore the Amaze bootloader to show "Locked" as it originally did. Not sure if the relocked status will void the warranty.
Throatchopper said:
I need to send Amaze in for warranty replacement, but bootloader shows as "Relocked." Do any of the legendary android dev heroes know if its possible to restore the Amaze bootloader to show "Locked" as it originally did. Not sure if the relocked status will void the warranty.
Click to expand...
Click to collapse
Not without s=off... The testers of s=off script I think are able to, but ours (s=on) will say "relocked."
Your warranty is probably still good... As long as it was a hardware issue... And if its a software issue, that can probably be fixed w/o sending it in
Sent from my HTC Ruby running Android Revolution HD
Thanks... I believe its a hardware issue. It was running fine on senseless rom, then all of a sudden it began overheating when charging, and the phone would just continually reboot until the battery was completely drained. It showed battery health was poor so I replaced the battery, but the problem persisted. The phone overheats when charging, and just keeps loading all the way to the home screen, then it auto reboots after less than a minute. I reverted everything back to stock to see if that fixed the problem, but it still does the same thing. T-mobile tech support said the prob sounds hardware related. Has anyone heard of software causing these problems? As far as I can find through searching s-off is still a no go for the average "instruction follower" like me. I dont wan t to jump into trying s-off when its still in the r&d stages and destroy an already limping device. thanks for all the help. There are many geniuses on XDA and I dont think you all get the credit u deserve.
You should be fine with it relocked then...
Sent from my HTC Ruby running Android Revolution HD
I don't know what happened. All of a sudden, my phone's WiFi functionality is totally shot.
No access points are detected, and when I try to switch WiFi on and off again, the phone locks up and reboots.
The last time I had flashed something was a week ago. I haven't even downloaded any new apps recently.
I was on jokersax's CM9 0.6.9.2 and 1.0 GHz kernel. After wiping data/cache, re-flashing joker's CM9, upgrading joker's CM9 to 0.6.9.3, and switching to faux's latest 1.0 GHz kernel, the problem persists.
Could I possibly have fried the WiFi chip on this thing somehow? It sounds crazy, but there were virtually no software changes made to the device prior to the incident.
Have you a nandroid backup of a rom with working wifi? I had same problem several times and restoring a backup with it working has always fixed mine.
Sent from my MB860 using XDA
I had the same. Mine just kept getting worse, until the phone kept rebooting at every phone call, and eventually every few minutes. Called warranty, and the said it is well documented problem and replaced both of my atrix phones. They said it was a hardware issue.
chrism.brunner said:
I had the same. Mine just kept getting worse, until the phone kept rebooting at every phone call, and eventually every few minutes. Called warranty, and the said it is well documented problem and replaced both of my atrix phones. They said it was a hardware issue.
Click to expand...
Click to collapse
That's unfortunate. Well, at least I know I'm not an isolated case.
So after charging overnight, WiFi worked for like 5 minutes, then proceeded to cut out again and continually reboot the phone until I turned off WiFi.
I would just send it to Moto, but of course their refurb/replacement units are bootloader locked... I doubt they'll even replace an unlocked device.
Looks like I'm screwed.
JPBeard21 said:
Have you a nandroid backup of a rom with working wifi? I had same problem several times and restoring a backup with it working has always fixed mine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I mean, the problem just started randomly; I was running that version of CM9 for a week already, so I doubt the ROM is the issue. I suppose I can try, though (if I even have a recent nandroid backup...heh)
Mine was unlocked and rooted. Just flash the latest sbf, and send it in. That returns it to locked stock.
chrism.brunner said:
Mine was unlocked and rooted. Just flash the latest sbf, and send it in. That returns it to locked stock.
Click to expand...
Click to collapse
He's saying he doesn't want to get a replacement back that has a locked un-unlockable bootloader. That's been happening lately.
stewartsoda said:
He's saying he doesn't want to get a replacement back that has a locked un-unlockable bootloader. That's been happening lately.
Click to expand...
Click to collapse
Yeah, that's the main reason.
So it seems Wi-Fi isn't 100% toasted. After a few cycles of toggle on, toggle off, toggle on, toggle off, lockup and reboot, toggle off, toggle on, lockup and reboot, toggle on, etc., I can end up connecting to Wi-Fi. It works, but then locks up and reboots after some amount of time (5-10 minutes usually) and then it doesn't connect anymore.
I don't know how, but maybe this could be a software issue? Could some system file that governs Wi-Fi have gotten corrupted somehow by some random process? Is there some system file I should check? Maybe flash a radio? I don't know.
All I know is that I'm gonna easily blow through my 2GB cap if I don't remedy this somehow.
(EDIT: My Smart Keyboard Pro settings got randomly wiped about the same time this started happening, but I have no idea how that could relate...)
EDIT2: Well, never mind, I found the thread in the Dev forum that has a bunch of people talking about this issue. Case closed, I guess, to some extent.
I unlocked the bootloader of the new phone. So, seems to me it is the way to go. Let them send you the new phone. Had to combine a few of the unlock methods, but everything is fine.
stewartsoda said:
He's saying he doesn't want to get a replacement back that has a locked un-unlockable bootloader. That's been happening lately.
Click to expand...
Click to collapse
I just unlocked a warranty replacement atrix with the newest att firmware... What are you talking about...
Sent from my MB860 using Tapatalk 2
hoodlikegaza said:
I just unlocked a warranty replacement atrix with the newest att firmware... What are you talking about...
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Well, since you are not everybody....
SBF/Bootloader Unlocking Blocked on New Atrix (forum.xda-developers.com)
Perhaps you got lucky when you got your phone back.
stewartsoda said:
Well, since you are not everybody....
SBF/Bootloader Unlocking Blocked on New Atrix (forum.xda-developers.com)
Perhaps you got lucky when you got your phone back.
Click to expand...
Click to collapse
That makes two of us then. Its still worth a try, because you can't hardly use the phone the way it is. At least with warranty you get a new one. If you are worried about bricking it leave it alone. At least it is useable.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
stewartsoda said:
Well, since you are not everybody....
SBF/Bootloader Unlocking Blocked on New Atrix (forum.xda-developers.com)
Perhaps you got lucky when you got your phone back.
Click to expand...
Click to collapse
Classic user error. The solution is right there in the very thread you posted...
Non-issue ftw.
Sent from my MB860 using Tapatalk 2
hoodlikegaza said:
Classic user error. The solution is right there in the very thread you posted...
Non-issue ftw.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Very well, I stand corrected. I read the posts when they were first posted but didn't follow them to the point that there was a resolution.
In the past I've sent back phones to VZ with custom stuff on it with no issue after receiving a replacement. Does anyone know if this is still the case?
corz123 said:
In the past I've sent back phones to VZ with custom stuff on it with no issue after receiving a replacement. Does anyone know if this is still the case?
Click to expand...
Click to collapse
if you can get into hboot then i would ruu just to be safe. if you cant get the phone to boot or anything then you should be fine.
If he locks the bootloader and installs the stock ics RUU, then he might not even need to send it back to verizon, unless he has a hardware problem.
HowardZ said:
If he locks the bootloader and installs the stock ics RUU, then he might not even need to send it back to verizon, unless he has a hardware problem.
Click to expand...
Click to collapse
this is true.
OP: whats the problem are you having with the device?
synisterwolf said:
this is true.
OP: whats the problem are you having with the device?
Click to expand...
Click to collapse
headset audio output is not working properly. hardware issue.
corz123 said:
headset audio output is not working properly. hardware issue.
Click to expand...
Click to collapse
had the same problem with my number 2 rez.
i would go back to stock with an ruu before returning it. if you dont they do have the right to deny you a replacement because root voids warranty.
At this point, I have to consider I have a hardware issue.
I am S-off and i have been on every RUU from Gingerbread to latest OTA ICS. I have tried MANY kernels with updated or modified radios and have the same problem through and through:
My bluetooth will not turn on and my wifi (depending on the ROM and or Firmware) will either stay on and intermittently say its scanning for networks or will toggle quickly back and forth from on to off by itself or get stuck at "turning on".
I have had no luck with BT or WIFI. I have spent hours searching forums for anyone in this same predicament and everyone else seems to get relief from updating Kernels or firmware, etc.
I was on CleanROM for the longest time with no issues (S-on at that time). Then the latest RUU came out and I flashed to VipreRez, since then, no wifi. Downgraded back to 3.xxx and back to CleanROM with no luck. I've tried updating kernels and manually pushing WIFI module files. Currently S-off to see if that was my issue but even going to the original GB RUU (1.xxx) and upgrading, I never had wifi or BT.
Im starting to think this is now a hardware issue. However, the wifi BT problem only happened after I upgraded to latest OTA.
I've been following directions on every flash for every rom, kernel, RUU, etc to no avail. Not a single one of them has allowed me to get wifi BT back.
Can anyone out there in their infinite wisdom give me a suggestion or perhaps something I'm over looking? THANK YOU SO MUCH
U aren't missing any of the contacts that make connection with the battery cover are you ?
Also, when you wipe before flashing are you making sure you flash boot ?
Sent from my Nexus 7 using Tapatalk 2
dottat said:
U aren't missing any of the contacts that make connection with the battery cover are you ?
Also, when you wipe before flashing are you making sure you flash boot ?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for replying. I'm S-off now so I didn't think it would be necessary to manually flash the boot.img. However, when I was S-on and first started having the problem, I would always flash the boot manually to no avail.
Also, I checked the backplate and everything is fine there. I've even gone as far as to place the phone directly on the wifi router to make sure it wasnt an issue with that. When the wifi starts glitching out and sliding itself off and on, it makes me think i can rule out backplate connections.
update
Update:
just flashed Rezound.Cubed.ICS.Kernel.1.0.7.Sense4 after wiping cache and delvik and WIFI now says "error". *shrug*
That typically happens when your WiFi libs don't match your kernel. S-off or not did you actually wipe boot and system before flashing? You symptoms sound very indicative of a dirty flash as you are ending up with mismatched components.
Sent from my Nexus 7 using Tapatalk 2
dottat said:
That typically happens when your WiFi libs don't match your kernel. S-off or not did you actually wipe boot and system before flashing? You symptoms sound very indicative of a dirty flash as you are ending up with mismatched components.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
just went into recovery and wiped dalvik/cache/boot. Flashed kernel. wifi stuck on "turning on".
Thanks for your thoughts and ideas to help fix
Wipe system/boot/data/cache and reflash viper again. Tell me if your WiFi works after that.
Sent from my Nexus 7 using Tapatalk 2
dottat said:
Wipe system/boot/data/cache and reflash viper again. Tell me if your WiFi works after that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
just did that and am stuck in boot loop... standby...
dottat said:
Wipe system/boot/data/cache and reflash viper again. Tell me if your WiFi works after that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was stuck in boot loop hell last night. Coudlnt even get out of it by flashing 3.14 RUU. Had to use the RUU for 1.xxx gingerbread. When that finally came back up - still no wifi. Kept getting error message: "Settings has stopped working". No wifi still, no BT.
Left my phone on gingerbread last night, it OTA'd ICS and still, no wifi, no BT, same error. I'm beyond baffled. *shrug*
MicahJamesNRCAL said:
was stuck in boot loop hell last night. Coudlnt even get out of it by flashing 3.14 RUU. Had to use the RUU for 1.xxx gingerbread. When that finally came back up - still no wifi. Kept getting error message: "Settings has stopped working". No wifi still, no BT.
Left my phone on gingerbread last night, it OTA'd ICS and still, no wifi, no BT, same error. I'm beyond baffled. *shrug*
Click to expand...
Click to collapse
If you're completely wiping your phone and installing the current OTA RUU and your wifi still errors, exchange it for a new phone.
A RUU should have fixed all your problems all together. Sounds like a hardware issue. Call Verizon, replacement should be sent within a 5 minute phone call.
HTC Rezound
luis86dr said:
A RUU should have fixed all your problems all together. Sounds like a hardware issue. Call Verizon, replacement should be sent within a 5 minute phone call.
HTC Rezound
Click to expand...
Click to collapse
wont they know that im s-off and modded ? ive never had to call verizon for an RMA issue. im not even sure if im within a warranty period
No they won't. They asked me a series of questions. (Did I factory reset, blah blah blah...) Told them I did, in which he then decided to ship me a replacement. Once I got replacement in mail, then I restored my Rezound to S-On and Locked. Simple as that.
HTC Rezound
What firmware is this phone on?
Sent from my Nexus 7 using Tapatalk 2
on latest OTA. should i bring it to my local Verizon store or call only?
thanks guys. looks like on my receipt i bought the phone on 9/18/2011
luis86dr said:
No they won't. They asked me a series of questions. (Did I factory reset, blah blah blah...) Told them I did, in which he then decided to ship me a replacement. Once I got replacement in mail, then I restored my Rezound to S-On and Locked. Simple as that.
HTC Rezound
Click to expand...
Click to collapse
dottat said:
What firmware is this phone on?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Just got off the phone with Verizon - theyre sending me a replacement Rezound refurbished.
Sadly, I think the hardware is nuked on this. Thanks for everyone's help
MicahJamesNRCAL said:
Just got off the phone with Verizon - theyre sending me a replacement Rezound refurbished.
Sadly, I think the hardware is nuked on this. Thanks for everyone's help
Click to expand...
Click to collapse
Make sure you check it fully once received. Verizon is know to send you devices with problems.
HTC Rezound
luis86dr said:
Make sure you check it fully once received. Verizon is know to send you devices with problems.
HTC Rezound
Click to expand...
Click to collapse
will do, thanks
luis86dr said:
Make sure you check it fully once received. Verizon is know to send you devices with problems.
HTC Rezound
Click to expand...
Click to collapse
hey so, do i just need to relock the Bootloader and S-on?
im paranoid they are going to tell me this is something I did.
I did. It's honestly up to you.
HTC Rezound
Hello all,
I've experiencing some problems with my GSM Evo 3d. The touch buttons (home, menu, back & search) are not (always) responsive when i puss them. So when i want to go the the home screen or to options the devices won't respond or sometimes responds a while (~>2 mins) later (multiple times). [Sometime it's also typing random letters or making random touch gestures (launching programs, typing in message e.g.)]
This problem I'm experiencing with multiple custom roms (CM10, CM9, mwakious3Drom, Virtuous_Eclipse) so i tried flashing back to stock rom (tried RUU_Shooter_U_HTC_Europe and RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio) but the problem persist. I believe the problem start when flashing CM9 DevilToast a view weaks ago, but I'm not sure. Before this i was running Virtuous_Eclipse for a few months without any problems.
Unfortunately i don't have a Nandbackup from stock anymore (lost/deleted it when switching sd card), so no going back to my original stock.
I've searched the forum and google but didn't find a thread similar or a solution. Anyone a clue to fix this issue or to whats it relating to?
Thanks in advance!
Sounds like your digitizer is going bad.
Jsparta26 said:
Sounds like your digitizer is going bad.
Click to expand...
Click to collapse
So it's hardware gone bad? No software problem?
That the buttons not responsive i get more often on custom roms, but that also could be judgemental since i hardly use(d) the phone when i'm back to stock.
(btw i'm s-off)
Honestly, the Rom itself is normally not the cause but rather the kernel you maybe using or the digitizer itself. What kernel have you been using if I may ask?
Jsparta26 said:
Honestly, the Rom itself is normally not the cause but rather the kernel you maybe using or the digitizer itself. What kernel have you been using if I may ask?
Click to expand...
Click to collapse
I believe when flashing one of the custom roms (CM9 or CM10 i think) i/it flashed a custom kernel. But since i flashed stock RUU rom.zip yesterday i guess it's back to htc kernel?
Tru 'settings, about phone, software info, more' the following kernel info is presented:
Kernal version:
3.0.16-ge733189
[email protected] #1
SMP PREEMPT
After reading your first reply about digitizer i found out that when applying pressure (by pushing) to the side of phone just above 2d/3d switch its 'applying touch' to the screen.
as said by Jsparta26 you have a faulty digitizer..I had the same problem...my phone had a mind of its own pressing things and not letting me do what i want...I think the only fix is going to service centre for replacement or fix...i got mine fixed..n its fine till now ! (i was noot rooted then)
invince2 said:
as said by Jsparta26 you have a faulty digitizer..I had the same problem...my phone had a mind of its own pressing things and not letting me do what i want...I think the only fix is going to service centre for replacement or fix...i got mine fixed..n its fine till now ! (i was noot rooted then)
Click to expand...
Click to collapse
Okay, looks like i've to get it fixed too...
Will the fix fall under warranty, or is warranty void bij unlocking hboot, rooting, and flashing custom roms e.g. ?
klooster said:
Okay, looks like i've to get it fixed too...
Will the fix fall under warranty, or is warranty void bij unlocking hboot, rooting, and flashing custom roms e.g. ?
Click to expand...
Click to collapse
Depends on your carrier. You could lock it down before taking it in. But is leave it s-off and just lock the bootloader.
Posted with Tapatalk 2
coal686 said:
Depends on your carrier. You could lock it down before taking it in. But is leave it s-off and just lock the bootloader.
Posted with Tapatalk 2
Click to expand...
Click to collapse
I bought the phone >1 year ago in an online shop plus a two year contract of KPN (=carrier). The website of the shop states an one year warranty of the shop itself and a two years warranty of HTC. After 1 year i'm suppose to send it directly to HTC. So carrier (KPN) isn't an issue right? And the bootloader is currently locked tru flashing RUU, thats allright? Or do i need to perform additional steps?
klooster said:
I bought the phone >1 year ago in an online shop plus a two year contract of KPN (=carrier). The website of the shop states an one year warranty of the shop itself and a two years warranty of HTC. After 1 year i'm suppose to send it directly to HTC. So carrier (KPN) isn't an issue right? And the bootloader is currently locked tru flashing RUU, thats allright? Or do i need to perform additional steps?
Click to expand...
Click to collapse
As long as your bootloader at the top says "locked" and back on full stock your good to go.
Jsparta26 said:
As long as your bootloader at the top says "locked" and back on full stock your good to go.
Click to expand...
Click to collapse
Relocked you mean right? Cause there is no way back to 'locked' once been unlocked right?
Actually, there is a guide that ramjet put together that will give you "locked" bootloader and s-off after you follow his guide to a T. Here it is http://forum.xda-developers.com/showthread.php?t=1889438
Hope this helps you.
Don't forget to hit my thank you button for the awesomeness lol jp:laugh:
Jsparta26 said:
Actually, there is a guide that ramjet put together that will give you "locked" bootloader and s-off after you follow his guide to a T. Here it is http://forum.xda-developers.com/showthread.php?t=1889438
Hope this helps you.
Don't forget to hit my thank you button for the awesomeness lol jp:laugh:
Click to expand...
Click to collapse
Allright, thanks! I'll look into the wire trick.
home mene back and search not hardware issue
I'm having similar problems with my s2 but i am responsible for them acting the way they are. (not working)
i was attempthing to flash jellybean to my sgh-i757m but before doing so i was told to press *#*#2662#*#* and press touchkey firmware update.
Since then my home menu back and search softkeys have not worked. I have done several factory resets and have also since then upgraded my ics to jb and still no buttons!!
dareshell said:
I'm having similar problems with my s2 but i am responsible for them acting the way they are. (not working)
i was attempthing to flash jellybean to my sgh-i757m but before doing so i was told to press *#*#2662#*#* and press touchkey firmware update.
Since then my home menu back and search softkeys have not worked. I have done several factory resets and have also since then upgraded my ics to jb and still no buttons!!
Click to expand...
Click to collapse
Seems to me you got lost. This forum has nothing to do with Samsung phones