i just update the 2.3.4 by recovery.
after it done, i change the fonts in the system.
I FORGOT TO CHANGE THE RIGHT FOR THE FILES
now, it cannot power on. even cannot enter RSD mode.
the screen just show __svf 105:1:2__
what can i do now.
Do you also see 0x1000 on the screen? Possible you bricked.
If so, you may want to read this --> http://forum.xda-developers.com/showthread.php?t=1165154
I see people with the same error as you also getting the 0x1000.
What were you on, and what had you done, i.e. unlocked bootloader, before flashing?
Which 2.3.4 did you flash?
yes, i saw that numbers.
after i OTA to 2.3.4, i flashed into 1.6.8. i didnt do unlock for it.
so, as you know, the phone become a brick.
before that, i dont know it cannot downgrades
0u0u05 said:
yes, i saw that numbers.
after i OTA to 2.3.4, i flashed into 1.6.8. i didnt do unlock for it.
so, as you know, the phone become a brick.
before that, i dont know it cannot downgrades
Click to expand...
Click to collapse
If there was no warning about downgrading after the OTA prior to you installing the upgrade, you could go to a store and argue with them that since there was no warning, you did not know you couldn't flash back.
lol.
even i argue with them, maybe my phone still sleep.
i dont want to arguing, just let it back.
thank you so much for providing many informations. im trying to unbrick it.
thanks a lot
CaelanT said:
If there was no warning about downgrading after the OTA prior to you installing the upgrade, you could go to a store and argue with them that since there was no warning, you did not know you couldn't flash back.
Click to expand...
Click to collapse
there does not need to be a warning as the sfb's are not supposed to be public at all. So in flashing them you are already going against theme. Not to mention anyone at a store will most likely have no idea what your talking about lol. Its worth a shot tho.
cool.
im look that thread, but got some problems.
do you know how to use nvflash.zip
i mean, after i download that, how to keep going the steps.
Related
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
Hi there,
I'll try to make this brief. My touch screen has a 1/2" slice that is unresponsive (middle of the default google bar and down) and I am under warranty so I figured hey, let's call and get the phone warrantied.
Motorola is sending me a new phone when should be at my apartment when I arrive back from my travels.
My bootloader is unlocked. I understand there is no physical or theoretical way to relock thee bootloader; I get that. I am on 4.5.91. I never did the OTA updates; every update or ROM or anything since 1.26 has been from here. I've read a LOT in the last 24 hours.. and I'm concerned that trying to SBF anything over 4.5.91 will end up bricking the phone that I'm slated to return for a faulty screen. So, I was then thinking about moto-fastboot. That works for system and boot, but not bootloader, right?
My main concern is this: I don't want them to turn my phone on and see "UNLOCKED" in the top left and immediately charge me $499 for voiding the warranty. I DO understand this is a risk I took, and I am willing to eat the charge should it happen; but that withstanding my screen is legitimately borked. I'd be willing to try something to overwrite this bootloader if there were a tangible means to do it without like >80% chance of bricking it. Every SBF I've flashed on here has been pudding.
Is there anything that can be done to get rid of "UNLOCKED" up there? I know it won't relock the bootloader; but I want the techs to see that the screen is broke before they start snooping through system settings. I may get lucky, I don't know.
Also, anyone with experience warrantying a phone with an unlocked bootloader? How did it work out for you?
As it stands now I'm downloading the stock 1.8.3 system and boot images. But they won't overwrite the bootloader. I have about 4 days to figure this out before I fly home.
Thoughts?
I'm pretty sure you're stuck man.
Sent from my MB860 using Tapatalk
Hey I would play it safe and just buy another ATRIX off craigslist. I picked up an ATRIX in my area for 200 that is in mint condition. That sure beats the 499 they are going to charge you when they power on the device to check for user related problems before they slap a new screen on it and put it their refurbish phones inventory.
Sent from my MB860 using XDA App
I'd need somebody else to confirm this:
I thought that when you installed 4.5.91 through the safe .zip files, you were able to flash back to a previous SBF safely. I remember people in the IRC doing just that, and reporting that once they had done so, the "UNLOCKED" message on startup disappeared until they reflashed pudding. I'm pretty sure that it didn't actually relock the bootloader, just somehow get rid of the "UNLOCKED", but again I'm not entirely sure.
tl;dr I think you are safe to flash an SBF if you got GB from a .zip and that way you won't show "UNLOCKED".
I thought about that but I'd rather just get one from them if I'll be spending any money period.
I read a few posts that stated that there was a way to remove the "UNLOCKED" on the bootloader by flashing stock SBF's but I'm not sure if that would result in a brick at this point.. which is why I haven't tried it.
Either way.. I was also thinking: when they were troubleshooting me on the phone, they had me do a factory reset. This was yesterday. So, if it does brick I may have a "I did a system update and something went wrong" way out.
Would love to hear from someone who has experience with warranty services.
Thanks to both of you for your replies. I am also slightly inclined to believe I am boned. :[
KF as soon as someone verifies that I'll be happy to. I still have the 1.2.6 and 1.5.7 stock SBF's. To the best of my knowledge, I never let the OTA update happen. On my XOOM yes but not on the Atrix. Just unlocked, flashed what ever rom/zip I wanted, and went to town. Sucks that my screen blew I just had it where I wanted it with 2.3.4 :[
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
lauterm said:
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
Click to expand...
Click to collapse
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
deziguy420 said:
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
Click to expand...
Click to collapse
I love you both. It worked and I'm on the stock stuff now.
Everything else is up to the fate of the universe. At least they'll see that my screen is messed up before they start prodding around.
What happened?
Can you let us know if this was successful? I'd really like to do the same thing if it was...
Ok so i don't know what happen but my phone now says Failed to Boot 4 Starting RSD Mode
What i want to know if i use the SBF for 1.2.6 will it brick my phone ? I see people saying just use that one and then upgrade after that, but i do not want to take the chance of bricking my phone.
So i hope somebody can help
Im assuming youve already unlocked bootloader. Dont use sbf to flash anything. Use recovery or fastboot.
I voided my warranty.
pukemon said:
Im assuming youve already unlocked bootloader. Dont use sbf to flash anything. Use recovery or fastboot.
I voided my warranty.
Click to expand...
Click to collapse
Well the problem is i did try fastboot and when i did that it still did not work and it also REMOVED fastboot..... so now i dont have that as a option
I found this http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I
and it says im safe to do that one beings it was the same as what i had on my phone before this happended, but im just not sure
If you cant boot into fastboot it may be hardbricked. If rsd doesnt recognize your phone, youre screwed. If it does, cross your fingers and hope for the best.
I voided my warranty.
pukemon said:
If you cant boot into fastboot it may be hardbricked. If rsd doesnt recognize your phone, youre screwed. If it does, cross your fingers and hope for the best.
I voided my warranty.
Click to expand...
Click to collapse
RSD does recognize it and i heard as long as its the latest OS im doing i should be fine but im not sure if the link i posted is the most latest.
Well, read, reread and try to find a couple of threads or better yet experienced members that can help. I try to avoid situations that can possibly get you in a predicament like this.
I voided my warranty.
It all depends if you have "burned the fuse" or not. I can not tell you how to check that with 100% certainty, but if you have EVER flashed/downloaded/used any official update from att or motorola for version 2.3.4 then you have burned the fuse most likely. If that is the case then NEVER flash any older version or you will kill your phone. If you are sure you have never used any official version and only used versions from people that know what they are doing (e.g. Kenn's or fruit cake just to name two) then you can flash whatever you want....but if you are not 100% sure the outcome is on your head.
The safe road would be is if you can get into fastboot?? If so then load cwm recovery with fastboot then load the 2.3.4 fruit cake.
Tao_Man said:
It all depends if you have "burned the fuse" or not. I can not tell you how to check that with 100% certainty, but if you have ever flashed/downloaded/used any official update from att or motorola for version 2.3.4 then you have burned the fuse most likely. If that is the case then NEVER flash any older version or you will kill your phone. If you are sure you have never used any official version and only used versions from people that know what they are doing (e.g. Kenn's or fruit cake just to name two) then you can flash whatever you want....but if you are not 100% sure the outcome is on your head.
The safe road would be is if you can get into fastboot?? If so then load cwm recovery with fastboot then load the 2.3.4 fruit cake.
Click to expand...
Click to collapse
I did use the OTA! ugh
But if i use this SBF http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I should i not be ok beings its the latest OS for the atrix which is the one i had.
And i tried fastboot and after doing that i do not have fastboot anymore :-/
Sigh i just dont know what to do
I used the OTA but even if i use
RivKristopher said:
I did use the OTA! ugh
But if i use this SBF http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I should i not be ok beings its the latest OS for the atrix which is the one i had.
And i tried fastboot and after doing that i do not have fastboot anymore :-/
Sigh i just dont know what to do
I used the OTA but even if i use
Click to expand...
Click to collapse
If you did an OTA *official* update, never use an .SBF except to flash a radio ever again. If you do you RISK hard bricking, period. Sorry man, I know it sucks. I can tell you that I have done an OTA to 2.3.4 and then flashed the 2.3.4 SBF and was fine, but then again, it may not work like that for everyone. I now use fruitcakes even if it's to get back to stock 2.3.4, it's just safer. fruitcakes can be found here http://forum.xda-developers.com/showthread.php?t=1163009
Phalanx7621 said:
If you did an OTA *official* update, never use an .SBF except to flash a radio ever again. If you do you RISK hard bricking, period. Sorry man, I know it sucks. I can tell you that I have done an OTA to 2.3.4 and then flashed the 2.3.4 SBF and was fine, but then again, it may not work like that for everyone. I now use fruitcakes even if it's to get back to stock 2.3.4, it's just safer. fruitcakes can be found here http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
How are fruitcakes loaded through RSD Lite as well ?
Fruitcakes are not .sbf files because they do not need to be. They don't contain the amount of data a .SBF would, usually just system and necessary files. They are flashed with CWM *clockwork recovery mod*, as a .zip file. This makes it a ton easier and the chances of hard bricking your phone are almost zilch. CWM for unlocked bootloaders can be found here http://forum.xda-developers.com/showthread.php?t=1204500
fruitcake is cwm, so if you can not get cwm/recovery to work your only option it seems is to flash the offical 2.3.4 sbf and ONLY the 2.3.4 one, do not use an older version.
once you flash 2.3.4 then you should then be able to get your phone opened up again and get cwm working again, and be ok going forward, but never go back older then 2.3.4.
There are hacked sbf files for safe versions of 1.8.3 but I see no reason to go back to 1.8.3 if you are not going to follow the normal upgrade path anyway.
RivKristopher said:
RSD does recognize it and i heard as long as its the latest OS im doing i should be fine but im not sure if the link i posted is the most latest.
Click to expand...
Click to collapse
I have done this before. I believe your right but obviously there is still a risk. I flashed 4.5.91 over 4.5.91 without bricking. Be sure u flash the same OS to lower potential brick.
Sent from my MB860 using XDA App
Sass86 said:
I have done this before. I believe your right but obviously there is still a risk. I flashed 4.5.91 over 4.5.91 without bricking. Be sure u flash the same OS to lower potential brick.
Click to expand...
Click to collapse
^ this. Always the possibility. Kinda the risk we all take when joining and being a part of this community. I actually got mine soft bricked at one point, and thank God I was able to recover. Good luck in all you do, keep the gravy train rollin'
I bricked one Atrix already a few weeks ago, and have since gotten another...(don't wanna think about it)..
I had toyed with unlocking it, and 'rooted' using the gingerbreak method. I was then, bored, one day and installed CWM paid version(Since I had it on my Nexus One, and it popped up under 'my apps'). Out of curiosity I installed the bootloader via CWM, thinking it would fail before it broke anything..wrong.. It froze after a reboot, but after taking the battery out and back in came back up. Didn't think any more about it, and figured i'd finish the unlocking/flashing part some other time..
Meanwhile the annoying pending system update kept going off, and I inadvertently clicked download... it downloaded, so I figured might as well install and not worry about roms since with root I was able to use the google adhoc wifi apk, which is what I care about most. The install was stuck in an infinite loop. It would 'fail to load RSD', if you took the battery out it boot to android then reboot automatically for system update over and over. I tried using the RSD lite program at this point to flash back to stock rom, and ended up hard bricked...
So, forgive me for being a complete noob as I never had an issue with my nexus one. I am at 4.1.83, android 2.2.2. and baseband 1.7.15.. Which of the many tutorials and post should I follow? How safe are they? Did I brick because I had a partial 2.3.x install, and flashed back to a pre 2.3 base? I've read many post, but definitely a bit gun shy of bricking another Atrix. The phone keeps bugging me to update, and I keep hitting 'cancel'.
I'd like to unlock the boot loader for custom roms.
I'm also a heavy linux user, majority of tutorials seem to only imply windows with RSD lite? can this not be done with adb, and fastboot via linux?
http://forum.xda-developers.com/showthread.php?t=1154600
I would personally go HERE Read through the entire post, then read it again. And go with the ATT 2.3.4 pudding+root
That of course is after reading and re-reading THIS post! (also linked in the post above mine.
Just my opinion.. and make sure you read and nkow what to expect!
xploited said:
http://forum.xda-developers.com/showthread.php?t=1154600
Click to expand...
Click to collapse
That references 4.5.91 and unless I missed it, doesn't explicitly state it's backwards compatible with 4.1.83 and 2.2.2. is it?
Should I update first, to be at those levels and just know not to flash to an earlier build(pre 2.3.4/4.5.91)?
jmorgan6 said:
That references 4.5.91 and unless I missed it, doesn't explicitly state it's backwards compatible with 4.1.83 and 2.2.2. is it?
Should I update first, to be at those levels and just know not to flash to an earlier build(pre 2.3.4/4.5.91)?
Click to expand...
Click to collapse
Nope, don't update. It's safer to unlock BL while you are still at 4.1.83, you just need to download the correct unlock file from the pudding thread.
Otherwise the unlocking steps are exactly the same.
The easiest steps to unlocking are here:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
From there you can flash CWM in one minute.
From there you can flash any rom via CWM in two minutes.
Good luck and don't do anything stupid.
I don't want my phone rooted at all. I just want regular sprint updates. I try updating my phone and all I get is clockwork recovery mod and it not letting me install it. Please help me just get back to stock everything. Remember, I am not good at all with this kinda stuff.
XxDeadlyNinjaxX said:
I don't want my phone rooted at all. I just want regular sprint updates. I try updating my phone and all I get is clockwork recovery mod and it not letting me install it. Please help me just get back to stock everything. Remember, I am not good at all with this kinda stuff.
Click to expand...
Click to collapse
i dont understand?? is your phone rooted now?? if its rooted with a custom recovery.. then u need to run a ruu to get back to stock
I don't think it is as there is nothing like super user on my phone. But when I click HTC software update, it downloads the update, I try to install it then it goes to clockwork mod recovery. I don't get it
XxDeadlyNinjaxX said:
I don't think it is as there is nothing like super user on my phone. But when I click HTC software update, it downloads the update, I try to install it then it goes to clockwork mod recovery. I don't get it
Click to expand...
Click to collapse
you need to flash everything back to stock or try an ruu
I would ruu back to stock or just flash a stock recovery if everything is stock but that... Though if you update you won't be able to s-off ever!!!
Bringing Love to HTC since the OG!!
XxDeadlyNinjaxX said:
I don't want my phone rooted at all. I just want regular sprint updates. I try updating my phone and all I get is clockwork recovery mod and it not letting me install it. Please help me just get back to stock everything. Remember, I am not good at all with this kinda stuff.
Click to expand...
Click to collapse
Stop you're being dumb.
If you're S-OFF, NEVER EVER EVER EVER EVER EVER TAKE SPRINT UPDATES!
All of this is confusing me..
Honestly, all of this is foreign to me. I just want my updates. I went to super user and clicked unroot and it didn't take clockwork recovery mod off. I don't even know what that clockwork mod thing is.. I just want sense 4.1 and android 4.0.4. Can someone please help me..
XxDeadlyNinjaxX said:
Honestly, all of this is foreign to me. I just want my updates. I went to super user and clicked unroot and it didn't take clockwork recovery mod off. I don't even know what that clockwork mod thing is.. I just want sense 4.1 and android 4.0.4. Can someone please help me..
Click to expand...
Click to collapse
Download this
http://shipped-roms.com/download.ph...09_NV_SPCS-2.45_003_release_277028_signed.exe
if you are currently S-OFF you are making a very stupid choice.
Please note that till will make you COMPLETELY STOCK AND YOU WILL PROBABLY LOSE S-OFF AND ALL KINDS OF OTHER AWESOMENESS. ok??? If i was you i would flash stock with goodies or Viper4G. screw sprint updates
It's their choice and not our place to judge.
om4 said:
It's their choice and not our place to judge.
Click to expand...
Click to collapse
If not us then who.. who sir will protect users from their own ignorance..
So that makes it right for you to try and force your beliefs over another? These forums are about choice, filled with the information and tools to let regular users the ability to do what they want with their devices. This user has chosen to go back to stock. If they decide that they want to go back to a custom rom in the future they still have the choice to unlock and flash. It is their phone not yours. If you choose to help someone with an issue like this in the future, please do so objectively
om4 said:
So that make it right for you to try and force your beliefs over another? These forums are about choice, filled with the information and tools to let regular users the ability to do what they want with their devices. This user has chosen to go back to stock. If they decide that they want to go back to a custom rom in the future they still have the choice to unlock and flash. It is their phone not yours
Click to expand...
Click to collapse
I don't see anywhere in my post telling him he cannot go back to stock with the RUU. Im just telling him he might regret it later. I even gave him a link straight to the RUU so he doesn't have to look for it. never did i say NO you cannot go stock. He honestly might think that the only way to get the latest and greatest is being pure stock. I didn't do a good enough job, but there are stock roms with enhancements like Stock w/ Goodies that gives him all of Sprints latest and greatest, but more! He might really not be aware of that. How ever I am! should I not make him aware of that? Should I not tell him there are hundreds of guys who are not S-OFF. and want S-OFF for a reason?
I gave him the info he needs, and will give him more if he needs it, but I would feel like a douche if I didnt make him aware of the other alternatives which are much better and fix the issues present in Sprint's Stock Rom
And that's fine but to call their decision stupid is outright disrespectful. I gather it isn't your intention to do so, but there are ways to inform a user without insult
If you want to go back to stock, click on the link a few posts up, it isn't that hard to do. But while the RUU is running DO NOT TOUCH YOUR PHONE until it runs its cycle, the link will tell you how to do it.
The RUU update failed. It told me my phone is tampered and unlocked. I don't care if I really have to keep it rooted, I just wanna know how to get the updates. If I knew how to get 4.0.4 with Sense 4.1 without unrootinv and using CWM, I would.
If you really want to be persistent, flash the stock and kernel for your base, flash stock recovery and relock bootloader so you can take an OTA
om4 said:
If you really want to be persistent, flash the stock and kernel for your base, flash stock recovery and relock bootloader so you can take an OTA
Click to expand...
Click to collapse
I don't know what any of that means :/ I have never rooted or unrooted a phone before.
you need to have adb and fastboot. Download it from my Dropbox here
https://www.dropbox.com/s/uw2nj95w2hktnvt/ADB.zip
unzip it to a folder and remember where its at. i suggest you put it on your C:\
now click run the CMD prompt. hold the WINDOWS key and push R at the same time. now type in
adb reboot bootloader.
once your phone is on the while screen with a bunch of text on it. type
fastboot oem lock
you are now locked. reboot your phone and run the RUU
Just saying, we should probably get his phone S-OFF. Afterwards he can stay completely stock and keep S-OFF until it starts mattering to him, as long as he doesn't pull a derp and fastboot oem writesecureflag 3.
XxDeadlyNinjaxX said:
I don't know what any of that means :/ I have never rooted or unrooted a phone before.
Click to expand...
Click to collapse
Turn your phone off..hold power and volume down until a white screen pops up. This is bootloader. Look at the top left and let us know if its s on or s off. This information is crucial so we know your flashing methods either through fastboot, bootloader, or recovery. Give
Sent from my EVO using xda premium