Hey guys, I have a possible workaround until someone figures out how to unlock the bootloader.
I've heard countless people saying that the only differences between the US versions of the Galaxy S III is the radio. So, since we don't have an unlocked bootloader anyway, flashing a ROM in recovery wouldn't mess with the kernel OR the radio.
I've tried flashing a Cyanogenmod nightly for the AT&T version but I got this message:
assert failed: getprop("ro.product.device") =="d2att"
Installation aborted.
Is there any way to work around this to attempt an unofficial port?
This isn't R&D, it is just a question, and therefor still belongs in Q&A since YOU are not DEVELOPING it.
DO NOT POST A THREAD IN DEVELOPMENT UNLESS YOU DEVELOP SOMETHING
Message received... but can anyone post an answer to my question?
snoshreddax21 said:
Message received... but can anyone post an answer to my question?
Click to expand...
Click to collapse
I don't think it will work due to the kernal and bootloader configuration. I'm no developer, but i'd recommend against trying it until someone with more knowledge says they have a working version or a proper work around. If you do, the chance of bricking your device is over 9,000%! Oh wait, that isn't right....
-- Just wait for a proper. I don't believe it will work. And the AT&T one is still buggy itself. (camera, USB, etc).
snoshreddax21 said:
Message received... but can anyone post an answer to my question?
Click to expand...
Click to collapse
You need to edit the update script to read your device instead of the AT&T one, as long as the mount points on both devices are the same I don't think it could do any harm
Sent from my ADR6425LVW using xda app-developers app
bradsinram said:
You need to edit the update script to read your device instead of the AT&T one, as long as the mount points on both devices are the same I don't think it could do any harm
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
How exactly would I go about doing that?
Google it
Sent from my ADR6425LVW using xda app-developers app
Seriously, do your research. 1) The ATT boot loader IS NOT locked. 2) You can't even post in the correct section no one wants to help us.
Related
Please check /cache and copy all files from it before rebooting to install.
That way, we can get a copy.
For more advanced users, please run a logcat during download process, so that we can try and get a URL to download it manually.
Thanks!
no prob I was just saying in another thread that i am new to the forums and a verizon wireless employee. I was just about to post a thread letting all the devs know that i have access to info a few days (sometimes...you guys are good) before the general public. I also have a thunderbolt that im not afraid to brick trying new things (giunea pig) because i can get it replaced being an employee.
adrynalyne said:
Please check /cache and copy all files from it before rebooting to install.
That way, we can get a copy.
For more advanced users, please run a logcat during download process, so that we can try and get a URL to download it manually.
Thanks!
Click to expand...
Click to collapse
Disclaimer : Hi my name is Daniel and I'm a noob.
I'm assuming that if you're rooted you shouldn't touch any updates until they've been modified by the devs?
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Lightning Rom v3.3.1 / Adrynalyne 4.4.3
raider3bravo said:
I'm assuming that if you're rooted you shouldn't touch any updates until they've been modified by the devs?
Click to expand...
Click to collapse
I'm wondering this aswell
raider3bravo said:
I'm assuming that if you're rooted you shouldn't touch any updates until they've been modified by the devs?
Click to expand...
Click to collapse
Honestly I am noobish myself but from what I understand if you CAN get the update, it may unroot your device but you just have to do the last few steps of the rooting process over to gain root again. If you are using a custom ROM you may have to manually push the update to the phone.
Again this is not absolute but this is what I believe to be true. If I am mistaken please correct me. This is why I think the OP wants to be able to download it from a website...and also to tear it down for any new goodies
Sent from my ADR6400L using XDA Premium App
dcmbullet said:
Honestly I am noobish myself but from what I understand if you CAN get the update, it may unroot your device but you just have to do the last few steps of the rooting process over to gain root again. If you are using a custom ROM you may have to manually push the update to the phone.
Again this is not absolute but this is what I believe to be true. If I am mistaken please correct me. This is why I think the OP wants to be able to download it from a website...and also to tear it down for any new goodies
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I have never been through a htc update but I'm pretty sure it puts s back on which would make you unable to regain root I believe.
Sent from my ThunderBolt using XDA App
miketoasty said:
I have never been through a htc update but I'm pretty sure it puts s back on which would make you unable to regain root I believe.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
There's been some talk that they'll force-push the update. Dunno the veracity of that. I'm thinking about returning to stock beforehand.
What can we do to stop the OTA?
tekhna said:
There's been some talk that they'll force-push the update. Dunno the veracity of that. I'm thinking about returning to stock beforehand.
Click to expand...
Click to collapse
If that's the case, there must be a way to block or prevent this. Would any devs care to add their valuable input?
Would switching to an AOSP make any difference?
The release date is 05/03/2011. That means, we have ample time to get a plan in place. I'm sure I'm not the only one that would hate to re-root their phone.
Is it possible for them to lock the bootloader with this OTA?
raider3bravo said:
If that's the case, there must be a way to block or prevent this. Would any devs care to add their valuable input?
Would switching to an AOSP make any difference?
The release date is 05/03/2011. That means, we have ample time to get a plan in place. I'm sure I'm not the only one that would hate to re-root their phone.
Is it possible for them to lock the bootloader with this OTA?
Click to expand...
Click to collapse
I would say switching to aosp would prevent it as it prevented the updating of the prl.
No. In motorola phones they are locked by hardware. If you were to install a new kernel it trips a component that basically bricks your phone and to disable the trip you would need to crack military grade encryption. We are okay.
Sent from my ThunderBolt using XDA App
If you are running a Rom with the Verizon framework remove, they have no control over your phone. You will be fine.
Sent from my ADR6400L using XDA Premium App
miketoasty said:
I would say switching to aosp would prevent it as it prevented the updating of the prl.
No. In motorola phones they are locked by hardware. If you were to install a new kernel it trips a component that basically bricks your phone and to disable the trip you would need to crack military grade encryption. We are okay.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
I'm not familiar with AOSP's. Is the "Pre-ALPHA Pre-release of CyanogenMod 7" an AOSP?
Are Senseless or Desensed Roms AOSP?
God I hope this update comes today or tomorrow !
tekhna said:
There's been some talk that they'll force-push the update. Dunno the veracity of that. I'm thinking about returning to stock beforehand.
Click to expand...
Click to collapse
I call bullish*t
dirtyfingers said:
I call bullish*t
Click to expand...
Click to collapse
I second that.
droidxscott said:
God I hope this update comes today or tomorrow !
Click to expand...
Click to collapse
I already put in a different thread that verizon has announced that the ota is scheduled for release 5/3. I have noticed in the past that software updates have been released earlier than scheduled release dates (e.g. froyo update for fascinate was available 7pm the night before)
Sent from my ADR6400L using XDA Premium App
raider3bravo said:
I'm not familiar with AOSP's. Is the "Pre-ALPHA Pre-release of CyanogenMod 7" an AOSP?
Are Senseless or Desensed Roms AOSP?
Click to expand...
Click to collapse
According to this thread (http://forum.xda-developers.com/showthread.php?t=1027706) in the development forum, CM7 is listed under "AOSP Based." As for senseless ROM's, I think it depends on the specific ROM in question, as some are and some aren't (but I could be wrong).
Are we waiting for the update that was just recently announced? The same one that's already in bamf? Or am I missing something?
Sent from my ADR6400L using XDA Premium App
dadsterflip said:
Are we waiting for the update that was just recently announced? The same one that's already in bamf? Or am I missing something?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I want the ota update to tinker with, yes.
Sent from my ADR6400L using XDA App
I might have just saw the update. I saw something out of the corner of my eye in the notification bar but when I turned my head nothing. I then rebooted my phone and I saw something else out of the corner of my eye (I have really good peripheral vision). There is a small chance it was the clock changing times (yes my vision is that good). I will let everyone know if the phone feels faster and more updated to know for sure.
Sent from my ADR6400L using XDA App
adrynalyne said:
I want the ota update to tinker with, yes.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
aight ill let ya know if i get something unless someone hands it to you first. Bamf doens't have the block updater installed?
Will I still receive the android updates? Ive always been sketchy about rooting my phone because i want to keep the android system as up to date as possible. Will I still receive the android updates if I root my phone or will I have to manually do it somehow?
Much thanks
If you flash a custom rom then you won't recieve the official OTA updates from Google.
If you root the stock rom you will still receive ota updates. You can also manually flash updates(best method). Please do alot of reading about rooting before attempting anything. Had you done this you would have known the answer to your question. Learn how to use adobe and fastboot. Don't be lazy and use a one click root method as this will not teach you anything about your phone and you will not know how to fix a problem should one arise. Thanks for posting in the correct section!
Sent from my Nexus S 4G using xda premium
any recommendations for a guide to root my nexus?
wsiegfri said:
any recommendations for a guide to root my nexus?
Click to expand...
Click to collapse
If you have a mac, my guide.
thats what i have. could you link me? also my phone is on 2.3.7
Rem3Dy said:
If you root the stock rom you will still receive ota updates. You can also manually flash updates(best method). Please do alot of reading about rooting before attempting anything. Had you done this you would have known the answer to your question. Learn how to use adobe and fastboot. Don't be lazy and use a one click root method as this will not teach you anything about your phone and you will not know how to fix a problem should one arise. Thanks for posting in the correct section!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
What in the world does he need to know anything about adobe for?
Sent from my Nexus S using xda premium
Auto correction on his phone turned abd into adobe I would say. It is clear to me what was meant.
sooo how should i go about rooting it with 2.3.7 and being on a mac?
Found this sticky in the Nexus S General section:
http://forum.xda-developers.com/showthread.php?t=878446
double check if it supports your Nexus s version though.
Guides in Android Development section
do you think it will matter that I'm on mac 10.7?
wsiegfri said:
do you think it will matter that I'm on mac 10.7?
Click to expand...
Click to collapse
You'll be just fine
Also, if your rooted and running a, custom ROM, you don't need OTA updates, as the ROM developers incorporate the updates into their ROMs, within a day or two usually. I don't even worry about updates from OEMS or Google anymore.
Pipsqueak approved this message.
One click is certainly looking like a bad idea as the ota does come through and then screws up your superuser. I've been arguing w my phone for a week trying to get past this and put cm7 on it.
Sent from my Nexus S 4G using XDA App
i get to the part where i have to mount my phone while in recovery mode and my phone won't mount to my computer. Some help with this would be greatly appreciated
I keep on getting this prompt saying I need to update my software, it'll just take a few minutes, etc. I rooted my phone just recently and want to make sure that if I update I won't lose my root privileges.
The reason I'd like to update us I'd like top see if it will fix the problem with the WiFi connection, I've completely lousy the ability top connect to WiFi.
Does anyone have any info in these issues?
Thanks
Sent from my HTC One X using xda app-developers app
Yes, you will lose your root. You can either use ota rootkeeper from the play store or my recommendation would be to just flash a ROM. CleanROM to be specific. It's based off the latest OTA. Flash that and the latest radio and you'll be golden. Best ROM available.
Sent from my HTC One X using xda premium
choocher said:
I keep on getting this prompt saying I need to update my software, it'll just take a few minutes, etc. I rooted my phone just recently and want to make sure that if I update I won't lose my root privileges.
Click to expand...
Click to collapse
If you install and activate OTARootkeeper, it will preserve your root. It's pretty much idiot-proof.
+1 for OTARootKeeper. It worked for me when my phone updated from 1.73 to 1.85.
Sent from my htc_evita using xda app-developers app
iElvis said:
If you install and activate OTARootkeeper, it will preserve your root. It's pretty much idiot-proof.
Click to expand...
Click to collapse
It should be noted that OTA Rootkeeper is verified to work with the 1.85 OTA, but its not a sure thing for every OTA. Its possible that future OTA's may still break root, even with Rootkeeper. When future updates come out, safest to see if OTA Rootkeeper works for others before attempting yourself, unless you feel like being brave (I guess somebody has to be the guinea pig). Or to install the update by some other means, as they are often posted here in pre-rooted form and installable via recovery.
I think I'll do both. The only thing is, everybody talks about flashing a Rom as if I should know what that is, or how to do it. Sadly, I don't have the slightest clue. Does anyone have a link to a step by step instruction on how to do it?
Sent from my HTC One X using xda app-developers app
choocher said:
I think I'll do both. The only thing is, everybody talks about flashing a Rom as if I should know what that is, or how to do it. Sadly, I don't have the slightest clue. Does anyone have a link to a step by step instruction on how to do it?
Click to expand...
Click to collapse
There are such things, but if you're that clueless, you should do some reading and researching about the general subject before doing anything with your phone. Don't do anything that a) you don't fully understands and b) don't know how to undo.
choocher said:
I think I'll do both. The only thing is, everybody talks about flashing a Rom as if I should know what that is, or how to do it. Sadly, I don't have the slightest clue. Does anyone have a link to a step by step instruction on how to do it?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
The reason why everybody talks like you should know what a ROM is is because this is xda-developers. This site is geared directly towards developers and users who root and flash ROMs and mods. It is pretty much understood that if you are on this site, you should at the very least know what a ROM is. There are other, more general Android sites out there that are for the average user but this is not one of those sites.
That said, if you check out the development section, you will see a whole bunch of threads for various ROMs and mods, I suggest checking them out and you will see what benefits they provide and how their experiences differ from the stock one. Flashing a ROM is a lot easier than you would think, and the benefits are endless. Everything you need to know about how to do it can be found here on xda, just look around a bit and you will find all the info you need. Good luck!
Thank you for the help and direction.
Sent from my HTC One X using xda app-developers app
No prob. If after doing some reading you still have questions, don't hesitate to ask. We're here to help
Sent from my HTC One X using xda premium
I have an AT&T HTC One X, with android 4.1.1. I had been scouring the internet for about three weeks now trying to figure out how to Unlock the bootloader. I finally figured it out. Then I did a perm root, applying superuserSU and i tried to flash CyenogenMod 10.0.0, and i got stuck in the CyenogenMod 10 loader. So i went back, and cleared the cache and data and dalvik. Then it loaded, and it started at the home scree. It didn't take me through a set up or anything. Then I tried to touch the screen, and it wasn't responsive. I tried re-applying it and what not, and then it just stopped working, the CWM Recovery kept saying it E: Cant Mount /sdcard, and it would have a long list of things it couldn't mount (which was litterally everything, and now I'm trying to just reset it to the stock HTC so i can try again. Can any one walk me through how to reset it?
And this is what happens when you don't read and start doing **** without knowing what you're doing.
So lazy.
If you do enough research in this forum to tell me why your touchscreen didn't work in cyanogenmod. I'll help you get your phone working again.
Sent from my HTC One X using xda app-developers app
Not to be rude but OP i agree with exad. You didnt do any reading or research. You didnt ask questions first. But I'll get you to a working phone.
Just go to twrp again. Download viperXL. "Mount" in twrp and drag viperxl onto phone and flash that. You'll boot
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Not to be rude but OP i agree with exad. You didnt do any reading or research. You didnt ask questions first. But I'll get you to a working phone.
Just go to twrp again. Download viperXL. "Mount" in twrp and drag viperxl onto phone and flash that. You'll boot
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Pft inflatedtitan is nicer than me
Avoid cwm it has low compatibility for the one xl. twrp 2.3.3.1 or below is recommended. (but that won't fix cm touchscreen issue)
You guys are the everyday superheros
Sent from my HTC One X using xda premium
exad said:
Pft inflatedtitan is nicer than me
Avoid cwm it has low compatibility for the one xl. twrp 2.3.3.1 or below is recommended. (but that won't fix cm touchscreen issue)
Click to expand...
Click to collapse
Then what will? I know, I was overly eager and crap. I get that, but i posted here for help. Not criticism. I'm used to working with Samsung, and Apple. But if you can help, please just say it and don't direct me to another page.
trevon2698 said:
Then what will? I know, I was overly eager and crap. I get that, but i posted here for help. Not criticism. I'm used to working with Samsung, and Apple. But if you can help, please just say it and don't direct me to another page.
Click to expand...
Click to collapse
Touchscreen issues are to do with HTC changing the drivers for newer 4.1.1 ROMs. What you want to do is downgrade the touchpanel firmware using h8rift's excellent guide. That downgraded touchpanel firmware will then work with all ROMs and also with newer TWRPs. I'm running 2.5.0.0 with no dramas here.
juicejuice said:
Touchscreen issues are to do with HTC changing the drivers for newer 4.1.1 ROMs. What you want to do is downgrade the touchpanel firmware using h8rift's excellent guide. That downgraded touchpanel firmware will then work with all ROMs and also with newer TWRPs. I'm running 2.5.0.0 with no dramas here.
Click to expand...
Click to collapse
Thank you! Finally some help.
trevon2698 said:
Thank you! Finally some help.
Click to expand...
Click to collapse
Also the reason you boot looped in the first place was due to htc's infamous "s-on" security feature. While s-on, you are required to fastboot any img file instead of flashing through recovery. Examples are splash screens, kernels, recovery imgs. If you also follow the super easy s-off thread, this will allow your phone to surpass any security checks, allowing you to simply flash anything you want.
So until you s-off, you have to flash the ROM then immediately boot into boot loader and fastboot flash the boot.img. then the rom will boot up just fine
Sent from my HTC One XL using Tapatalk 2
trevon2698 said:
Thank you! Finally some help.
Click to expand...
Click to collapse
No worries. If this stuff doesn't seem easy, it is because it isn't. There are no user manuals, support systems or helpdesks. All of us on here are just a community of like minded people. We encourage new members and especially those who are eager to read, learn and contribute.
Good luck with your phone, you will love what you can do with it!
juicejuice said:
No worries. If this stuff doesn't seem easy, it is because it isn't. There are no user manuals, support systems or helpdesks. All of us on here are just a community of like minded people. We encourage new members and especially those who are eager to read, learn and contribute.
Good luck with your phone, you will love what you can do with it!
Click to expand...
Click to collapse
I dissagree entirely. It is easy. If it seems hard, the only reason would be that one did not have the patience to do a little light reading beforehand. And when you flat out give responses to easy questions it only encourages ignorance. The touchscreen issue is posted in just about all aosp Rom op and in stickies and a search would have brought up at least 10 threads with the issue documented aswell.
Honestly it is easy, but there's a lot to learn and watch out for so it can easily be overwhelming. After you toy around with it and see what command does what, what to flash, how to flash it, it gets a lot easier. Just lurk here often and learn the terminology and you'll be successful. You may get called a dumbass but that's because a lot of users here are really sick of people asking the same questions over and over, or they're just blatent idiots.
PS. Use the latest Nightly of CM 10.1, the new 3.4 kernel is supposed to be really slick.
Also, flash the 2.3.3.0 version of TWRP, versions 2.4 and above seem to have problems.
Sent from my HTC One XL using xda premium
Thanks guys. Like I said before. I'm new to the whole HTC world of modding. Its much different from The GS3 and iPhone 5. I have my phone. Wroking, and I'm running CyanogenMod 10.1 and I have S-Off. Thanks again.
PS. Dude. If you don't want to help, you sound like your so important, so go find some thing better to do if you can't be helpful.
Sent from my One X using xda premium
trevon2698 said:
PS. Dude. If you don't want to help, you sound like your so important, so go find some thing better to do if you can't be helpful.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Who exactly is that in reference to?
Sent from my Evita
timmaaa said:
Who exactly is that in reference to?
Sent from my Evita
Click to expand...
Click to collapse
I think he means me D:
I don't think people like it when I point out their lazyness and that they need to read more.
Searching before posting is encouraged here on xda. There are stickies with forum rules indicating so. It's not that I don't want to help people. I just don't want to answer the same questions over and over because lazy people can't take the time to search or check the faq.
No one here is getting paid to help. So do the entire xda community a favor and help yourself first. Then, if after searching and reading through some stickies you still don't know the answer. then post your question.
Sent from my HTC One X using xda app-developers app
exad said:
I think he means me D:
I don't think people like it when I point out their lazyness and that they need to read more.
Searching before posting is encouraged here on xda. There are stickies with forum rules indicating so. It's not that I don't want to help people. I just don't want to answer the same questions over and over because lazy people can't take the time to search or check the faq.
No one here is getting paid to help. So do the entire xda community a favor and help yourself first. Then, if after searching and reading through some stickies you still don't know the answer. then post your question.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Oh that sad face seems so sincere
Yeah that's what I had suspected. I was going to fire up haha. I agree with you 100% man.
Sent from my Evita
I figured that I might post this to help some people as I see this posted a lot.
Are you one of the ones that tried to install a custom recovery on the MF3 update? Are you facing a never ending boot sequence or device just freezing at boot screen?
Try this to help you get a normal boot so your phone is at least usable. (Note that your factory recovery will no longer work!)
First off, do a battery pull.
After you put the battery back in (make sure it's not plugged up) go into download mode.
Click Cancel instead of continuing into download mode. Chances are your device will boot up normal. I've tried this with a device I own and also tried it on a few others (through PM and chat online).
If this works for you please let me know!
Lol I figured this out in 2 mins of owning the phone.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
You should change the title...EXTREMELY misleading...sounds more like a thread for a workaround to install a custom recovery lol
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
You installed a custom recovery on the MF3?
Sent from my GT-I9505G using XDA Premium HD app
mg2195 said:
You should change the title...EXTREMELY misleading...sounds more like a thread for a workaround to install a custom recovery lol
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Fine I'll change it. I was just trying to help some folks that post the same things every day that you get mad at and bash around.
Sent from my GT-I9505G using XDA Premium HD app
Your doing fine...you just got my hopes up lol. But something a little more specific like workaround for failed recovery flash or fix mf3 bootloop or similar
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Your doing fine...you just got my hopes up lol. But something a little more specific like workaround for failed recovery flash or fix mf3 bootloop or similar
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Sounds good I'll do that now
Very sleepy lol..wasn't thinking clearly when I posted it.
Sent from my GT-I9505G using XDA Premium HD app
agent929 said:
Sounds good I'll do that now
Very sleepy lol..wasn't thinking clearly when I posted it.
Click to expand...
Click to collapse
Yeah it'd be good to have this info in a better titled thread than it was...and an even better titled thread than this one.
Maybe: [How To] Unbrick MF3 after (stupidly ignorantly) attempting to install a custom recovery
Anyways, it was first discovered here, as far as I can tell:
http://forum.xda-developers.com/showthread.php?t=2398336
(post 11)
And there's an alternative method too, if that didn't work:
http://forum.xda-developers.com/showthread.php?t=2404970
Guys I'd appreciate it if you didn't spam up this topic with nonsense.
The phone is not bricked for one.
It was never publicly announced what to do one these forums that I could find.
Edit: I just read your posted topics and neither one says to do this
The questions are asked every day by people.
This post has potential to stop some messages.
Stop posting here just to get your post count up. If you don't have anything relavent to say then find another topic.
For the guys post above me thanks for adding more ways to help try to do a workaround even though you tried to undermine me here.
Sent from my GT-I9505G using XDA Premium HD app
no worry bro--you did good--many new folks don't know that
and, you can't please everyone
agent929 said:
Guys I'd appreciate it if you didn't spam up this topic with nonsense.
The phone is not bricked for one.
It was never publicly announced what to do one these forums that I could find.
Edit: I just read your posted topics and neither one says to do this
The questions are asked every day by people.
This post has potential to stop some messages.
Stop posting here just to get your post count up. If you don't have anything relavent to say then find another topic.
For the guys post above me thanks for adding more ways to help try to do a workaround even though you tried to undermine me here.
Click to expand...
Click to collapse
If you're stuck in download mode and cannot get to your OS, I think that counts as a brick! Yes, btw, post 11 in the first thread I linked shows the solution which I have been telling others to do...which you did us the favor of making a post about as well. I agree that it's good to make this post, though I think your thread title could be more useful if you edited it.
Also, should this method not work for some people, an alternative method is a good thing to have.
Thanks again and have a nice day! :good:
I seem to be helping folks with the issue I have posted here in many other post. Have also had some PM's about it. Any suggestions on making this more searchable?
Sent from miPhone using XDA Premium HD app
agent929 said:
I seem to be helping folks with the issue I have posted here in many other post. Have also had some PM's about it. Any suggestions on making this more searchable?
Sent from miPhone using XDA Premium HD app
Click to expand...
Click to collapse
Don't assume people are searching...
joeybear23 said:
Don't assume people are searching...
Click to expand...
Click to collapse
Search? What's that. Lol
jd1639 said:
Search? What's that. Lol
Click to expand...
Click to collapse
Funny lol. Well, I tried. And failed lol. Was just trying to save some others time that keep getting so stressed about answering some of the same questions over and over.
agent929 said:
Funny lol. Well, I tried. And failed lol. Was just trying to save some others time that keep getting so stressed about answering some of the same questions over and over.
Click to expand...
Click to collapse
I think my suggestion in post #8 is still a good one.
Your current thread title makes it sound like you tried to flash a custom recovery on MF3 and it didn't work. There's no way anyone would read that title and think there's a "How To" guide in it.
Alright maybe that will work.
Sent from miPhone using XDA Premium HD app
Lol I found this thread after I figured it out for myself. I was kind of hoping this would lead me into a way to get back my recovery.
This is how I fixed my brick.
Flashed this file in ODIN. Now my phone boots normally. Got it from another thread with a diff issue here on XDA. I tried it and it worked. Wish I could remember where and what the thread was called. I believe it was this thread. http://forum.xda-developers.com/showthread.php?t=2360859