Hi......so unlocked bootloader and rooted phone according to here - theunlockr.com/2013/03/16/how-to-root-the-motorola-razr-i/[/url]
All great but had been getting problems with the phone not recieving txts.........virgin are sending out a replacment but taking the old one back now obviously this does not bode well for me as it is rooted, especially with that riduculous warning screen motorola have incorparated..........tried using the stock.img flashboot work around to get rid of that at least, but just end up soft bricking the phone and it stays in flash mode(non signed img)...........managed to reflash it and use recover to restore phone settings but im still stuck with that problem........if i could at least just get rid of that stupid warning message on reboots i would be happy to give it back as these phones probably just get sent to a factory to be refurbed and re flashed anyway, but i feel the message just makes it far too glaringly obvious!!(the point of it i suppose)
I've seen the thread on reflashing with stock roms using rsd lite on this site but also seen it has a high chance of hard bricking the phone.
SO!!
My question(s)is........is there actually a way of getting rid of just the logo and does it def work?
Should I try and unroot the phone using the rsd lite method?
Do you think it will matter if I hard brick the phone when I give it back or could this actually be a good thing to do and just plead ignorance if Im asked and just say it suddenly died on me, therefore covering my tracks.
Does it really matter anyway since they are already sending me a new phone out?
And would I be right in assuming that this phone isn't as straightforward for rooting/unrooting as other phones out there are?
My system version is 91.2.26001.XT890.Retail.en.EU
My Kernel version is 3.0.34 [email protected]#1
Android 4.1.2
Thanks for reading if your still with me and not nodded off!!And yes I have already scoured the net and threads for answers and even phoned my mother to find out why I'm special!!
I'm not sure if this will work but you can try downgrade to ics with mattlgroff's homemade fastboots and then try to flash locked logo but this won't probably help you if JB was installed through OTA as its bootloader replaces unlocked logo back
Related
Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.
seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)
How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch
Where are you located? And who is your provider?
Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again
tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
AbsoluteZero said:
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
Click to expand...
Click to collapse
Go here....http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Scroll down and you will see a link to the stock Roger's ROM.
Microwave...15 seconds...you don't want to overcook
I have that, i'm trying to install it, but it's taking a long time to start installing update. I've tried reformatting everything, I've tried renaming the Rogers stock to update.zip.
any thoughts on how long it should take to install, or any better instructions on how to get back to stock?
Still stuck at installing update after 15 minutes.
also, is there go instructions on how to get rid of the AT&T Logo, or will the stock rom/firmware fix that?
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
AbsoluteZero said:
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
Click to expand...
Click to collapse
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Auridran said:
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Click to expand...
Click to collapse
Did you end up being able to boot ok somehow?
AbsoluteZero said:
Did you end up being able to boot ok somehow?
Click to expand...
Click to collapse
Nope. I'd always be stuck at that black lock screen unable to unlock. After one erase and restore there was a background image instead of blackness, but it didn't go any further. I just decided to stick with Assonance, but that's not really an option for you unfortunately.
so I was wrong right from the beginning, I didn't flash Assonance, i flashed Cognitionv2.3b8. Sorry for the confusion
I clipped this from the above link to the rogers stock rom.
"Be aware when installing AT&T Firmware 2.2 and trying to recover to Rogers stock, you will have a short AT&T display on boot up. One way to remove this is to flash the phone with firmware from a Samsung I9000 model and then reflash it with the Rogers Firmware. This will remove the AT&T logo. However, there is a chance that this method may, in certain circumstances, leave a seemingly random pixlation on screen upon boot-up for the time the AT&T logo was meant to be displayed. A very minor issue and doesn't affect the phone or boot process"
So try to find a stock I9000 rom I guess. The assonance rom is based off the I9000(Or at least that what it says on boot :/). I'm not sure if that will be good enough. I'm running Assonance right now on my fiance's rogers captivate. It's been working great since she has gotten it. So maybe even just flashing Assonance will fix things for you.
As a side note, I returned my x10 with a custom rom on it for warranty and I never heard from them. My understanding(hearsay) is that it doesn't even go to rogers. I'm in Ontario, and I believe it goes to a refurbishing company that is contracted by rogers where they check for water damage.
So I'm not sure where you are located but it may be the same.
(Disclaimer: I'm not saying you WONT get billed for the phone if you send it back with custom rom on it.. I'm simply saying that I didn't and I have heard of others not being as well. Perhaps we were just lucky)
Good Luck.
If you try this let me know if it works, should I ever need to send hers in for warranty.
check your pm
a few days ago my fiance was complaining her basically stock Nexus was rebooting into a bootloop - where it displays the loading X and vibrates and then reboots and repeats every few moments (a few days after her doing the system update)- if I remove the battery for a few minutes then put battery back and reboot it will boot into the OS where it will stay sometimes for a few minutes othertimes an hour or more before going into the bootloop- so I told her I would attempt to flash a new rom. after many hours of messing with the phone and attempting to access the recovery it just will not work- the phone just goes into the bootloop - exactly as mentioned above. I have used fastboot to flash new images (userdata, system, boot, recovery etc) numerous times and it still does the same thing- crashes and reboots into the bootloop from the OS randomly and bootloop when trying to access recovery. I am pretty sure it is a hardware issue (the phone is only 3 months old) but the company i bought the phone from is stating it is a software issue and not covered by tehir warranty.
Problem is I unlocked the bootloader while messing with the rom's yesterday and am now concerned they wont honour the warranty anyway- does anyone have any suggestions as to anything else I can try? As far as I can tell as I cannot access recovery I cannot install any other roms..
Please help- otherwise I will be posting a yourtube video of me destroying a basically brand new nexus one- I really am that frustrated....
a bit more info- it was rooted but still had locked bootloader when this started- rooted using onclickroot or something- which after the update it wasn't rooted anymore- I am wondering if this has caused some low level conflict somehow- I have rooted again using superoneclick - and as stated have unlocked the bootloader.
is there any way to flash a rom using fastboot or adb on this thing- I would hazard surely there is but amongst all the information floating around for this phone I cannot find out how- I am thinking maybe I try and load cyanogen 6 or something if I could work out how to flash a rom using adb (because njo matter how many times I try to flash different recovery images it wont boot into recovery- I can access fastboot etc but as soon as i select recovery I get the bootloop...
and before I get flamed I have spent three days searching and reading and attempting everything short of voodoo witch magic. I thought my X10 was a P.I.A. to root and flash etc but really it was simple compared to the trouble this phone has given me..
I am wondeirng if some of the rom's are incompatible with some hardware- and I don't quite understand the whole radio thing either... can someone explain that?
BTW Im not a total noob- I have been around for a while without an account - then have had this account for a while but mostly just read the forums as I have no real input and knowledge to give...
...help!
Can no one help?
I have managed to get into recovery (by putting the phone in the freezer for ten minutes at a time to reduce the temperature and stabilise it enough to run for 15-20 minutes at a time)...
Have flashed different kernels this way and nothing is stable- it still bootloops because of heat....
I contacted HTC Hong Kong (it was purchased from a Hong Kong company) and they have told me there is a $350 fee to repair it as its a UK phone. Now the phone is exactly 55 days old not three months and I am really really frustrated.
Does anyone know if its worth contacting HTC UK?
I have friends in the UK I can have them send it in and recieve it from repair....
Someone please help- even if its just a comment of "just smash the damn thing..."
Thanks guys sorry about the long self centred posts but I am ready to destroy this phone- it doesnt have a mark on it either- any ideas what its worth for spare parts?
I am smart enough apparantly to get myself into trouble with flashing and rooting...I thought i had a pretty good grip on this till this happened.
I know you guys are working hard and my problems are small and silly in the grand scheme of things, if I missed something in my searches I apologize, I looked for hours and found one other post, but that persons issue was slightly different than mine. I own a Htc vivid ( holiday, raider) I was originally running the stock ICS ruu, I reflashed to the Pre-rooted ICS rom, it froze due to my "fiddling" with the font settings. I tried to flash back to the original ICS RUU, when the Prerooted version would not take on my phone. Everything seemed great until it froze at 34%. I have attempted to boot into recovery (volume - and power) and get nothing but the black screen with four triangles in the corners and the HTC logo in the middle, I am using the original USB cord, I have tried rerunning this from a few different computers with it only to get stuck at the 34% mark again and again. I would love to get back to ICS pre rooted again, but at this point I am close to tossing it in the microwave for a few seconds and warrantying the phone out. Advice? Suggestions?
I appreciate any help thrown my way, as I said I know you guys are busy making awesome stuff happen, and my problems are small by comparison.
Thank you ahead of time!
Another member was (could still be) having what sounds identical (RUU stopping at 34%). Not sure if he's gotten it fixed, I do believe TheCubed is helping him with it still, you might hop on IRC (Freenode, #htc-holiday) and talk to TheCubed when he gets on.
If you manage to get back into the hboot try to re lock your bootloader and it'll reset everything if memory serves me right.
Brand New said:
If you manage to get back into the hboot try to re lock your bootloader and it'll reset everything if memory serves me right.
Click to expand...
Click to collapse
other user with same issue - http://forum.xda-developers.com/showthread.php?t=1581902
might want to follow that. I don't have any suggestions at this point other than the last suggestion in that thread. IF you can get to bootloader, try relocking bootloader and running the ph39img that thecubed posted to restore to GB, then try running the RUU.
Did you try to run the RUU while you were unlocked???? You need to be locked to run the RUU
Could it also be a bad RUU download? I would try downloading the RUU again, from another server if possible, and see if it gets stuck at the 34%.
S7
A friend of mine tried to root his white tmobile g1 and im not sure what he did to it. heres what im working with.
press power button goes to g1 screen and then to the factory android recovery (e2)
can wipe, factory reset and can select install update.zip
the phone wont take any update i throw at it and ive tried like 7-8 i have found here on xda. I have no idea what phone was on previously.
I CANNOT access the bootloader no matter what i do. i even went as far as to dissasemble the phone and replace the buttons (thought home might be sticking), anyone have any ideas on how i can possibly ressurect this?
without bootloader access i cant flash to downgrade. Im at a loss here and really hate getting outsmarted by a phone. I dont think its a brick... yet being i can hit stock recovery and that blue led test works.
If bootloader is truly gone, not just hidden from you, the phone can not boot. I know of no flash able update.zip for a bootloader in the stock recovery which unfortunately means this is a brick. The blue light mode is only helpful for JTAG, sorry
Sent from my Nexus 7 using xda premium
I finally managed to get the phone to boot by swapping the cables out of another phone. Weird issue but nice having a half dozen phones laying around for parts
Sent from my HTC One XL