[Q] Need to do Warranty exchange, how do I switch everything back? - Droid Incredible Q&A, Help & Troubleshooting

I tried the 2.2 Froyo Leaked rom and it is not working. I've tried several different roms and my touch screen is still not working. (not registering touches, registering erroneous touches). This has led me to believe that there is something wrong with the screen itself.
My phone is still under warranty but I would like to uninstall clockwork and find a completely stock, unrooted 2.1 ROM before I do the warranty exchange.
Can anyone point me in the right directions? I've searched the forums extensively but there are no ROMs or directions for getting rid of clockwork and reinstalling the default loader.
Thanks again for all your help.

gxs1 said:
I tried the 2.2 Froyo Leaked rom and it is not working. I've tried several different roms and my touch screen is still not working. (not registering touches, registering erroneous touches). This has led me to believe that there is something wrong with the screen itself.
My phone is still under warranty but I would like to uninstall clockwork and find a completely stock, unrooted 2.1 ROM before I do the warranty exchange.
Can anyone point me in the right directions? I've searched the forums extensively but there are no ROMs or directions for getting rid of clockwork and reinstalling the default loader.
Thanks again for all your help.
Click to expand...
Click to collapse
Stop at number 4 of the rooted instructions in the OP.

gxs1 said:
I tried the 2.2 Froyo Leaked rom and it is not working. I've tried several different roms and my touch screen is still not working. (not registering touches, registering erroneous touches). This has led me to believe that there is something wrong with the screen itself.
My phone is still under warranty but I would like to uninstall clockwork and find a completely stock, unrooted 2.1 ROM before I do the warranty exchange.
Can anyone point me in the right directions? I've searched the forums extensively but there are no ROMs or directions for getting rid of clockwork and reinstalling the default loader.
Thanks again for all your help.
Click to expand...
Click to collapse
You'll probably want to downgrade your radio, and then install one of the stock roms. I can't dig up any of links right now, but at least you know where to start searching...

....sits back and watches the **development** unroll in this thread...

zerf said:
....sits back and watches the **development** unroll in this thread...
Click to expand...
Click to collapse
No need to be smug. I am obviously new here.
I downloaded the ROM from the this forum, followed the instructions on this forum, so, naturally, I figured I should post my question on this forum.
Now if perhaps you'd like to actually be helpful like all the wonderful people in these forums and tell me where it should have gone instead, I'd be grateful.
Thanks.

do as douger1957 advised then my understanding is you can't simply use the RUU to get downgrade the hboot and radio but need to follow the instructions here:
hxxp://androidforums.com/all-things-root-incredible/123816-how-revert-back-earlier-version-hboot.html
hopefully you get that link before it is removed and good luck.

Related

Can someone link or show me where to get a rundown on how to root Froyo?

I am coming off a bricked phone so I am a little apprehensive about trying to root without a clear guide, especially froyo since it just got rooted from my understanding. I am sorry if this isnt in the right section, I really couldnt tell if this belonged in the General forum as it is a question, or if it belonged in the development as it is regarding Root/Roms. I would appreciate any help, and even any remarks on how I am misposting in this forum .
There is no root for froyo if you installed the official updates. You can try the previous methods but I doubt they work. You may be sol until someone decides to work on finding an exploit but I doubt that happens until there is an official release. The only rooted froyo that is out is for people who were rooted prior to froyo. Sorry.
If you have Froyo OTA (from Sprint) installed, you cannot yet root it (if/when someone releases root instructions). You have to already have your phone rooted with nand access and then install one of the rooted Froyo updates (there are two right now, from Avalaunch and netarchy). As well, there is a AOSP FROYO from cyanogenmod.
The wiki from toastcfh for this forum gives all sorts of instructions and options for rooting. Good luck.
swaze said:
There is no root for froyo if you installed the official updates. You can try the previous methods but I doubt they work. You may be sol until someone decides to work on finding an exploit but I doubt that happens until there is an official release. The only rooted froyo that is out is for people who were rooted prior to froyo. Sorry.
Click to expand...
Click to collapse
So please don't murder me for this question, i'm a noob coming from a pre.
I updated(or i should say my phone automatically updated) the 2.1 sprint image from the last update with the SD card Fix. This was before I got to this forum about rooting, etc.
Are my options to only go to the sprint store and get a replacement phone if I want to root now? Or is there a way to backtrack.
I tried to root last night but kept getting daemon errors when trying to connect to the phone. :S
manville140 said:
So please don't murder me for this question, i'm a noob coming from a pre.
I updated(or i should say my phone automatically updated) the 2.1 sprint image from the last update with the SD card Fix. This was before I got to this forum about rooting, etc.
Are my options to only go to the sprint store and get a replacement phone if I want to root now? Or is there a way to backtrack.
I tried to root last night but kept getting daemon errors when trying to connect to the phone. :S
Click to expand...
Click to collapse
What software version are you running? From homescreen go to menu>settings>about phone>software information and give me your software #.
1.47.165.1
I thought I could with this, because this is what the simpleroot software is showing in the program.
I did a full erase also last night with the volume down power button trick.
search for simpleroot 1.47 either on google, youtube, or here. there are loads of vids and tutorials
Also, there is a Q & A forum and would suggest you use that next time you have a question. You'll get your ass handed to you for posting in the dev section.
manville140 said:
1.47.165.1
I thought I could with this, because this is what the simpleroot software is showing in the program.
I did a full erase also last night with the volume down power button trick.
Click to expand...
Click to collapse
Are you on IM? it will be easier than doing this in the forum? I'm on yahoo will that work for you?
regulator207 said:
search for simpleroot 1.47 either on google, youtube, or here. there are loads of vids and tutorials
Also, there is a Q & A forum and would suggest you use that next time you have a question. You'll get your ass handed to you for posting in the dev section.
Click to expand...
Click to collapse
Yea I know. I didnt post this thread. i just posted IN it.
I tried simpleroot and it didnt work. I just wanted to confirm that it COULD work, instead of playing around with it aimlessly for hours. Only to find my phone was locked.
manville140 said:
Yea I know. I didnt post this thread. i just posted IN it.
I tried simpleroot and it didnt work. I just wanted to confirm that it COULD work, instead of playing around with it aimlessly for hours. Only to find my phone was locked.
Click to expand...
Click to collapse
Simpleroot is the best option to root v1.47. Unrevoked has known issues, AVOID it. Simpleroot was made from my earlier posting & guide of manually rooting 1.47, so I know it works. WATCH THE VIDEO he made!! It practically cups your nuts the entire way thru the process with both PC & EVO screen videos. Once you do simpleroot, I recommened doing toast's part 2. Right after that do a nandroid backup. Then apply one of the rooted Froyo ROMs posted in the dev forum (there are both odex and deodex versions posted).
However (as already stated numerous times in numerous threads) if you apply the OTA update, your screwed.

