Related
Hey Everyone,
I'm hoping someone can help me find a way to un-brick my Galaxy Nexus GSM 16GB (GT-I9250M). Before you call me an idiot, I'll have you know I wasn't flashing it or anything. I was simply listening to music when the screen went all glitchy and the sound started looping. Then the phone attempt to restart, but mid way through booting, it would glitch out again. It would repeat this until I finally pulled the battery. When I got home, I tried to get it into Fastboot mode or Download/Odin mode. Neither of which worked. I was running the stock version of android. If I recall correctly, it was running 4.0.2.
So in a nutshell, here's the status of the phone:
Regardless of what I do, Fastboot mode and Download/Odin are not accessible.
No matter what combination of buttons I press, the screen always shows: Phone ... Yellow Alert Triangle ... Computer
Using Galaxy Nexus Toolkit or Wug's Toolkit, the phone is not listed under Fastboot or ADB devices.
While the phone is plugged in via USB without a battery, I see device manager adding and releasing an OMAP4440 device every second or so.
When I plug in the phone (with the battery) in via USB while its off, it will turn itself on showing the alert screen mentioned above.
ODIN is about the only app/toolkit I've used that "sees" the device.
Using ODIN, I have tried various stock images mentioned in the forums. All of them have either failed or get stuck on "NAND Write Start!!"
I've read dozens of posts on various forums but I could not find a concrete solution, so I'm appealing to you guys for help. Any help would be great appreciated.
Thank you!
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
1. first off you need to download "Odin 3 v1.85" here
2. also download CF-Root-GGN_YAKJU_ICL53F-v5.1 here
3. open Odin in your computer
4. where it says PDA put CF-Root-GGN_YAKJU_ICL53F-v5.1
5. Power on the device and when you have the "phone triangle pc screen" connect it to your PC.
6. ???
7. PROFIT!!!
kmdub said:
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
Click to expand...
Click to collapse
You're probably right. I still have my Nexus S which I can fall back to resort to this. I will try what nonione has suggested, and if that doesnt work, I will likely look to replace the phone.
I've never seen a samsung phone that couldn't be recovered (other than physical or water damage).
You can easily get the phone back with odin (no you do not have to be in odin mode on the phone).
Study up on it....tons of threads, use search.
Never seen a bricked Samsung....ever...and I've had at least 6 or 8 different models.
(edit)
There;s quite a bit more to it than nonione tried to walk you thru.
You will need the correct drivers on your computer first...buncha other steps too.
Study hard before you try odin.
Google, "Galaxy Nexus OMAP Unbricker". Download it and when the OMAP devices comes up in the Device Manager quickly right click on it and install the driver includes with the OMAP download. Once the driver has installed run the .bat file in the download. Should go to Fastboot now.
Then:
http://forum.xda-developers.com/showthread.php?p=27160425
Download the .pit file here:
http://forum.xda-developers.com/showthread.php?p=27152659
Sent from my SGH-T769 using Tapatalk 2
That's easy to repair, dude
That's not a brick, that's just telling you, that the firmware files are corrupt, all you need, is a jig, a Windows PC, Odin and chainfires ODin files
I can walk you through, on Teamviewer, if you want. I've had this problem quite a lot (Not on the GNex, though) I jope I get it, so I get a GS 3 ^^
I do have the same phone with the same problem..but currently out of the country, so cant get it replaced.. I get no yellow triangle my phone is completely dead..I tried the omap flash no luck..please let me know if the omap flash tool worked for you..
Hey guys,
So a bit of an update. I tried using Odin to flash. None of the files suggested worked for me. I also tried the OMAP flasher. While it "did something" without erroring out, it did not switch to fastboot mode for me. My phone is simply stuck in that yellow alert state. So now, i'm going to try using a Jig as familyguy59 has suggested. I saw a video of one guy use one to fix the exact same issue as I'm having, albeit with his Samsung Galaxy 2, but it looks promising. I purchased one a couple days ago and it should come soon. I'll let you guys know how it goes.
Hey Guys,
So I tried the jig i bought. No dice. I'm pretty disappointed. : / I guess off to Samsung it goes... I just don't have any luck with Samsung products.
Hey guys, My Samsung Galaxy Tab 3 10.1 (Wifi) Won't turn on anymore. Don't even charge! My brother was playing minecraft until my Tablet's life reach 0% (Died). Then I charged it, It's still charging after 30 mins of charging I turned it on then the SAMSUNG GALAXY TAB 3 logo appear (Start-Up) but it fails like it shutted down. I tried charging it again but it wont charge anymore nor turn on, I'm not using any ROM but i rooted my SGT 3 10.1
Anyone knows how to fix this? Please help asap!
Try different charger, usb cable, leave it for a while then try charging it, plug it into computer usb port or plug out sd card then try
Sent from my SM-T210R using Tapatalk
Ripshock said:
Try different charger, usb cable, leave it for a while then try charging it, plug it into computer usb port or plug out sd card then try
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
Okay, Gonna try those now and hope something will fixed this. I'll reply if it works or not soon
Edit :
Be right back in 2 hours to check everything.
Edit Again :
My Tablet is fixed now, Thanks dude.
What I did is stopped charging for 10 minutes then i charged it using PC/Laptop then waited 1 hour, then charge it on normal then it started to charge and turned on. but again, stuck on SAMSUNG GALAXY TAB 3 logo then shut down....
None of those works. Any other idea?
I would do the process over again. But do not start the tablet. See if you can get into recovery mode (Vol+ / Power) or download mode (Vol- / Power). If that is successful then leave it there for awhile. Power off and try again. If good, then I would reload the OEM Rom or a backup that you may have. But I would not try powering the unit again. There might be a corrupt file caused by the initial improper shutdown.
It got even Worse, I tried to do the process again but it DOESNT turn on or Charge anymore. I waited 1 hour then charge, still, charge 2 hours, still. What to do now? Theres no helper here on our village except me so please help me
If your device is not charging then I wonder if it is the charger and not the device. I don't think the battery could go bad that fast. I could be wrong, but I don't think. So that leads me to believe that your charger possibly is not working like Ripshock mentioned.
Is the charger the OEM that came with the Tablet?
If not, can it produce 5vdc @ 2 amps?
What about the USB cable, is it OEM that came with the Tablet?
If not, is it wired correctly and can it handle 2 amps?
Regardless of how you answered the questions, I would seek another source for charging. I don't think the PC will charge. I don't believe the USP ports are setup to handle that much current. I could be wrong, but again, you might seek out another source for charging.
UPC won't charge tab. It has to be plugged into an eletrical outlet
Brian D said:
If your device is not charging then I wonder if it is the charger and not the device. I don't think the battery could go bad that fast. I could be wrong, but I don't think. So that leads me to believe that your charger possibly is not working like Ripshock mentioned.
Is the charger the OEM that came with the Tablet?
If not, can it produce 5vdc @ 2 amps?
What about the USB cable, is it OEM that came with the Tablet?
If not, is it wired correctly and can it handle 2 amps?
Regardless of how you answered the questions, I would seek another source for charging. I don't think the PC will charge. I don't believe the USP ports are setup to handle that much current. I could be wrong, but again, you might seek out another source for charging.
Click to expand...
Click to collapse
tones160 said:
UPC won't charge tab. It has to be plugged into an eletrical outlet
Click to expand...
Click to collapse
As I suspected, but I thought I read somewhere that the PC can be setup to do just that on the USB port. Key phrase is "thought I read".
Nah. For some reason the tablet can't charge and transmit data through the cable at the same time unlike our phones and other devices. Personally i think it's stupid that it won't charge but hey that's how they were made lol. I use a very good cable too.
Brian D said:
As I suspected, but I thought I read somewhere that the PC can be setup to do just that on the USB port. Key phrase is "thought I read".
Click to expand...
Click to collapse
Well, I have been to this situation more than once (Galaxy Tab 3 10.1 and Galaxy Tab 2 7.0, which are both family tablets). Do a "force boot"
Steps:
1.) Leave it there for, like, 4 hours or while it is charging do step 2.
2.) Now, press the power, volume up, volume down and home button together, until the it boots up completely
3.) Charge the tablet again..
Easy as that.. If that does not work, remove the battery inside (You need to have proper tools and a hand that can search youtube)
or, even if that does not work, your brother may have screwed something up (Either by dirty flashing another ROM or by doing some dangerous system modifications).. Your last hope is the repair shop (If you have warranty, send it back to a SAMSUNG REPAIR SHOP and act dumb, they will fix it for you, free of charge.)
I am not 100% sure here, but I don't think pressing the home key while using the power and vol keys will do anything. I believe that to be a process found on some of the other Samsung devices, but not the P5210. I personally have not tried it and I really don't want too knowing right now that my machine is working just fine. Would hate to do something that I cannot reverse.
- Mᴏʀᴏɴ - said:
Well, I have been to this situation more than once (Galaxy Tab 3 10.1 and Galaxy Tab 2 7.0, which are both family tablets). Do a "force boot"
Steps:
1.) Leave it there for, like, 4 hours or while it is charging do step 2.
2.) Now, press the power, volume up, volume down and home button together, until the it boots up completely
3.) Charge the tablet again..
Easy as that.. If that does not work, remove the battery inside (You need to have proper tools and a hand that can search youtube)
or, even if that does not work, your brother may have screwed something up (Either by dirty flashing another ROM or by doing some dangerous system modifications).. Your last hope is the repair shop (If you have warranty, send it back to a SAMSUNG REPAIR SHOP and act dumb, they will fix it for you, free of charge.)
Click to expand...
Click to collapse
Yep, I did those steps. and it's turning on now. but i cant start it up. When I open it, it goes to TWRP mode. This happens when I wipe all my phone cache,dalvik,etc (everything) then when i restarted the system it says "no OS installed, still continue?" I choose yes, then it said "your tablet's root could be corrupted, want to install a fresh new one?" I choose yes then my tablet restarts but on TWRP again, I install a rom named Pimpdroid then restarted the tablet, still the same (Always go to TWRP mode even i'm not press power+up volume+home bottom together) Just the power button but it goes to TWRP mode, i tried installing other roms but its still the same. If you can't understand properly due to my poor english. I can make a video on it if u r willing to help me. I really need help guys since theres no repair shop here its just an island!
Does anyone experienced this problem already? or does anyone knows how to fix this problem? Help me please
RazerKnight17 said:
Yep, I did those steps. and it's turning on now. but i cant start it up. When I open it, it goes to TWRP mode. This happens when I wipe all my phone cache,dalvik,etc (everything) then when i restarted the system it says "no OS installed, still continue?" I choose yes, then it said "your tablet's root could be corrupted, want to install a fresh new one?" I choose yes then my tablet restarts but on TWRP again, I install a rom named Pimpdroid then restarted the tablet, still the same (Always go to TWRP mode even i'm not press power+up volume+home bottom together) Just the power button but it goes to TWRP mode, i tried installing other roms but its still the same. If you can't understand properly due to my poor english. I can make a video on it if u r willing to help me. I really need help guys since theres no repair shop here its just an island!
Click to expand...
Click to collapse
When it asked to reinstall the root, say NO. Then power off the unit. Do not try and run the tab at this time. There is no OS. Start the tab in download mode. Connect to PC and start ODIN. Load the OEM Rom. This is the only way to get things back to normal unless you have saved a backup. If you have a back up, then start the tab in recovery mode (TWRP/CWM) and restore from backup.
I would recommend NOT installing Pimpdroid or any other rom until you have a fully operational tablet again. Best to always start from a fresh OEM Rom.
What is OEM Rom? and where can I download it?
OEM = Original Equipment Manufacture
OEM Rom is the firmware that was developed by Samsung and is the only official Rom for your device. All the other roms that are developed here are done so with caveats placed on them. Mainly that the roms can damage your device or brick it (cause it to fail completely).
Original firmware (OEM Rom) can be found here. In the search window just enter the model number of the device you have. In this case that would be P5210. It will take several hours to download the rom as it is huge, on the order of 1.9GB. Just be patient. It is always a good idea to have the OEM Rom safely tucked away on you computer for situations like this.
Brian D said:
OEM = Original Equipment Manufacture
OEM Rom is the firmware that was developed by Samsung and is the only official Rom for your device. All the other roms that are developed here are done so with caveats placed on them. Mainly that the roms can damage your device or brick it (cause it to fail completely).
Original firmware (OEM Rom) can be found here. In the search window just enter the model number of the device you have. In this case that would be P5210. It will take several hours to download the rom as it is huge, on the order of 1.9GB. Just be patient. It is always a good idea to have the OEM Rom safely tucked away on you computer for situations like this.
Click to expand...
Click to collapse
It's just like a rom? after downloading ill just install it like other roms?
and, Which country firmware should I download? There are tons of Country but the same rom
You will download the version for your country. I have no information about your whereabout. So you will have to find the rom for your country or region of the world.
You will need to extract the MD5 file from the zip and place it on your computer. Once extracted, you will open ODIN and load the MD5 file into the PDA slot and upload it to your device. Don't worry about the SS_DLL file. It will take some time to load into ODIN and then some time to load into your device. Do not stop the upload or interrupt. Once loaded, you will then restart your device and configure it like it was brand new out of the box.
The standard recovery will be loaded also. If you desire to load TWRP or CWM, you can if you want. You can also root the device. But I would not recommend loading any of the other roms until you get a better understand of what that rom does and how to load it. There are many posts on XDA that tell you how to load an OEM (stock) Rom. Just do a search for them. No need to be redundant here.
Just be careful.
Brian D said:
You will download the version for your country. I have no information about your whereabout. So you will have to find the rom for your country or region of the world.
You will need to extract the MD5 file from the zip and place it on your computer. Once extracted, you will open ODIN and load the MD5 file into the PDA slot and upload it to your device. Don't worry about the SS_DLL file. It will take some time to load into ODIN and then some time to load into your device. Do not stop the upload or interrupt. Once loaded, you will then restart your device and configure it like it was brand new out of the box.
The standard recovery will be loaded also. If you desire to load TWRP or CWM, you can if you want. You can also root the device. But I would not recommend loading any of the other roms until you get a better understand of what that rom does and how to load it. There are many posts on XDA that tell you how to load an OEM (stock) Rom. Just do a search for them. No need to be redundant here.
Just be careful.
Click to expand...
Click to collapse
Well, This is pretty weird. There's no Philippines (Which is my country) OEM rom and on the Tablet, it wont go to Recovery mode or Download mode. because when I charge my tablet it automatically opens then go to TWRP. When i turned it off it goes to normal charging. Then when I try to open it using this (Power button+volume up+ Home) it still goes to TWRP mode. How to fix this?
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
oscillik said:
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
Click to expand...
Click to collapse
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
alvinhochun said:
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
Click to expand...
Click to collapse
Yeah, this is likely going to be an expensive lesson in making sure I don't have multiple factory image folders sitting on my drive, ready for flashing onto the various Nexus phones I have to 'administer' for my family and friends!
From what I've been able to gather, I had already come to the conclusion that it may be salvageable, providing I can get access to the appropriate partition image files from Qualcomm and the appropriate tool to flash it, and instructions! I've seen as much for the Nexus 5, but nothing for the Nexus 5X.
I can try and get some screenshots later tonight, and even boot up a Linux box to get some more info.
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
alvinhochun said:
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
Click to expand...
Click to collapse
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
alvinhochun said:
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
Click to expand...
Click to collapse
If it reboots the phone, I'm not getting any feedback from the device whatsoever of that happening. Nothing appears on the screen, no vibration, no sound. Even if I do that while it's plugged into the computer, I don't get the Windows 'disconnect / reconnect' USB device sound (if you get what I mean?) to denote that a device has been unplugged/replugged back in - which is what I would expect to happen if I power cycled the phone whilst it's connected to the computer.
Hi,
I am dealing with the EXACT same situation. Did you find any solution to this? I wanted to sell my 5X in order to purchase 6P and when the buyer came I wanted to un-root the phone and write back the original recovery image. Anyway, I ended writing the bootloader also, but from my wife's Nexus 5 (hammerhead) and not from 5X
Same problem. Tried a lot of qualcomm tools and the lg flash tool with tot file. Doesnt work.
bricked
Hey brother, I am sorry to say you are screwed. I just did the same thing to my phone two weeks ago. It seems without the bootloader the phone will not react at all and yes the flash-all script flashs bootloader first then restarts but once the nexus 5 bootlader is flashed the phone cant start the bootloader.
here is my thread i started with some responses but its all bad news
http://forum.xda-developers.com/nexus-5x/help/hard-bricked-phone-t3278033
There is a plus side for you that is not for me. I have called google and was 100% honest with them as to what happend. They told me they would not warranty me out a new phone since its my fault. However they did say because it is a software issue LG should be able to fix the issue. I already started the RMA process and my phone should be arrivng at LG on monday (two days from now) so hopefully they cover it under warranty or charge me something small to just flash the proper bootloader.
I will report back to my orignal thread and this one for others as I am betting as time passes a lot of original nexus 5 owners who upgrade and are used to flashing a lot will also make the same careless mistake.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
anjelika said:
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
Click to expand...
Click to collapse
They told the truth and everything worked in their favor: http://forum.xda-developers.com/showthread.php?t=3278033
Sent from my Nexus 5X using Tapatalk
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
konsolen said:
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
Click to expand...
Click to collapse
pardon me , did you have solve it ? my 5x have this problem for a week , i can't find the file , what i find is boardiag (N5) and blank flash (n6)
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
thanks for reply , it's so hard to find OTG with C type in indonesia and LG in here must to check it not sure they can fix it .
Did some tested if this method works for N5x?
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
Hi I have this issue on my H791. I do have a USB C OTG cable. Are you saying you were able to point the LG Tool to the file on the SD card through the OTG cable/PC, then flash? Can you elaborate or point me to the thread in reference? I backed up my EFS partition before all this happened, so my IMEI is still intact on a backup. Thanks.
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
I found a way off QHSUSB_BULK that worked for me--with rubber bands. To invoke either boot loader when stuck like this I needed to drain the battery completely, and I figured that would take a very long time without the screen even turning on.
I noticed that if I held in any of the volume keys + power while connected to my PC that the phone was in reality rebooting every 30 seconds--it would come and go from Device Manager. So I grabbed three rubber bands and wrapped them around the phone at each of the 3 buttons and pressed them in.
After a few hours the phone was completely dead and I could power it back on with a brief charge. Into the bootloader it went and I'm back in business.
So, here's the deal with this phone. It's sat untouched for many many years. The original owner can't remember why she got rid of it (family friend). So I volunteered to take it, and turn it into an emulator device. However, it was made clear as to why she got rid of it. The phone is stuck in a gnarly boot loop. The boot loop is, Sony Ericsson screen lit up, and then goes to an unlit version of the logo. After a while, the phone will restart repeat. The phone will get into flash mode (green light) and will not continue the loop but stays on the unlit version of Sony Ericcson. I've gotten it into fastboot once, maybe twice, but I can't remember exactly how I did it (holding menu doesn't work)
I have installed the drivers for the phone, however, the phone is listed as:
E:\
Device Type: Portal Device
Manufacturer: SEMC
Location: on Volume
The drivers that it is apparently using is wpdfs.inf
Things I have tried to correct this issue.
-The Xperia app (tells me to enter flashmode in its own way and never does anything after)
-Flashing using "FlashTool"
It sees a phone but just says.
"19/025/2018 22:25:46 - INFO - Device connected with USB debugging off
19/025/2018 22:25:46 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I've attempted using a fastboot method but nothing substantial as fastboot rarely happens.
Accessing the device through ADB (ADB shows not devices connected
Accessing the device through FastBoot (FastBoot shows "waiting for devices")
I have crawled through dozens of pages worth of information, similar questions, similar problems and come up short. Any advice would be super helpful.
Will provide images, and further information if requested. Thanks for your time.
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
inaroom said:
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
Click to expand...
Click to collapse
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Disenfranchised said:
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Click to expand...
Click to collapse
to install flashtools drivers in win 10 you need to disable uac but maybe you already did that. make sure the adb drivers are fully and correctly installe. have you tried flashing a kernel in fastboot mode by pushing the search button? also i would try to install r800i or r800a drivers. then i would suggest to make a little bit of search (i know you already did a lot...) to ensure that you can flash r800i or r800a firmware on your r800at and also try that route. i´m sorry i can´t help you more but i´m in europe and never worked on a r800at..
Hey, dont worry about it. This post is basically a hail mary for a phone that super old. I haven't tried flashing in fast boot because I have only ever gotten in fast boot once or twice. Fast boot is menu key correct? Cause I see conflict information all over the place.
i´m pretty sure it´s the search button for fastboot mode
Do you need a new battery?
Hi Disenfranchised,
I recently got out my old r800i GSM which was regularly being flung across the lounge by my kids, attached a charging cable and I had exactly the same boot loop issues as yours, but only as long as the phone was being charged. I ended up biting the bullet and buying a new battery and the phone started up. I ended up flashing Gin2Kat and it has been working well other than occasionally reverting back to the same behaviour for about an hour if the battery was completely discharged. The funny thing is when i finally manage to boot the phone at the right point during the boot loop cycle, the battery is only at 2%, meaning during the boot loop the battery is charging for maybe only a fraction of the on-off cycle.
It's a bit of an outlay (my battery was about GBP £10 - ebay). I now play SNES games on this every day during my commute. There are a few quibbles - the audio out port doesn't work (bluetooth audio works) and I get a wifi error but I ended up using Gin2Kat's apk installer to install my apps from micro-sd.
Anyway, it's a bit of a risk but see how it goes.
Fuzzy
So I just got this phone yesterday, and tried to update it via the Motorola Smart Assistant.
Clearly something went wrong, cause now the phone will not boot. It will load up AP Fastboot Flash mode, and nothing else can be done.
All I want is it to be on Oreo. I have read lots of guides, but I do not know which is the most simple way of doing this. I don't really want it rooted, just stock android.
Can anyone help?
I have the firmware for oreo, I just don't quite grasp how to get it running on the phone now. My pc does not seem to detect the phone anymore.
First, post, please, photo with error.
Then get latest Motorola drivers installed, and LMSA too. Is connection stable? Genuine cable? Use USB from the motherboard port directly? Other USB devices do work?
After you get phone be visible by PC you can attach diagnostic info that gives "fastboot getvar all". Download Minimal ADB package (see google, or here XDA), launch cmd, then this command.
Rayravage said:
So I just got this phone yesterday, and tried to update it via the Motorola Smart Assistant.
Clearly something went wrong, cause now the phone will not boot. It will load up AP Fastboot Flash mode, and nothing else can be done.
All I want is it to be on Oreo. I have read lots of guides, but I do not know which is the most simple way of doing this. I don't really want it rooted, just stock android.
Can anyone help?
I have the firmware for oreo, I just don't quite grasp how to get it running on the phone now. My pc does not seem to detect the phone anymore.
Click to expand...
Click to collapse
I had the same problem when trying to upgrade from 7.1.1 to Oreo.
I power off and on again with volume button down press and reconnect USB cable to PC
With the same Motorola Smart Assistant software open, click on Rescue tap
At first no action, but after few trials, the software re-flashes the phone and brings it back to Oreo boot screen.
You can also read the procedure from the post#2387 in the link below
https://slickdeals.net/f/12409510-6...at-t-smartphone-100-free-shipping?p=123370042
Good luck.
I just got my Z2 on the 25th. Bought brand new directly from Moto ATT variant. I just used the setting/system/System Updates. The phone came with 7.0 and I used the above to get it to 8.0.0. It actually took 4 times to get to Oreo but never had any problems. I've never trusted those up-date apps. They seem to work fine on some phones and not on others.
I'd do a factory reset and try to update through the Android settings.
I'm not rooted or anything just locked up ATT stock.
Or try this:
https://support.motorola.com/us/en/softwareupgrade
Thanks guys, I just asked for a replacement and got a new one shipped and sent off the messed up one. I'm not even going to bother updating this, as I am selling it anyway.