I would like to start with saying I am new to posting here, have used this site for some time now for information but never had a actual problem that I could not fix from some searching.
I am trying to load InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285 onto my Atrix 2 with Motorola RSD Lite version 5.6 and every time it gets to step 6 it stops and says. Failed Flashing process. Failed flashing process. 6/20 flash cdt.bin "cdt.bin" ->Phone returned Fail; phone connected.
A little bit of a back story as to how I got here. I dont remember how exactly I got here, I was trying to OTA upgrade to ICS and did some reading on here as to what i had to do to un root my phone. Somehow in the process i believe I soft bricked it. It will power on to the Motorola dual core screen but that is it. I am following the n00b guide to FXZ.
This happened a few days ago, and during the process of me trying to fix it, Fast boot had the battery status as low. So I ordered a wall charger from Amazon it came today, so now with a fully charged battery I started to dive into this again, and got this error.
Anybody have any insight to this? I am sure it is something I am doing stupid or not understanding.
Thank you for your time.
Got it to load 2.3.5 I was on 2.3.6 before. But close enough, I am just happy to have this phone back. I dont know if i could take any more of the Blackberry i was using.
I switched computers, and USB cables. I guess that could have been it. I have flashed roms onto a few phones for friends on that the PC I was originally using. Both had up to date drivers and everything. It is a mystery.
Related
I have been doing this since the g1 came out and last night I finally managed to get a device to not respond at all. I have an i9020a that I had rooted and flashed brainmaster's miui rom. Long story short I needed to return the phone due to poor call quality from my end. I flashed the nandroid backup and was stuck in airplane mode. Every rom I tried to flash would not take with e:verification errors or just plain aborts. I relocked and unlocked, and put 2.3.1 stock recovery back on with still no luck. Finally after all frustrations I went to odin. I loaded the files listed in the thread, APP[ODIN] thread, and once again it failed to load. I restarted the phone and tried again but it was late and when odin didn't respond I unplugged the usb which in return made the phone unresponsive. No power on, no recovery, no boot loader, and no download mode. I ordered a jig and am hoping wedensday when it comes in it will get me back to down load mode. I am hoping someone can help me find the correct files via odin for the i9020A. Thanks for reading, I have googled everything via i9020A and there are not many threads about this problem.
lot of views but no answers, i was shocked when I kept googling but no answers. Guess no one has had the problem I faced with the 9020a
well today I just took it back to best buy and said I woke up and it wouldn't turn on. Gave me another one, so time to root
Just saw this post. Glad they gave you a new phone with no issues. If I would have read this post earlier, I would have recommended Odin but obviously that didnt work for you. I would have been fresh out of suggestions!! Lol.
Sent from my Nexus S using Tapatalk
okay so i have spent many hours with my new motorola photon 4g that i recently got from sprint. bout 4 days now. im more use to using samsung android devices and htc devices and this is my first motorola. i had been wanting to root it because its my favorite thing with an android when i get one. so i did research and unlocked my bootloader and did the unlock sbf file and installed clockwork mod revocovery as well. after all that my photon was working fine but was on stock rom. i had downloaded a rom and put it into the phone and of course installed it. im not used to motorola and it was my first time learning about their bootstrap and blah blah blah. after installing i had tried turning the phone on but it just stayed at the Motorola dual core screen. i tried booting three more times to no luck. so then i had tried another rom and again i had no luck. i should have done the smart thing which is after the unlocking and putting on recovery to make a back up immediately but for some reason didnt. so i go online to find another sbf file so that i could start all over and see my mistakes, but then my battery was way to low. my advice to you is to make sure your battery is filled up cuz trust me this was a ***** to figure all out. so this is what i did in case if any body has this kind of problem, cuz i know im not gonna be the first, well maybe, but definitely not the last. what i found out is the phone wont let you flash any files when battery is low. and as i can say, its for saftey reason cuz if it dies while flashing, well you might be **** out of luck. depending on what you are flashing. but what i found out is that if you connect the hone to the wall outlet, the phone will turn on into clockwork. dont try plugging into the computer cuz it will be useless. i tried several times till i finally got the message. the recovery is the only thing that can be booted up. you dont even need the battery in the photon. it will still turn on as long as it was in the outlet. i then transfered files to the sdcard from another phone, over and over till finding the right one, then flashed and flaseh. finally, finally found a rom that woul work with ,y phone. i kept the rom till i was able to charge the phone. rom kept bootlooping but it kept bootlooping long enough to charge the battery then flashed the sbf sprint file to my phone. i wanted to write this cuz i was hoping somebody would be able to explain to me what i may have done wrong with the flashing or if their was a step that i had skipped cuz it seems like no rom works as of now with my photon. hopefully someone can help me out here cuz i really do want a custom rom. or maybe someone can tell me what i should do in order to install a custom rom and have it work for me.
start here:
http://forum.xda-developers.com/showthread.php?t=1413349
jokersax11 has done an amazing job bringing ICS to the photon... I believe he will soon have his beta officially picked up by cyanogenmod... also, I am pretty sure he's close to fixing the 4G that you loose when you unlock the bootloader.
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
I am new to this forum in terms of posting but I have read a lot in the past. Three months ago I used this site to root my Samsung Note 2 on Verizon. I used Adam Outler's one step method to root the phone. I never downloaded any other ROMs or anything. I just used the root to delete Verizon programs. I ran across some issues with my screen and I was planning to send my phone back to Samsung since it is still under warranty. I unrooted the phone using "imnuts" instructions and everything went well. I then shut off the developer options since I was planning to send the phone back. The binary counter never changed from no and life was good. Later that day the phone ask to do an update with Verizon. I said ok and let the phone reboot. A few minutes later I looked at the phone and the Samsung Note 2 screen kept flashing and shutting down. I am unable to get into recovery mode (power+up volume+home). I am able to get into download mode but odin won't work since the debugger is off. Some people online say you can run odin without the debugger on but I don't think that is the case. I tried to run the "imnuts" Verizon stock but odin quickly says fail. I have read a lot of posts about similar issues but most of the replies were either telling the OP to recover or flash a recover. If my phone is dead I just want to hear that. If you have any ideas please let me know. If I send back to Samsung is this something they will fix? I don't know why it happened but it happened when the phone was back to stock. Any help you can provide would be great. Thanks.
This is the results I get from odin. When I unrooted my phone the first time (the time that it worked) it took about a minute to show the file in the pda section. When I do it now it instantly pops up. I'm thinking the ID COM isn't actually connecting to the phone sine debugging isn't active.
I've been getting help in the Newbie thread, but it's time I start a new topic, since it's getting harder and harder to find replies.
All I'm trying to do is upgrade an old LG from Android 5.0 to 6.0. That's it.
I've got the drivers installed. I've downloaded three different versions of Flash Tool. The only one I got to do anything was "Flash Tool 2014".
The first time I ran it (following the directions on the web page where I found it), I picked "CDMA", "DIAG", and "CSE Flash". I was able to pick "Other Country" and "English" and got the phone to start installing. However, it only got as far as 4% and gave me an error. Now, when I run it, I pick "Other Country" and can't even pick a language. They're all blank. If I continue, all the messages consist of Question Marks, however, it still gets as far as 4% before stopping.
The phone is bricked in Download Mode. I have tried two different USB cables, two different computers, one of which has Windows 7 & 8.1 installed. I've tried all different USB ports to make sure I'm on USB 2.0 and not 3.0. I've tried running in Administrator Mode.
I see many posts about the 4% Error. The solution involves downloading a "wx.dll" file and putting it in the C:\system32\LGMOBILEAX\PHONE folder, but that didn't work. I also so one that said when you get the error, take the battery out of the phone, unplug it, put it all back together, and then Continue. That didn't work either.
What else can I possibly do? Thanks.
Hey, I have been trying to find a rom for 6.0 and I can't find anything. The only way to get to 6.0 is through ota. If you have 5.0 then your lucky. Ota can only be used if you still have a sim card that's active in the phone. There isn't roms for stock android 6. I would try and help but I can't.
If anyone finds away to get stock 6.0 please let me know.
Talking about your issue of your phone being bricked, there is many unbrick methods. I personally used https://forum.xda-developers.com/t/...n-qualcomm-hs-usb-qdloader-9008-mode.2933853/ it helped and fixed my issue. I still had my device info wiped off my phone somehow but at least it works. Your at a issue with a flash tool, fresh reflash with that method I sent if you can use it and start over. I can guide you through it if needed.
You might be stuck at a stand still, tell me what your phone says in device manager. You probably flashed a bad firmware. In that case I used the method above.