[Q] Any way to re-install OTA Froyo ?

I see I'm not going to get any help with my bluetooth issues, and since the problem only started AFTER Sprint pushed 2.2 to my EVO, I can deduce something got f'd up during the flash.
HTC has washed their hands of the problem because apparently, I'm special and am the only one complaining.
So my question is, can I re-install 2.2, and if so, how?
I thought about rooting, but I'm happy with the phone and doubt I'd use many of the benefits other than WiFi tethering.
Besides, it's too confusing. Nand? NAN back up? MSL? dalvik? RUU? Blah?
Not to mention root guides dated weeks b4 2.2 was even officially rooted! Try to follow one guide, and it describes a step you must do first by following another link.
Ask a noob question and you're likely to get an unrelated answer (Why would you want to do that?).
I just want to fix my fu*ing bluetooth!!!
Will this accomplish what I want, as far as re-installing 2.2 (even though I'm not rooted)?
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
leebo said:
Will this accomplish what I want, as far as re-installing 2.2 (even though I'm not rooted)?
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
Click to expand...
Click to collapse
Looks like it should-- everything except doing a NAND backup first, of course.
Although if Bluetooth performance is what you want, you really should root and install CM6 or some other ROM that actually uses a decent BT stack. It's really not that hard-- the stickied thread in the Development forum for rooting OTA 2.2 explains everything in real basic terms and works perfectly.
Many thanks.
So, I don't have to go back to 2.1 to re-install 2.2?
I'll try it this weekend. If it doesn't fix my BT problem, I'll try another ROM.
It's just, like I said. My BT worked perfect with 2.1. As far as other ROMS, maybe someday, but right now Android Market And AppBrain keep me busy.
Whoops! Forgot to ask, when they say "stock" RUU, does that include HTC Sense? I know a lot of people don't like it, but I do.
Well, now, I made the "mistake" of doing more reading, and now I'm more confused than b4.
So b4 you flash or restore a RUU (ROM?), you're supposed to do a "nand backup".
Someone suggested Amon_RA , so I went to this thread:
http://forum.xda-developers.com/showthread.php?t=705026&highlight=Amon_RA
There it says installing it will wipe all your info. But I thought this was supposed to let you back up?
Somewhere else I saw this:
Boot into recovery. Select Backup/Restore. Select Nand Backup.
How exactly? How do you boot into recovery mode? I found bootloader mode, but not reovery. I found a post where someone asked that same question, of course it wasn't answered.
The problem with forums is that everything is all over the place. People get tired of answering the same questions over and over, yet the reason most people ask the same questions is... everything is all over the place!
Forget about doing a NAND backup... you need root to restore it anyways, which you don't have, so it's pointless.
Just run the RUU. It will basically give you clean 2.2 image.
I am not worthy.
Do what Sohr said you will lose everything but you will have a clean image. When it comes to recovery to get to it you must first be rooted and have a custom recovery either Amon Ra( the link you left earlier) or Clockwork Mod recovery. To get into it you could use a free app from the market called quick boot that would bott you into recovery without using the bootloader...
It all seems complicated for the first week then it becomes natural on how to do it all. If you need help with anything PM me and maybe I can help you.
Thanks. Well, I did the deed yesterday. I will take anywhere from a few minutes to a couple of days to see if my problem is fixed.
Thanks for the help. I will probably try another ROM if this didn't work. At least now I have a sense of how to do it.
Well, it took minutes. Crap. Same problem (bluetooth audio cuts in and out on my end, but not on the other persons end).
HTC told me to go to hell. I wonder if Sprint has any units in yet. I con't believe I'm the only one with this issue!

[Q] Newb needs help/explanation about how to root my MT3GS 2.2.1

ok, ok put the stones down....DOWN. yes Im a newb, but im not an idiot. I have spent the last hour tonight (as well as searching a few times over the last 2 weeks) searching, not just this site, for a way to Root my MT3GS. and apparently its currently impossible.
Yes I am aware of these threads:
http://forum.xda-developers.com/showthread.php?t=1181214
http://forum.xda-developers.com/showthread.php?t=1108316
and http://forum.xda-developers.com/showthread.php?t=1189485
however none of these fully explains anything and after reading all the replies in these threads it seems that theres conflicting comments, which are confusing me to no end. so Basically I have 3 questions:
Can I root my MT3GS what is currently running the OTA push of 2.2.1?
IS there a way to get S-Off working on it?
Can I Put any new Rom(could very well be using hte wrong word, if so it should be easy to understand what i mean) on the phone so that I can remove all unwanted stock apps, install any marketplace app I had before, and (drum roll please) get NETFLIX to work on my phone?
thank you in advance to anyone who can help me. but please, please please don't just refer me to another thread, because odds are A) I have read it and it didn't explain it well enough for me to understand and feel comfortable doing it, or B) it didn't provide the needed programs or only discussed part of my question and didn't seem to fit up with other threads which covered the other areas.
in short:
1- yes, you can root it. i've done it 3 times on my phone
2- as far as now, no, unless the new method posted today actually reverts the hboot
3- yes, although there might still be some apps that are on the rom that you do not want.
hey txdeathray, thanks for your reply. I found eckres original post on a different site that was much more elaborate, but from what i read still doesnt specify the S-off problem. last post: forum.cyanogenmod.com/topic/28205-stuck-on-step-8-rooting/
SO basically, if I CANT get s-off working, then even if I put cm7 or whatever other version i find, as soon as I reboot my phone, it will undo everything I did and ill be stuck with 2.2.1 again.
Have you tried the unlockr.com way to do it? Their page has a vid following you thru the process.. id post the link but im mobile at the moment
Sent from my PG06100 using XDA App
Last I looked a couple days ago there was no way working method on unlockr. heck last week the only method involved goldcards, and my firned who rooted his droid refused to touch it.
JXM003 said:
hey txdeathray, thanks for your reply. I found eckres original post on a different site that was much more elaborate, but from what i read still doesnt specify the S-off problem. last post: forum.cyanogenmod.com/topic/28205-stuck-on-step-8-rooting/
SO basically, if I CANT get s-off working, then even if I put cm7 or whatever other version i find, as soon as I reboot my phone, it will undo everything I did and ill be stuck with 2.2.1 again.
Click to expand...
Click to collapse
No. You don't need S-OFF to keep a new ROM. And you won't lose root with S-ON.
To my understanding, you only need S-OFF if you want to be able to manage some things without having to reboot your phone into recovery, or to get to some system files you otherwise can't with S-ON.
I have not seen the need for S-OFF for my personal use of my phone.

So I think my HTC One V is bricked, can someone help?

So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.
matterlord1 said:
So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.
Click to expand...
Click to collapse
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
http://androidfiles.org/ruu/?developer=Primo
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.
FreakyFreakGA said:
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.
Click to expand...
Click to collapse
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.
matterlord1 said:
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.
Click to expand...
Click to collapse
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.
FreakyFreakGA said:
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.
Click to expand...
Click to collapse
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.
matterlord1 said:
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.
Click to expand...
Click to collapse
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.
Be sure to flash an OTA-compatible ROM. Try RhythmicROM or CyanPrimo, both of which I've used for a long time and can attest that they are better HTC One V ROMs.
matterlord1 said:
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.
Click to expand...
Click to collapse
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.
gotts101 said:
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.
Click to expand...
Click to collapse
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.
matterlord1 said:
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.
Click to expand...
Click to collapse
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.
gotts101 said:
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.
Click to expand...
Click to collapse
Yeah, make sure you find the right version for your radio, virgin mobile made a terrible move by updating it so you cant do much with it.
Or kernel or something, anyways mine was v5.2 and it was a pain, i think there was a lot more kernels available for older versions.
Best of luck, and if you are having problems with authentication then try using WPS, in some cases it fixes those types of problems.

Stuck on Samsung boot screen

I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!
General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.
Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.

Categories

Resources