I was running my TF with prime v1.5 and an overclock kernel (at 1.4GHz variable rate with setCPU). It all worked like a charm. Then the unlock screen froze and the screen went dark.
I have tried everything to reboot but nothing works (including volume- + PWR for CWM, etc).
I can get into APX mode though and I have tried nvflash with the nvflash version prime 1.5. However after working for several steps the process stops each time with this message:
failed executing command 14 NvError 0x30012
command failure: create failed
I am not sure what to do at this point and I am thinking the TF is irreversibly bricked.
Here are my questions:
1. Anything I can do to fix this with nvflash? I was thinking of trying v1.4 of prime but I am doubtful it will make any difference.
2. If it is truly bricked is there any way I can wipe the system in APX mode before maybe sending it in for service?
3. Anyone have any experience with ASUS service on this? I believe that I have technically voided the warranty with the root/mods.
Thanks for the help.
mike infinity said:
I can get into APX mode though and I have tried nvflash with the nvflash version prime 1.5. However after working for several steps the process stops each time with this message:
failed executing command 14 NvError 0x30012
command failure: create failed
Click to expand...
Click to collapse
That doesn't look healthy. I take it that error comes up on the TF itself, or is it on your computer?
mike infinity said:
1. Anything I can do to fix this with nvflash? I was thinking of trying v1.4 of prime but I am doubtful it will make any difference.
Click to expand...
Click to collapse
Assuming you followed the steps exactly as laid out and you still got problems (like the above error, for instance), you could be in trouble. Perhaps the overclocking you performed killed it? Not sure.
mike infinity said:
2. If it is truly bricked is there any way I can wipe the system in APX mode before maybe sending it in for service?
Click to expand...
Click to collapse
I'm not sure there is, I think APX mode is only for flashing a new ROM.
mike infinity said:
3. Anyone have any experience with ASUS service on this? I believe that I have technically voided the warranty with the root/mods.
Click to expand...
Click to collapse
Yes you have voided the warranty, manufacturers of Android devices in general don't look too kindly upon you rooting their devices and trying to claim warranty, given that it's your risk not theirs. A bit like seeing if your TF would survive a drop from a tall building on purpose, and then trying to claim warranty if it breaks as if it's their fault .
you should try the 1.4 nvflash because the 1.5 didnt work for me too. There are some files missing i assume.
The description u just gave seems more like hardware failure than software. Anyway worth to try since u get to apx.
Good luck m8
Link to download 1.4:
http://www.sdx-downloads.com/devs/roach2010/flash_roms/
The error comes up on the computer, not the TF.
sounds like you have fried your hardware...but I am no expert or hacker. I have loaded kernel celsym blades, running at 1.4 well, doing a lot of stuff running fine so it shoulnt have done anything. I would recommend PMing the developers of Prime and Kernels the development section, if someone there is able to answer?
mike infinity said:
The error comes up on the computer, not the TF.
Click to expand...
Click to collapse
Sounds more like the .img files are not in the right place. Make sure the system.img, boot.img and recovery.img files are in the same directory as the nvflash files. Cheers.
MasterfullDON said:
sounds like you have fried your hardware...but I am no expert or hacker. I have loaded kernel celsym blades, running at 1.4 well, doing a lot of stuff running fine so it shoulnt have done anything. I would recommend PMing the developers of Prime and Kernels the development section, if someone there is able to answer?
Click to expand...
Click to collapse
The OP already said that CWM isn't working.
UPDATE:
I used the nvflash version of prime v1.4 and the process completed successfully! Not sure what the problem was with v1.5 (I had the correct files in the correct folder in the process). When I replaced with v1.4 nvflash completed successfully and the system rebooted.
However, there now seems to be another problem: When the system boots up it asks me to plug in the charger as the battery is low....It then shuts down even though the charger is plugged in.
I did plug in the TF when it was bricked (APX only)...but I am guessing it was not charging at the time.
Now that it is re-imaged and is able to boot, I assume it would be able to recharge. This does not seem to be the case.
Any thoughts?
mike infinity said:
UPDATE:
I used the nvflash version of prime v1.4 and the process completed successfully! Not sure what the problem was with v1.5 (I had the correct files in the correct folder in the process). When I replaced with v1.4 nvflash completed successfully and the system rebooted.
However, there now seems to be another problem: When the system boots up it asks me to plug in the charger as the battery is low....It then shuts down even though the charger is plugged in.
I did plug in the TF when it was bricked (APX only)...but I am guessing it was not charging at the time.
Now that it is re-imaged and is able to boot, I assume it would be able to recharge. This does not seem to be the case.
Any thoughts?
Click to expand...
Click to collapse
Are you trying to charge via USB? If so this won't work (not very well, at least), you have to be plugged into the wall to charge.
I am using the power supply. I have checked all of the connections to make sure the box that plugs into the AC is solid, etc.
I have noticed a few threads on bad charging units...maybe mine got fried somehow (although seems like a strange coincidence for both my charger and the TF to get bricked simultaneously...the TF was recharging at the time it was bricked).
I am going to spend $20 and get a dynex charger that others report to work with the TF. If it doesn't I will return it.
UPDATE:
Well, I got the dynex dx-ua for $10 (open box)...and now my TF is working perfectly again! I will now begin the process of reinstalling my apps and getting back to v1.5 with CWM.
I'm not sure what gives with the power supply...maybe that was the issue from the beginning and not the v1.5 + overclock...or maybe the overclock killed the PS as well as caused the brick? I don't see how it could cause a brick since the TF seems to work normally now with no hardware failure (except the PS).
Anyway I guess these forums are a blessing and a curse. On the one hand we get great mods that greatly enhance the user experience in some cases and we get fixes when things go wrong. On the other hand we get the potential for bricking and voiding the warranty.
I am liking this dx-ua charger from dynex. It has connectors for every device in my collection. A small bonus after a week of believing my TF was toast.
mike infinity said:
UPDATE:
Well, I got the dynex dx-ua for $10 (open box)...and now my TF is working perfectly again! I will now begin the process of reinstalling my apps and getting back to v1.5 with CWM.
I'm not sure what gives with the power supply...maybe that was the issue from the beginning and not the v1.5 + overclock...or maybe the overclock killed the PS as well as caused the brick? I don't see how it could cause a brick since the TF seems to work normally now with no hardware failure (except the PS).
Anyway I guess these forums are a blessing and a curse. On the one hand we get great mods that greatly enhance the user experience in some cases and we get fixes when things go wrong. On the other hand we get the potential for bricking and voiding the warranty.
I am liking this dx-ua charger from dynex. It has connectors for every device in my collection. A small bonus after a week of believing my TF was toast.
Click to expand...
Click to collapse
This is just my suggestion so take it as you will, but i would VERY strongly suggest flashing stock and running this unmoded for a few weeks. I know it would be a pita to reinstall your apps twice, but if there really is a problem with the hardware, it might rear its head again. This way, if you need to rma it, you are completely stock.
I'm not sure what gives with the power supply...maybe that was the issue from the beginning and not the v1.5 + overclock...or maybe the overclock killed the PS as well as caused the brick? I don't see how it could cause a brick since the TF seems to work normally now with no hardware failure (except the PS).
Click to expand...
Click to collapse
The overclock may include upping the voltage to the cpu. This might have caused the load on the power supply to be too high to power the unit and charge the two batteries, and burnt out the power supply.
AustinMartin said:
The overclock may include upping the voltage to the cpu. This might have caused the load on the power supply to be too high to power the unit and charge the two batteries, and burnt out the power supply.
Click to expand...
Click to collapse
This is my guess as well.
The tablet did freeze on the lock screen as well...yet the hardware seems none the worse for wear with the new power supply.
Related
I'm running Darky's 6.0 Rom with xcaliburinhand's kernel. I began to realize my phone wouldn't charge when I plugged it into the charger. I tried flashing to stock using odin but once I'd get into download mode via the long-press menu when pressing the power button (because other methods that involve plugging in the cord and pushing buttons doesn't work since it's not recognizing the cable). I don't think it's a faulty cable or port since everything was working before I flashed the ROM. Anyone have any ideas on how to get the computer to recognize the phone so I can flash stock??
edit: When I do plug in the phone to the computer, I'll sometimes get a message saying the device isn't recognized.
(And yes I do have drivers installed.)
Also, I tried flashing other ROMs via CWM but I get error messages on all that I try. Such as can't mount .dev/block/st19 and can't mount SYSTEM
Edit: After a while I've noticed that it in fact is charging but the battery icon doesn't show it's charging. And in settings it shows it's not charging. But battery level is increasing
Have you tried a different computer to see if the usb port is bad?
Sent from my SAMSUNG-SGH-I897 using XDA App
Does it charge when you plug it into an ac adapter? You can also try reinstalling the drivers and see if that helps and/or try a different usb port. I've had issues with the drivers before.
Also try a different cable. My cable became defective somehow where xp no longer recognized it, yet would still show charging on the phone. All was back to normal after I got another "data/sync" cable.
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't have a different computer to try it on but I've tried different ports. It's not the computer because it still won't show it's charging when I plug into the wall. And yes I think it does charge when it's plugged into a wall but it doesn't show it or turn on when I plug the cord into the phone. I don't think it's hardware. It has to be software since it just happened when I flashed the ROM. Also whenever I open contacts I get a force close of acore (a little off-topic, but still another issue). I also have tried reinstalling drivers. But also, it doesn't work when plugged into a wall charger. So it's definitely nothing with the computer
I just need to know if anyone knows how to force the computer to recognize the phone so I can flash to stock and hopefully that'll resolve the issue
update: I also tried v7 via CWM and no luck still.
Well I update xcaliburinhand's kernel by transferring it over bluetooth and that installed fine over CWM. Then I tried updating Darky's rom to v7 and that worked too. I booted up and got a million FC's. Tried to get into recovery and it just sits at AT&T screen. It's very tricky to even boot up the phone, and even when I do I can't do anything because of all the Force closes. I can't get back into recovery mode with any button combinations and when i try via the power long press I can get into download mode fine, but I still have the issue with the computer not recognizing it, so it's useless. Anyone have any ideas????? I'm getting sick at staring at this AT&T boot screen for so long. I have no idea of what to do next. Someone please help!!
Sorry to say it, but it sounds like your phone has serious hardware problems.
opcow said:
Sorry to say it, but it sounds like your phone has serious hardware problems.
Click to expand...
Click to collapse
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.
well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.
zoubidou said:
well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.
Click to expand...
Click to collapse
Please read earlier posts... I cannot get into recovery mode and the computer won't recognize download mode.
mikel.canovas said:
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.
Click to expand...
Click to collapse
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.
opcow said:
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.
Click to expand...
Click to collapse
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.
mikel.canovas said:
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.
Click to expand...
Click to collapse
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.
opcow said:
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.
Click to expand...
Click to collapse
Ok. Thanks. If anyone else has any other ideas. Please post
I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?
mikel.canovas said:
I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?
Click to expand...
Click to collapse
Or you could just rob a liquor store and use the proceeds to buy a new one.
So my tablet got unplugged during the NVFLASH process shortly after formatting the partitions. It is now stuck in NVFLASH. Is there anyway I can reboot it or do I need to wait for the battery to drain and for it to die.
I have been having problems with my power button not responding when pressed so I filed for an RMA. They said to send it back but I wanted to flash back to stock before sending it. Could I send it to them like this ans say that it just stopped working or do I need to reflash to stock. Its a B50 so I know it can be fixed I just dont want to waste time waiting.
If you still have service on your tf they will repair your power button , i don't know if they flash new software files because of your button. What i do know they have to test your button and then they will see that it won't boot.
So with a bit of luck they will flash new files bcause of the whole startup problem with the power button.
Good luck
Let the battery drain, and NVFlash to stock. It will seriously help if you don't want to deal with any crap if they see you were rooted.
You don't have to let the battery drain.
When I bricked mine, my battery was low when I started the nvflash process, then the process failed b/c I forgot to put the files where they were needed, so I unplugged my transformer, let it charge for a little bit more so the battery wouldn't die while I found the files needed, then I plugged it back into my laptop and did a reboot into nvflash and let it do it's thing.
So I am having a weird issue with nvflash; it randomly quits mid-process. Sometimes nvflash stops when initializing the boot loader while other times it starts formatting the partitions and then stops. A few times it has even kicked my tablet out of apx mode.
Has this ever happened to anyone?
Is your cable bad? That's all I could think of, try several different USB ports as well.
Thing O Doom said:
Is your cable bad? That's all I could think of, try several different USB ports as well.
Click to expand...
Click to collapse
I tried multiple usb ports on two different computers. My macbook running ubuntu and a windows pc both have the same issue. I will try using another cable but dont know if that will help.
If I send the tablet back in this condition (no OS and NVFLASH not working), will they say its user error?
So I was never able to get the tablet to boot up. I am not sure what the issue was but I believe that the battery was almost dead but not quite. This left the tablet in nvflash mode, unable to charge. When I tried to transmit data however, it created too much of a load on the tablet and it would fail. I sent the tablet to asus as is and I just got a notification that they fixed everything and are sending it back to me. In case somebody is in the same situation as me it seems they did not care that all the partitions were formatted blank, just that there was no custom rom installed.
Good that it was resolve, and that they didn't give you any trouble.
So last week my B70 TF101 suddenly started to gave up on me... Rooted and running ARHD 3.4.0 for about a week, in the morning all was ok, played with it a little bit and put it away (not sure if I turned it off or locked screen only) and in the afternoon it didnt wake up anymore. Black screen, I could still here e-mail notifications and docking sound when plugged in the dock.
Repeatedly tried to hard reset, get into CWM recovery, and finally tried to hook it up to my desktop to get into APX mode. Got sure it was charged until dock LED was lit green, also had it hooked to charger directly for a few hours (without dock).
At this point when blindly tried to reset/power off/power on I did not hear any notification anymore except for the occasional camera shutter click but as I have no feedback if its on or off or whatever mode it was in I dont know if its running anymore or not.
Strangely not even my desktop recognizes it when plugged in with USB, trying to get into APX (vol up + power >6sec), no USB notification sound in Windows, new hardware found, refresh of the Device Manager tree, nothing.
I feel at least the backlight is defect but that doesnt explain the no response on USB so looks like there is more to it than just the backlight. I also tried to use a flashlight but cannot detect any screen activity.
So I decided as I still have 2 months warranty I would RMA it. It is beeing picked up tomorrow but have not been able to unroot and install stock recovery/rom...
Now my question is, what chances do you think I have if, lets asume, also the Asus repair centre cannot get access over USB so they wont notice it was rooted, will repair/replace it and send it back?
Did any of you guys manage to get your rooted TF101 repaired and returned under warranty? Or did you get charged? If so how much?
Thanks for any replies!
NVFlash is out for SBK2 devices, use that and repartition your device.
http://forum.xda-developers.com/showthread.php?t=1676845
whitekidney said:
NVFlash is out for SBK2 devices, use that and repartition your device.
http://forum.xda-developers.com/showthread.php?t=1676845
Click to expand...
Click to collapse
Yes thanks, and so I noticed, but that brings me to 2 questions:
1. I am not familiar with Linux.. Does that mean I have to wait until the tool is released for windows?
2. It clearly says "All usage requires booting your tablet into APX mode by connecting it to USB, turning it off and turn it back on while holding Volume Up!".
There is absolutely no response when I connect my TF101 by USB and try to enter APX mode. Would that be different on Linux?
FYI, I used APX a few times about a year ago to gain root, so I am not unfamiliar with this method. I know the USB hardware detected sound in Windows should sound when APX mode is entered and besides it should show up in the deivce manager. Neither is the case.
APX mode is power-volup, just to be totally clarified. Try reinstalling the apx drivers on windows manually, and you don't have to install linux totally, you can use a LiveCD or virtualbox to run NvFlash
You're right, typo edited.. I will try your suggestion, thanks.
Sent from my HTC One X using xda premium
wait, don't bother with windows drivers, you need linux if you're Sbkv2. They'll most likely notice if you're on a ROM, definitely if you have recovery, and may or may not charge you for repairs.
Thing O Doom said:
wait, don't bother with windows drivers, you need linux if you're Sbkv2. They'll most likely notice if you're on a ROM, definitely if you have recovery, and may or may not charge you for repairs.
Click to expand...
Click to collapse
Update: some progress... guess what.. tried my friends USB cable and presto.. APX mode, was able to flash stock rom (http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/ROMS/NVflash+STOCK/ICS+.21). Following succesful flash, tried powering off and on + voldown to get in recovery but does not give ANY visual feedback.
So still zero screen activity, during flashing, booting, whatever. At least I got it back to stock and can now turn it in for repairs...
Good, rma that and it should be fixed without complaint from asus.
Thing O Doom said:
Good, rma that and it should be fixed without complaint from asus.
Click to expand...
Click to collapse
Thanks, will do... might as well toss in the cable too
As the title says.
Thinking of getting this device on the cheap. I have a Moto factory cable that i've used to flash stock firmware onto a couple different devices.
Would that same cable work on this device to get it into fastboot?
Are there any cases of completely hard bricked devices?
Also, if any of you experts know some questions i might want to ask the guy, I'm all ears! Thanks!
Markyzz said:
As the title says.
Thinking of getting this device on the cheap. I have a Moto factory cable that i've used to flash stock firmware onto a couple different devices.
Would that same cable work on this device to get it into fastboot?
Are there any cases of complete hard bricked devices?
Also, if any of you experts know some questions i might want to ask the guy, I'm all ears! Thanks!
Click to expand...
Click to collapse
You can use the moto factory cable on the xoom but that just gives it power to fastboot.
You can have a xoom be hard bricked. If you plug it in and it shows up as a APX device it is hard bricked. (i own one that's sits in the drawer for spare parts for it's replacement) The charge light will still come on.
What type of xoom is it a (wifi 3g/4g family edition)
You should ask what caused it to brick?
was he rooted?
If you buy it post here and I can give a one click restore for it. AI have it for most versions of the xoom.
Be Sure...
Before you buy it I would recommend getting as much information as possible from the seller as this device may be beyond repair. If the device can still be recognized in fast boot then you should be fine.
if it is a 3g/4g xoom you might want to get the esn/meid number and check with verizon if it is clean.
If the bootloader is damaged it is of no use other than spare parts. You must at the very least be able to get to fast boot. If it is not recognised when plugged into the USB there is nothing to be done without serious hardware hacking.
I have one just like that in a box. It is rare, but it happens. It will not even flicker when powered up - nothing.
Grege50 said:
If the bootloader is damaged it is of no use other than spare parts. You must at the very least be able to get to fast boot. If it is not recognised when plugged into the USB there is nothing to be done without serious hardware hacking.
I have one just like that in a box. It is rare, but it happens. It will not even flicker when powered up - nothing.
Click to expand...
Click to collapse
This morning while loading a webpage (20% of battery life left) my MZ601 just froze, didn't respond to any screen or button presses, slowly went to sleep and has resisted all attempts to start since then. Even hooked up to the charger for the last hour, it still doesn't respond no matter what buttons I press, completely blank, no lights, nada...
I'm guessing it's a dead parrot, has anyone else had a similar Xoom death?
EDIT: Just found a more appropriate thread, ignore...
So I have a RAZR MAXX HD that has been rooted running Cyangenmod 10.2 and bootloader unlocked for a few months now. But the last couple weeks, each time I plugged phone up to charge, it kept starting a reboot loop. Each time it reached the start of Cyanagenmod boot logo, it restarted. So I thought maybe it was a bug in the latest Cyangenmod. So I tried updating. But I didnt realize that I accidentally chose Cyangenmod 11, thus when it was installing in Clockwork Mod Recvoery, it errored out about 1/3 of the way through. This erased everything.
So I was going to try hooking up to my MacBook and using fastboot to load new OS. However, as soon as i plugged in my phone, my computer shut down and would not turn back on. Had to go to Apple store to do a hard SMC reset. Thought that was a fluke and tried using my computer again and same thing happened. Phone still has CWM recovery working (i think properly). How do I get a working phone again? I tried putting OS on SD card on another phone and putting SD card my MAXX HD in and trying. That installed OS fine but when i rebooted, it still would not go past "bootloader unlocked" warning screen.
Also, I tried once more to plug in to my computer once more last night. However, it did not shut my computer down, but I did get a warning from OSX to unplug the USB device that was consuming too much power.
Any help would be appreciated! Thanks!
i would tend to be more concerned as to why its drawing to much power before trying to get it working again. did you try another usb cable? and check the charging port for debris? seems like something is causing a short circuit. this wouldnt be noticable while charging normally except it would likely take longer than it should to charge. if you rule out the things i have suggested above and its still has the short then there is likely a hardware issue, which over time will certainly get worse to the point of failure.
i dont see how a software issue would effect the charging circuit, i could be wrong.
bweN diorD said:
i would tend to be more concerned as to why its drawing to much power before trying to get it working again. did you try another usb cable? and check the charging port for debris? seems like something is causing a short circuit. this wouldnt be noticable while charging normally except it would likely take longer than it should to charge. if you rule out the things i have suggested above and its still has the short then there is likely a hardware issue, which over time will certainly get worse to the point of failure.
i dont see how a software issue would effect the charging circuit, i could be wrong.
Click to expand...
Click to collapse
Thanks for replying. I have tried multiple USB cables and they all do the same. And I know it isnt my computer USB slot since other devices/phones do not trip my power on my MacBook. Do you or anyone else who might read this reply know if I could send the phone in for repair under warranty considering it is rooted and bootloader unlocked? Im not too sure if unlocking the bootloader could cause power issues like this and if companies would even help for hardware issues since it is rooted/unlocked.
vol4life27 said:
Thanks for replying. I have tried multiple USB cables and they all do the same. And I know it isnt my computer USB slot since other devices/phones do not trip my power on my MacBook. Do you or anyone else who might read this reply know if I could send the phone in for repair under warranty considering it is rooted and bootloader unlocked? Im not too sure if unlocking the bootloader could cause power issues like this and if companies would even help for hardware issues since it is rooted/unlocked.
Click to expand...
Click to collapse
i don't see how rooting or unlock the bootloader could cause this as they are both generally software.
sending it in under warranty is a big risk imo, you would be better off if it was fried and they couldn't see the bl unlock and root. if they see it, they could likely bill you for the replacement phone, if they don't notice, you will likely get a refirb that's updated past the point of unlocking. so there will be no more modding. plus the phone is a couple years old, personally i would look to upgrade.
just some food for thought.
btw, i shelved my rmhd for a g2, the rmhd is a great phone, but the g2 just blows it away in almost every aspect.
bweN diorD said:
i don't see how rooting or unlock the bootloader could cause this as they are both generally software.
sending it in under warranty is a big risk imo, you would be better off if it was fried and they couldn't see the bl unlock and root. if they see it, they could likely bill you for the replacement phone, if they don't notice, you will likely get a refirb that's updated past the point of unlocking. so there will be no more modding. plus the phone is a couple years old, personally i would look to upgrade.
just some food for thought.
btw, i shelved my rmhd for a g2, the rmhd is a great phone, but the g2 just blows it away in almost every aspect.
Click to expand...
Click to collapse
Thanks man.. Yea i was kind of thinking the same thing but wasnt too sure. Maybe I can go somewhere locally and see if they can repair it for cheap. After having a phone that goes 1.5 days on one charge, I got spoiled. LOL plus I love the build quality much more than most oter phones like S3/4 etc.