Hi,
I got my razr i about two weeks ago. Today, when i rebooted my phone i noticed that it takes a lot of time, eventually it got to Fastboot with lots of I/O errors.
Before i send it back for warranty, is there a change to recover with flashing the stock firmware?
I never unlocked the bootloader, so is flashing even possible? I'm very good with Linux, but this is my first Android phone, so i don't know how things work yet.
akeszeg said:
Hi,
I got my razr i about two weeks ago. Today, when i rebooted my phone i noticed that it takes a lot of time, eventually it got to Fastboot with lots of I/O errors.
Before i send it back for warranty, is there a change to recover with flashing the stock firmware?
I never unlocked the bootloader, so is flashing even possible? I'm very good with Linux, but this is my first Android phone, so i don't know how things work yet.
Click to expand...
Click to collapse
I have never seen an error like that before. I would send it to the warranty without taking risks like unlocking the bootloader.
Related
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?
The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?
Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.
Emergency c-section... nope, I will try that now!
Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.
It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..
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
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
linasj said:
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
Click to expand...
Click to collapse
Remember Next time Unlock Bootloader before Installing CWM.
First off, I apoligize if this has been mentioned before. I did do a search and looked at a few pages to find that this hasn't really been brought up much. Or at least not often or recently.
I have a M8 now, but I gave my old M7 to my dad whos been attempting to use it (and enjoyed it while it worked fine.) But now the phone will reboot itself almost every 10 minutes no matter what I do.
I have
- Unlocked the Bootloader
- Relocked Bootloader and ran an RUU
- Unlocked Bootloader and Installed Custom Rom (AHRD)
all of which have not fixed the constant reboot problem. I was wondering, could the issue involve the firmware of the phone? Or is it a hardware defect.
When I gave my dad the phone he had to take it to best buy to replace, assuming they gave him a refurb I am curious whether or not that could be an issue of a loose part as well.
I have not tried to install a nonsense ROM.
.Ryker said:
First off, I apoligize if this has been mentioned before. I did do a search and looked at a few pages to find that this hasn't really been brought up much. Or at least not often or recently.
I have a M8 now, but I gave my old M7 to my dad whos been attempting to use it (and enjoyed it while it worked fine.) But now the phone will reboot itself almost every 10 minutes no matter what I do.
I have
- Unlocked the Bootloader
- Relocked Bootloader and ran an RUU
- Unlocked Bootloader and Installed Custom Rom (AHRD)
all of which have not fixed the constant reboot problem. I was wondering, could the issue involve the firmware of the phone? Or is it a hardware defect.
When I gave my dad the phone he had to take it to best buy to replace, assuming they gave him a refurb I am curious whether or not that could be an issue of a loose part as well.
I have not tried to install a nonsense ROM.
Click to expand...
Click to collapse
it's a hardware problem return it to Best Buy again
clsA said:
it's a hardware problem return it to Best Buy again
Click to expand...
Click to collapse
Thank you, will do.