So somehow today my port burnt up, phone wont work with ANY USB. I'm on an AOSP Rom, been running fine for 6 months, so who knows. But anyway.
What options do I have here? It's under warranty, but having rooted it obviously if I try to send it back like this, it wont go well. Any options for me at this point? I can get a charged battery, sister has the same phone so if there is a way to at least get this remotely close to where it needs to be, I can spend the time doing it.
Any insight would be great.
Mario
desantim said:
So somehow today my port burnt up, phone wont work with ANY USB. I'm on an AOSP Rom, been running fine for 6 months, so who knows. But anyway.
What options do I have here? It's under warranty, but having rooted it obviously if I try to send it back like this, it wont go well. Any options for me at this point? I can get a charged battery, sister has the same phone so if there is a way to at least get this remotely close to where it needs to be, I can spend the time doing it.
Any insight would be great.
Mario
Click to expand...
Click to collapse
Do you have a stockish nandroid? If not what if you bump your sisters phone, make a nandroid of stock, move the nandroid to your phone by ext sd card or other file transfer methods. Restore the nandroid on your phone, unroot in supersu, flash stock recovery with flashify app.
Or a good cell phone repair shop should be able to replace it for around 60 bucks. Unfortunately it's soldered to the board unlike samsung phones or you could just do it yourself. Phone comes apart super easy.
You are going to have to try to get a stock image to flash in recovery. Otherwise just wipe your system and data partitions so that there is no longer root. Granted, then you will still have custom recovery. You could probably dd if=/dev/zero over the recovery partition to wipe your recovery, too.
I've found that Verizon doesn't check too carefully, so at a bare minimum I would download and flash the stock ROM found here on XDA, then unroot using SuperSU. You'll still have a custom recovery, but typically I find Verizon only powers it up to make sure it works and that there isn't anything physically wrong with it before replacing it.
Related
So I can get into cwm recovery but my computer wont recognize my sd card so i cant restore a backup...any ideas? help appreciated..
Take the SD card out, put it in a different phone or an SD card adapter. Once you have a connection to your PC, put the backup on the SD card and put the SD card back in your phone. You will then be able to restore.
If you can't access your SD card even on your phone, you can follow a guide to flashing through fastboot by putting it on your phone that I think is in the CDMA development section.
well i lost everything. what do i need to flash other than the rom, kernel, and radio?
bo5ibbs said:
well i lost everything. what do i need to flash other than the rom, kernel, and radio?
Click to expand...
Click to collapse
damn beer, that't the 2nd accidental "thanks" tonight
shouldn't need anything but your apps and google stores what apps you've used if you told them to back your phone up.
okay so i think sprint fried my sd card when they tried to unbrick it. Other sd cards are recognized in recovery. What files do I need to flash to get my phone to boot again? stock rom? any rom? do i need to flash radios and kernel? I'm so aggravated lol
bo5ibbs said:
okay so i think sprint fried my sd card when they tried to unbrick it. Other sd cards are recognized in recovery. What files do I need to flash to get my phone to boot again? stock rom? any rom? do i need to flash radios and kernel? I'm so aggravated lol
Click to expand...
Click to collapse
...You took your phone to sprint to get it unbricked? A real brick is when the phone stops turning on completely and doesn't give an LED signal while it is plugged in to the charger. Anything else can be easily fixed. Not trying to sound mean, but yeah...
If you have a backup, I'm pretty sure all you need to do is restore from that. I'm not sure if it is possible to remove your radios unless you go into hboot and a flash a PG86IMG to purposely do that. Basically, you don't need to flash radios. Your kernel would hopefully be included in the backup/ROM. You can either restore from a backup or flash a (any) rom to get your phone starting up again.
Check out my handy guide on breaking your phone:
http://forum.xda-developers.com/showpost.php?p=17836714&postcount=2
Also, how did you lose everything?
its a long story but i can get into recovery, but my mac wont find my sd. I tried another sd and it found it, so it has to be a problem with my sd. They deleted everything from it when trying to fix it. I wanted to brick it to get a new 3d to trade to my buddy for his galaxy s2. I was rooted w CM and he said he wanted a fresh phone with no scrathes or root. So my buddy said to flash a gsm radio and battery pull in the middle of it to brick it. I did but they somehow got back to recovery but my sd is toast..
bo5ibbs said:
its a long story but i can get into recovery, but my mac wont find my sd. I tried another sd and it found it, so it has to be a problem with my sd. They deleted everything from it when trying to fix it. I wanted to brick it to get a new 3d to trade to my buddy for his galaxy s2. I was rooted w CM and he said he wanted a fresh phone with no scrathes or root. So my buddy said to flash a gsm radio and battery pull in the middle of it to brick it. I did but they somehow got back to recovery but my sd is toast..
Click to expand...
Click to collapse
Ah, I see. The way I bricked my phone (that didn't allow you to go into recovery) on purpose was by flashing the PG86IMG RUU that can be found in the CDMA development section. I was on 2.08 and half the stuff failed to flash. My phone wouldn't go past the HTC screen or go into recovery. I went to the bootloader and did "fastboot oem writesecureflag 3" or something like that to make it say S-ON and remove the -revolutionary- at the top.
I gave it to them and told them it wouldn't turn on. They checked HBOOT and verified it was S-On and tried going into recovery but nothing happened. They then said they would send me a replacement.
By the way, I did all this because 1/4 of the screen wasn't working but I didn't want to go through all their bullcrap so I did it the faster way by purposely breaking it.
makes sense. Well now I have a 3d that i said i lost, and tomorrow i'll be getting another i paid 100 dollars for. trading the new one for the galaxy to my buddy. But since this old one goes into recovery, i can possible fix it? should i just get a new sd card and flash the ruu? I'll check the meid and make sure it's clear, and if it is then i'll sell it for 100 bucks if anyone wants it. hboot 1.4
bo5ibbs said:
makes sense. Well now I have a 3d that i said i lost, and tomorrow i'll be getting another i paid 100 dollars for. trading the new one for the galaxy to my buddy. But since this old one goes into recovery, i can possible fix it? should i just get a new sd card and flash the ruu? I'll check the meid and make sure it's clear, and if it is then i'll sell it for 100 bucks if anyone wants it. hboot 1.4
Click to expand...
Click to collapse
If it turns on, it is fixable. In your case, you have to do is go into bootloader and flash the ruu. I'll warn you, though, it didn't work for me so I don't know if it will work for you.
Okay well I'll have to get a hold of another sd card first. I'd like to sell this thing.. You've been thanked!!
bo5ibbs said:
Okay well I'll have to get a hold of another sd card first. I'd like to sell this thing.. You've been thanked!!
Click to expand...
Click to collapse
Good luck!
I have a loose USB port on my phone, making it very hard to get a reliable connection between the phone and a PC. It still charges, although it's usually very slow to charge as well. Problem is, I've got CM7 and clockworkmod recovery running. I have a backup of my stock ROM which I could go back to, but I don't think that's sufficient for warranty repair. Is there a way to do the necessary ODIN/heimdall steps via WiFi (for flashing the stock image), or on the phone itself via a terminal emulator? If it's something that increments the flash counter, I have a jig that works if I apply pressure to it correctly (for now...again, loose USB port), so I can reset that back after. If I understand correctly, I basically just need a way to flash the stock recovery, and possibly flash the kernel back to unrooted, without USB.
Any help is greatly appreciated.
nd_geek said:
I have a loose USB port on my phone, making it very hard to get a reliable connection between the phone and a PC. It still charges, although it's usually very slow to charge as well. Problem is, I've got CM7 and clockworkmod recovery running. I have a backup of my stock ROM which I could go back to, but I don't think that's sufficient for warranty repair. Is there a way to do the necessary ODIN/heimdall steps via WiFi (for flashing the stock image), or on the phone itself via a terminal emulator? If it's something that increments the flash counter, I have a jig that works if I apply pressure to it correctly (for now...again, loose USB port), so I can reset that back after. If I understand correctly, I basically just need a way to flash the stock recovery, and possibly flash the kernel back to unrooted, without USB.
Any help is greatly appreciated.
Click to expand...
Click to collapse
You should flash back to your stock ROM backup first. Then, go on the market and download mobile Odin pro. With this app, you can flash kernels and stuff. Then you should download the stock kernel, and flash it to bring your phone back to Stock.
Sent from my SAMSUNG-SGH-I777
for a little more detail see this thread.
Thanks to the both of you. I've managed to get everything back to stock, and migrated to a replacement device. All that's left is to stick the phone with a bum USB port in the mail.
nd_geek said:
All that's left is to stick the phone with a bum USB port in the mail.
Click to expand...
Click to collapse
And do some more reading and searching before opening new threads.
I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.
As the title states, my Verizion SCH-i545 will lockup, shutdown and be unresponsive for long peroids of time ( read 24-96 hrs ) , unable to even take a charge.
What i think happened: I was trying to push boot loader files into my Kindle Fire HD 7" and *whoops* forgot to unplug my phone from the USB cord where it was charging merrily away. Since then I have gotten it to turn on a small handful of times - the most recent was after a 3 day wait for the battery to discharge and then it decided to accept a charge, worked for around 20 hours and then locked up again. Since that point it has been unresponsive.
I'm thinking that these boot loader files may have overwritten primary-boot and possibly secondary-boot sectors and sometimes the secondary-boot backup partition catches, and sometimes it doesn't.
I know what you all are thinking, and the guys I'm deployed with tell me the same thing - send it in as an insurance claim and get a new one. Well screw that, especially if I can get it done myself. I've also read that this is a possible hard-brick ( i don't think so since I can get something from it, sometimes ) and in need of a RIFF box to get this done properly.
At our last port, I was in the XDA-DEV chat room on snoonet and someone mentioned that the aboot.img may be disfigured or completely screwed, but being in port, I was fairly drunk and didn't save the log from that chat like I should have, does this sound right?
Can anyone give me any guidance as to what is going on with my phone and how to fix it? I have a stock Samsung ROM image on the way out here shipped from the states, but that's about a week away, at least. Will this be enough to fix it? Is there anything I can do to get my phone back operational in the mean time?
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=2735172
This is a link to the full wipe and no wipe nc5 tar images. Nc5 is the latest official firmware (4.4.2). These files are to be flashed with Odin. You can try the no wipe first so you don't lose your data but you might need the full wipe which will return you to total factory stock. I don't know how the network speeds are where you're deployed but be warned, these are big files.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2735172
This is a link to the full wipe and no wipe nc5 tar images. Nc5 is the latest official firmware (4.4.2). These files are to be flashed with Odin. You can try the no wipe first so you don't lose your data but you might need the full wipe which will return you to total factory stock. I don't know how the network speeds are where you're deployed but be warned, these are big files.
Click to expand...
Click to collapse
I appreciate the super quick reply. I know that I'm still running MDK base band but if I can still root the NC5 and reinstall my Hyperdrive, I'll be ecstatic about this. Maybe at our next port I'll be able to download some of these images, but if the image that I have coming from the states will work, then I'll just run with that.
As far as downloading goes, it's a no go out here. Satellite internet that barely allows me to browse XDA, let alone download a GB worth of files.
And as far as wiping? I have no qualms, I've already shed my tears over wiping my phone and somehow my SD card got corrupted and I lost all of my pre-deployment pictures with my family. I've already shed my tears and lost everything that I can lose on that phone. At this point I just want to get it working again. As a sort of GFY to Samsung who told me I needed to send it in to them to have it fixed with authorized samsung equipment and authorized samsung techs.
Anyways, thanks for the quick reply, once I get my image from the states and give that a whirl I'll report back here if it worked. if not, I'm just waiting for our next port to download some of these images and try try again.
breakneat said:
I appreciate the super quick reply. I know that I'm still running MDK base band but if I can still root the NC5 and reinstall my Hyperdrive, I'll be ecstatic about this. Maybe at our next port I'll be able to download some of these images, but if the image that I have coming from the states will work, then I'll just run with that.
As far as downloading goes, it's a no go out here. Satellite internet that barely allows me to browse XDA, let alone download a GB worth of files.
And as far as wiping? I have no qualms, I've already shed my tears over wiping my phone and somehow my SD card got corrupted and I lost all of my pre-deployment pictures with my family. I've already shed my tears and lost everything that I can lose on that phone. At this point I just want to get it working again. As a sort of GFY to Samsung who told me I needed to send it in to them to have it fixed with authorized samsung equipment and authorized samsung techs.
Anyways, thanks for the quick reply, once I get my image from the states and give that a whirl I'll report back here if it worked. if not, I'm just waiting for our next port to download some of these images and try try again.
Click to expand...
Click to collapse
Man that's rough now I see why you have to have it shipped. Hope it works.
Op makes good on promise! Op replies!
My files got here the other day, and I was able to reflash with MJ7 firmware. After that I spent a solid 2 hrs ( had to pay off people to download these files - limited computer time and what not ) downloading Safestrap and Saferoot and then subsequently installing an old copy of Hyperdrive ( RLS 14 ). Could I have just flashed Hyperdrive with Odin and been okay? Or did I have to have a stock firmware to repair the issue? BTW, thats 7MB in 2 hours.
Also, I've been reading up on Hyperdrive RLS 17, and it says that I've got to flash NC5 firmware before I do RLS 17? With Safestrap, would I just flash NC5 into the stock slot, and then HD 17 into a subsequent slot? Or could I do like I did with HD14 and flash right into the stock slot with no apparent issues.
BTW, you being the only respondent to this post, I thank you lots for your help.
So my wife broke her phone. (A car ran over it) .
As you can imagine the phone is pretty messed up. Originaly the phone still worked(for a few weeks) and then she bought a new phone and left that one.
Now a few weeks later i try to turn it on to take the pictures off and it boots into the bootloader and thats where i am in need of your help. If there a way for me to get the pictures off of this phone?
You're most likely out of luck. Without booting into the OS, the only alternate way you would have a chance is if had a custom recovery. You don't, unfortunately, as the bootloader is obviously locked. It would have to be unlocked before you could install the recovery, but on HTCs, that process wipes the phone. Only thing you could try would be to boot to the stock recovery and wipe cache. Works in some cases, but if you wipe anything else via factory data reset, it'd wipe everything as well. Sorry. It'd basically take some NSA level stuff to be able to extract anything else in this state, if at all.