Greetings. I found myself in a situation of being stuck at Alcatel splash screen after rebooting following a flash. Phone wouldn't respond to adb/fastboot commands, or upgrade tool. I kept powering off, and rebooting holding combo of power, vol up, down, and both. Finally after several tries, it booted into TWRP! I wish I could say it was a particular combo, but it was just repetition of power off, and combo of power/ vol buttons. Was able to do this twice with this "method". I have 60450 (Cricket). This Phone doesn't respond how I am used to getting into download (power+vol down), or recovery (power+vol up) Hope this helps if you find yourself in a similar situation.
I've developed an issue as well. I can get into twrp just fine and all is fine there but any combination of ROM or kernel even stock makes my phone reboot every 2-5 minutes. Last night after messing around with a few cm builds and then going back to stock after I couldn't get the phone to cool down..... Stock no longer wanted to cool down either. It's been running way to hot so I turned it off for the night. Turn it back on today and same issues. It even restarts on the powered off battery charging screen , I took it a step further and deleted system, data, cache, and internal storage as well as removing my external sd so no ROM or files was on it at all and it still wanted to reboot at the charging screen! Only place it doesn't is in TWRP. I'm not sure if it's a battery safety issue because it's noticing how hot the device is but I was proven wrong with that too, put it in the freezer for 3 mins and it rebooted then too lol. I'm not sure what to do as even download mode reboots. Wtf. Idk if maybe there's some stock files I could attempt to flash through adb? Can anyone help?
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
jani0417 said:
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
Click to expand...
Click to collapse
Just did. Damn i thought for sure it was the answer, but nope, the phone has rebooted 3 times since i just restored the backup from that thread 20 mins ago. It feeezes for a sscond and then will reboot. Whats even worse is it soemtimes doesent let me charge the phone when powered down. Instead of showing the charging battery screen it just boots up into Android. Its highly annoying. I can get into download mode, it just won't stay there.
that suxx. did you unlocked the bootloader? maybe you should relock it.... it's just an idea, really don't have any more idea
jani0417 said:
that suxx. did you unlocked the bootloader? maybe you should relock it.... iitt's just out oan idea, really don't have any more idea
Click to expand...
Click to collapse
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
carnivalrejectq said:
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
Click to expand...
Click to collapse
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
aleksandar.d123 said:
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
Click to expand...
Click to collapse
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
carnivalrejectq said:
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
Click to expand...
Click to collapse
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
DallasCZ said:
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
Click to expand...
Click to collapse
I found him a flashable stock that he got to work. Part of, if not all, of his problem is I think he only has access to a sub-par pc or tablet or something. Anyway, I remember when I didn't know how important it is to have patience and not freak out, and quite a few people had the patience for me , and guided me. I learned. Perhaps this is where he is at. I post things that I have run into, and figured out to try and repay the kindness shown to me. He was trying on his own to figure it out, and that is WAY better than people who don't even try to search, and expect others to do everything for them. This is a community, and just like life, people are at different places. As long as someone is trying, I will try to help if I can. You can't send a rooted phone running CM for warranty.
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
carnivalrejectq said:
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
Click to expand...
Click to collapse
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
dongarritas said:
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
Click to expand...
Click to collapse
All is back to normal, no reboots. I do have an SD card and did have a backup the thing is though I accidentally saved another back up over the original with custom kernel so it was useless lol. And oddly the reboots sort of stopped happening right before but I was using the custom kernel from Flyme which is the only one that seemed to be working. I'm hoping that the issue is with root and not a hardware one from the phone getting to hot flashing things.
Related
Hello Everyone,
I have a rogers captivate. I was trying to update to 2.3 android using Odin . I followed the whole process as stated. After rebooting, I got AT&T logo??? and the phone will not boot, go into recovery mode, or connect to my computer. Have I messed up my phone. Please advice.
how did you get an AT&T logo if it doesnt boot?
also what part of the process were you at? gingerbread shouldnt give the white ATT screen
it should give the "i9000" screen with gingerbread.
or were you flashing stock ATT first?
there is nothing wrong with having the wrong boot screen AND A FIX WAS RELEASED LAST NIGHT FOR GB
the fix for stock ATT has been out for a while. AND MY STOCK ROM FIXES IT TOO!
did you read the part about the button combos changing with gingerbread? or if you are on the ATT stock, use old button combos. Also you should have found my stock rom link before flashing, info there too!, its in my sig,
you have to give us more information to help you.
I beleive I was installing it to stock ATT first. That is when this happened. I was on Odin one click install. I remember the phone saying "do not disconnect the target". then all the installation was done from odin. This phone had 2.2 from samsung.Right now all that happens is that the phone starts and a flashing att logo on white background stays..
please let me know what other info is needed. i will post it all to the best possible
boot into download mode and flash ATT stock again. something messed up
are you using the "one click odin" or the other odin?
and what gingerbread are you trying after?
how do i do that. i have tried vol up+down+power combo. still the same flashing logo with no menus. i was using one click odin. and i was still on installing stock android. never got the chance to go to 2.3
If you can't get into download mode through the 3 button way you might need the jig. You got lucky since you're still able to boot up some have perma brick so try the jig and flash back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App
HOLD VOL UP + DOWN
the plug in USB to PC.
keep buttons held until screen comes on!
i asked which gingerbread you were going to do AFTER
What is the build number on your phone, 4 numbers printed under the battery, mine is a 1010 for example, which mean oct. Of 2010 is when it was built. Some phones 1010 and after will not accept the one click odin rom and cause a bootloop like you are having, Try an odin package from TRusselo's sig instead.
my packages dont have the bootloaders. that might be whats screwed up with blinking att boot.
need download first before anything. i do have a GB bootloader package separately
something else:
try removing battery,
plug in USB to PC and Phone
Hold both Volume buttons
put battery back in.
should get you download mode
I really have noidea about what gingerbread i was after, i guess i wanted just the stock android without any custom software from samsung. I am total noob here as far as androids go.
the number on the battery say 2010.12.20 and the last forr nos under the battery at s/n are 11.02.
what is a jig. how do i use it. My phone cannot connect to the computer.
When I try to reset my device by any method, whether usb or power combos, it goes into either a. ATT logo flashing every few secs. or b. battery charging logo with nothing happeining.
Also my phone cannot be seen on my computer
gingerbread isnt for noobs
NOT THE DATE ON the battery
UNDER the battery ON THE PHONE
4 digit number
if you dont know what a jig or gingerbread or any of this stuff is,
you shouldnt have touched your friggin phone!
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
GO GOOGLE A CAPTIVATE JIG AND BUY ONE
you wont be able to make one if you cant follow instructions.
that is your only hope. if not your phone is F'ed up perminantly.
your ONLY HOPE AFTER, is if your phone *somehow stops* turning on *forever*
and you send it back for warranty, and play dumb! ..... ..... ... .. .
PROGRAMMING a phone cant be learned it 5 minutes.
HELL you cant even read the friggin instructions (written for experienced users) in 5 minutes
this was an expensive lesson on researching and learning before doing
hitechchef said:
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
Click to expand...
Click to collapse
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Thanks I will try this method
BWolf56 said:
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Click to expand...
Click to collapse
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Oh right.. Wow..
Yep, go read about a JIG (it's pretty simple to use). You can either build it or buy one from mobiletechvideo or ebay.
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Lol That kind of subtly is lost here... noone is picking up on your suggestion...
and thats how its going to stay,
ive said it before with almost the same words.
ive laid out all the tools....
correction of the original problem is necessary,
research is salvation,
resistance is futile.
there it is... i laughed... all is good again...
Hey guys I didn't find any useful posts for this device with the same problem.So I started a new thread. Well I was googling and texting and all of a sudden my phone reboots. I thought well it's nothing and put my phone down, 15 minutes later I was hoping for it to be on and ready to be used and all I saw was Dual Core Technology. I rebooted it countless times to see if it'll come alive and no luck. I did root the phone awhile back and never had any problems with it until now.
I did try to go to recovery and all it shows is the android with an exclamation mark. I can get into fast boot and everything but I am a noob with fast boot so I don't exactly know how to wipe the phone by using that.
So I am counting on you guys to help me out. I don't even know if my phone is charging atm I just have it plugged into my power port and all it shows is Dual Core Technology and the battery is dead for letting it sit on that screen for about 30 minutes. I hope you guys can help.
Thanks,
Mike
Have you tried to fxz back to stock using RSD Lite? If not make sure your battery is charged before doing so. That should do the trick. If you have a back up try the recovery. When the Android with the exclamation comes up hit both the up and down volume keys at the same time.
Sent from my MB865 using xda app-developers app
MaTrixJ said:
Hey guys I didn't find any useful posts for this device with the same problem.So I started a new thread. Well I was googling and texting and all of a sudden my phone reboots. I thought well it's nothing and put my phone down, 15 minutes later I was hoping for it to be on and ready to be used and all I saw was Dual Core Technology. I rebooted it countless times to see if it'll come alive and no luck. I did root the phone awhile back and never had any problems with it until now.
I did try to go to recovery and all it shows is the android with an exclamation mark. I can get into fast boot and everything but I am a noob with fast boot so I don't exactly know how to wipe the phone by using that.
So I am counting on you guys to help me out. I don't even know if my phone is charging atm I just have it plugged into my power port and all it shows is Dual Core Technology and the battery is dead for letting it sit on that screen for about 30 minutes. I hope you guys can help.
Thanks,
Mike
Click to expand...
Click to collapse
Couple things we need to know mate. What firmware are you running? 2.3.5? 2.3.6? Or ICS?
These all play into how you are going fix your phone. And frankly your stock recovery is not going to do you any good with this issue. You WILL have to FXZ back, UNLESS you have a backup made in a different recovery system, IE: bootstrap, or bootmenu. Once again all dependent on what firmware you are on. If you can answer those questions, we can help you with the right procedure.
A good thread to start with is this one: Noobs guide to Android and the Atrix 2
It will give you all the info you need on the FXZ and fastboot.
More info and we can fix ya! :highfive:
EDIT: just saw your battery issue. Pull your battery until you are ready to flash in Fasboot. You need to conserve. How much battery do you think you have? Or is it dead? Flashing in FB and having your phone die due to low battery is a SURE way to hard brick your A2.
Fall of Enosis said:
Couple things we need to know mate. What firmware are you running? 2.3.5? 2.3.6? Or ICS?
I am running 2.3.6 stock
These all play into how you are going fix your phone. And frankly your stock recovery is not going to do you any good with this issue. You WILL have to FXZ back, UNLESS you have a backup made in a different recovery system, IE: bootstrap, or bootmenu. Once again all dependent on what firmware you are on. If you can answer those questions, we can help you with the right procedure.
A good thread to start with is this one: Noobs guide to Android and the Atrix 2
It will give you all the info you need on the FXZ and fastboot.
More info and we can fix ya! :highfive:
EDIT: just saw your battery issue. Pull your battery until you are ready to flash in Fasboot. You need to conserve. How much battery do you think you have? Or is it dead? Flashing in FB and having your phone die due to low battery is a SURE way to hard brick your A2
I have a way to charge the battery up without the phone so that's fine ill let it charge tonight and do it in the morning..
Click to expand...
Click to collapse
Axis_Drummer said:
Have you tried to fxz back to stock using RSD Lite? If not make sure your battery is charged before doing so. That should do the trick. If you have a back up try the recovery. When the Android with the exclamation comes up hit both the up and down volume keys at the same time.
I'll definatly try holding both volume keys at the same time next time, thanks!
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Oh and do you guys know what exactly caused this to happen?
Mike
It could've been caused by a number of things. The A2 is an unpredictable phone. Somethings that happen to one person may not happen to others. From my experience.
Did you make any changes to any system files or anything of the such? I see you was rooted, but did you have a custom ROM or custom recovery? I'm assuming since you tried to get to recovery and got the android on its back, that that you didn't have a custom recovery installed..
If someone knows the exact reason this happened, let us know. This is twice I've come across someone with this problem.
FXZ should work for sure though. All is well.
Sent from my MB865 using xda app-developers app
No I don't think I modified anything except rooting and installing cheesecake but I didn't use it. I don't remember having a recovery installed either.
What I did was use android recovery by pushing vol up and down and I reset it. Works fine now I lost root though so I'm going to reinstall it and reset my server on cheesecake because I can't add a motoblur account right now then uninstall it again Lol.
I really appreciate the help. I almost hate the A2. 2 phones 2 unique problems, like you said some people experience a issue that no one else has.
Sent from my MB865 using xda app-developers app
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
dontsayeta said:
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
Click to expand...
Click to collapse
The battery was at ~60% when I was flashing.
ALSO: I can't get into ODIN mode as the device doesn't respond to any type of button combination.
Deleted.
dontsayeta said:
Ok. I don't know what steps you have taken so far, but do a battery pull and then try to get into Odin mode.
Click to expand...
Click to collapse
I don't know if you read the OP or not but I did in fact already do what you stated. It does not work. I have: Battery pull+attach to USB, Battery pull+battery back in. Neither work to get back into ODIN mode.
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
dontsayeta said:
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
Click to expand...
Click to collapse
I understand, I have the same restriction. However, I think that the device is simply bricked and cannot be recovered. If no solution is posted then I will be heading to the VZW store tomorrow I suppose.
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
Your phone is hard bricked. I'm gonna guess you were flashing a non Verizon ROM, probably an international.
The only fix at this point is a JTAG service. Also, unfortunately you would not have been able to restore before leaving recovery anyways. I'll try to find the popular website people use for that service.
Sent from my SGS3 running Eclipse 2.1 build 4
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Zalithian said:
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Click to expand...
Click to collapse
Thanks I couldn't remember the site.
Sent from my SGS3 running Eclipse 2.1 build 4
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Probably just google about flashing roms, find a youtube video and follow instructions. Wonder if a lot of videos don't have a warning, or if people ignore it.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
I'm just an idiot, and jumped the gun on this flash.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Well, back in the days before quadcore... the roms that were made for the international HTC Desire HD also worked on the us version the HTC Inspire 4G. . . I fell right into the pitfall after getting used to that.
I'm lost.... Phone is stuck at the red electric eye animation. I can so a hard reset, actually did that several times, but the phone always stops in this animation. I haven't changed anything in a while other than downloading an app to reboot the device with one touch. The Phone is unlocked and rooted, but nothing beyond that.
Any ideas?
Thank you,
David
I've never seen this before. Usually only happens on bad recovery installs, ROM installation, or other flash. The only thing I can recommend is a flash of the stock image with RSD lite.
Wait for some other replies though.
Thanks, i would definitely have to research how to do that.
I can get to the boot menu, but all options... recovery, fast boot and factory all get stuck at the electric orb/eye animation.
davfed said:
Thanks, i would definitely have to research how to do that.
I can get to the boot menu, but all options... recovery, fast boot and factory all get stuck at the electric orb/eye animation.
Click to expand...
Click to collapse
If you can't even get into recovery, then definitely it means it's time to go into fastboot mode and flash a stock image back onto it.
You can get to fastboot mode by rebooting the phone (or powering on) and then immediately press vol down + power and that will get you into fastboot mode where you can use either RSDLite or House of Moto tools to flash a stock image back onto your phone.
That seems to be the only recourse.
OK, downloading RSDlite and installing now. Im in AP fastboot flashmode on my phone. I have the latest device drivers from Motorola installed.
So, this whole finding and flashing new image thing is beyond me, i will search for it, but if anyone has an easy explanation, i would greatly appreciate it.
Edit: Ok, i found the correct image to flash. I'm assuming that it is the complete OS? if that is the case, I'm going with the last version where I had almost double battery life. Am i on the right track?
So basically you are going to download a 700mb stock image. Go to http://sbf.droid-developers.org/phone.php?device=5 for that download. That will be what you are flashing
Sent from my DROID RAZR HD using Tapatalk
Thank you so much Sad Panda!!!
I'm flashing 4.4.2 instead of the last version I was planning on. It's in process now so I'll know soon.
If this works, then I will look for a custom rom without all the bloatware and other garbage. I suppose this failure has made me do something that i have always been too nervous to try.
I know that asking questions without searching is frowned upon, and I get that, but having someone to interact with is very reassuring.
Again, many many thanks to you for your time!!!!
Not a problem. I have a question out there right now waiting to be answered, so it's appropriate for me to give back
Sent from my DROID RAZR HD using Tapatalk
It worked. You are my hero Mr. Panda!!!
Thank you!!!
except sbf doesnt have the .15 update yet...but can be found here: http://www.droidrzr.com/index.php/topic/54379-fxz-442-1834615/
cmh714 said:
except sbf doesnt have the .15 update yet...but can be found here: http://www.droidrzr.com/index.php/topic/54379-fxz-442-1834615/
Click to expand...
Click to collapse
is it worth reflshing to get the .15?
I'm halfway to setting my phone back to the way it was.
davfed said:
is it worth reflshing to get the .15?
I'm halfway to setting my phone back to the way it was.
Click to expand...
Click to collapse
IMHO, nope, no real reason if everything is working well.....there was a security fix however.
http://www.verizonwireless.com/dam/support/pdf/system_update/droidrazrhd-09-09-14.pdf
DELETED! 5.1.1 root is out, so why downgrade?!?
Hey thanks! Are you going to try to downgrade your new replacement flex? I'm still a little hesitant to do this as I'm worried about the brick like the others.
Sent from my LGLS996 using Tapatalk
I have to downgrade because of root . no root no gsm signal for me. But i just waiting for root or a safe way to downgrade.
Sent from my LGLS996 using Tapatalk
I think the mods should close this before someone tries it and bricks their phone. I don't see how unplugging it after the phone tried to reboot will do anything. The phone already flashed everything it's going to flash before the reboot. So unless you have personally tried this, I would not use others as genie pigs.
justinswidebody said:
I think the mods should close this before someone tries it and bricks their phone. I don't see how unplugging it after the phone tried to reboot will do anything. The phone already flashed everything it's going to flash before the reboot. So unless you have personally tried this, I would not use others as genie pigs.
Click to expand...
Click to collapse
I have personally tried this, hence the WARNINGS! I have had it work, and I have had it fail. There, however, are people out there who want to know the process.
lyphe said:
I have personally tried this, hence the WARNINGS! I have had it work, and I have had it fail. There, however, are people out there who want to know the process.
Click to expand...
Click to collapse
i tried it and it doesnt work..results in a brick..i would take it down..the risk is now worth it...i i followed th instruction to the dot..plain and simple...lg has implmentend a anti roll back...ask the g4 users...they'll agree
So, first two phones I tried this with worked with no issues. Phone number three was a hard brick almost instantly. Maybe there are different HW versions? I got a blue screen with Factory Reset 2, something like that. Rebooted phone and hard brick. Black screen, no lights, nothing. Unsure of the reason, as I did exactly the same steps as before with success. Removing directions. Rather people be stuck on 5.1.1 than bricked. Plus, now with 5.1.1 root out there should be no reason to downgrade anymore!