My XT2113-2 has been in EDL mode for 6 weeks. I've tried blank-flash and did not work. Any help or suggestions would be much appreciated.
try rescue and smart assistant
[email protected] said:
try rescue and smart assistant
Click to expand...
Click to collapse
That obviously won't work in EDL mode, Smart Assistant requires a phone that can actually boot.
Short of pulling the emmc and programming externally or stealing a signed programmer, blankflash is your only recovery option. Try different ports, computers, and operating systems until you can finally enter fastboot and restore stock firmware. Who knows what's really going wrong with a description as vague as "did not work", though.
I changed the active slot to b. The phrase "did not work" means that i've tried several computers, through linux and windows. So many times over as to remove any of the initial humor I may have had in regards to the mistake I made to put the phone in this state. Ive tried numerous blank flashes and even combinations of blank flashes with modified xml's as well as changing the elf loaders placed in the singleimage.bin. And even numerous loaders from from various sources online. Using emmcdl, qfil, qpst, qsaharaserver, qdl from github, a few others I cannot recall right now. Would appear to me that the only file that I can get the phone to accept without hesitation is the xbl from the latest firmware package. Of course that doesnt do anything for the phone. Updated firmware doesnt seem to accept the blankflash from late 2020. I have toyed with the idea od SDcard boot but I do not have a backup of mmcblk0.
new blank flashes for this phone added to lolinet mirrors
Ok if you haven't fixed it, I know you're shaking your head but humor me and hold power and vol down for 10 seconds. Also for schnits and giggles how did you get it in edl? I know a fastboot command that messes up the phone until you issue the command again and it was like nothing happened.
bobbyp1086 said:
Ok if you haven't fixed it, I know you're shaking your head but humor me and hold power and vol down for 10 seconds. Also for schnits and giggles how did you get it in edl? I know a fastboot command that messes up the phone until you issue the command again and it was like nothing happened.
Click to expand...
Click to collapse
I was foolishly playing around with the phone like I do everything electronic but this time I decided to do something I knew I probably shouldn't... Slot b. I've since fixed it. Found blank flash was added to lolinet dated 10-6-2021. Now phone wants me to update .. not going to happen. I'll find myself bored one day and foul it up again without recourse. Just kidding but it could happen. I enjoy "testing the waters" on things and every once in a while it doesn't turn out good.
I thought it was supposed to revert back to the last bootable slot if the chosen one was not bootable but that didn't happen. Might be a perfect time to grab a copy of mmcblk0 and post it.
Jasonwoodruff2018 said:
I was foolishly playing around with the phone like I do everything electronic but this time I decided to do something I knew I probably shouldn't... Slot b. I've since fixed it. Found blank flash was added to lolinet dated 10-6-2021. Now phone wants me to update .. not going to happen. I'll find myself bored one day and foul it up again without recourse. Just kidding but it could happen. I enjoy "testing the waters" on things and every once in a while it doesn't turn out good.
Click to expand...
Click to collapse
I'm the same way, I'll find that fastboot command for you to see if that was it
Jasonwoodruff2018 said:
I was foolishly playing around with the phone like I do everything electronic but this time I decided to do something I knew I probably shouldn't... Slot b. I've since fixed it. Found blank flash was added to lolinet dated 10-6-2021. Now phone wants me to update .. not going to happen. I'll find myself bored one day and foul it up again without recourse. Just kidding but it could happen. I enjoy "testing the waters" on things and every once in a while it doesn't turn out good.
Click to expand...
Click to collapse
Can you post the blank flash that you used I too booted to b. Thank you
Here are the 3 files that are available on mirrors.lolinet.com. of it depends on your bootloader/software version. The most recent update isn't available.
Qzk30.q4-16, qzk30.q4-40-79, rzk31.q3-25-15.
Related
People that can't get the roms beyond stock to work, are your phones activated?
Is it possible to use the Pac Man Rom or CM10 on an unactivated phone?
I'm having similar issues to others trying to flash Pac Man and CM10.2. The first boot was fine and I can access everything on the phone fine, including settings. I rebooted and the activation screen (which I skipped as this phone doesn't have service) always pops up but I would like to use it without putting it on a cell network. I can skip the screen fine (until I decide to disable it) but then have issues like the keyboard (physical and touch), systemUI or NAV Bar crashing with a constant message pop up telling me it has crashed. I have returned to stock using RSD and reflashed Pac Man and CM10.2 MANY (15+?) times, doing a clean install 99% of the time but also trying a couple dirty installs to cover my bases. I should also note that I flashed the phone to Cricket but have no plans to activate it anytime soon.
Another thing to note is that I had issues getting the custom roms to boot at all as the initial setup would take hours. One time I though it was a boot loop but I left it on all night and it had booted in the morning. I believe it has something to do with the file check at boot (with my 32GB low speed class SD card) but that seems to be resolved and I can get the custom roms to boot fine (on the first boot) even with my 32GB (witch is fine and has no errors nor is generic, before you ask.) I also have tried 2 4GB cards and a 2GB card, all different brands, with no change in behavior.
I have done everything below multiple times and in different orders.(If needed I can give a direct breakdown step by step but if you could do it with the files below, I have probably tried it)
Wipe the phone (including all storage internal and external SDs included)
Using RDS v6.15
RDS asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (Works 100% of the time and never has issues. I keep reverting back to this if I actually need to use the phone)
RDS ClockworkMod, TWRP, and Open Recovery without TWRP (Tried different versions when available)
Then used each recovery to install Pac Man or CM10.2 (tried 10.1 once but had the same issues and I didn't see the need to troubleshoot a rom people seemed to not want to develop for. So 10.1 was only tried once but has the same issues)
Installed GApps at this point but I also tried alternate versions of GApps and not installing it at all. All have the same effect and don't seem to be contributing to the problems at all.
A few installed I tried wiping the phone again or installing each zip multiple times. I also verified the zips were good when on the device to make sure there was no corruption at transfer.
I also tried multiple (confirmed working) SD cards and installing from the internal storage.
I have tried installing arrrghhh's Kernel too.
The issue ether seems to be boot loop (if it's doing a file check) or more often it works until I get one of the said crashes after a reboot.(blame Tyler message is getting SO old...) The time I see the errors seems to be accelerated if I mess with the settings a lot but I don't believe it is directly related to the settings.
My next recourse is to try and flash it back to Sprint (maybe check my Cricket settings) and see if that helps, without it being activated.
On a separate note.
If people need help I can help get you back to stock easily. The instructions/guides on here are all but useless if you don't know what you are doing already. I have seen down to "USE RDS" or "DELETE LINE MD5" like people would just know what that means. I understand RDS Lite is a standard tool for flashing phones but it's nigh impossible to find real explanations on what stuff does in context. I understand the basics though, so if anyone has any questions I can walk you through it.
To start with if you are stuck in a loop at the start of a new rom and it loops between the 'Welcome' Screen (Select your Language) and Activation screen just skip the initial setup by tapping the corners on your screen in a clockwise manor when on the 'Welcome' screen to skip the setup there is a video to explain it here
pocketnow(can't post links )com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
Without doing this or activating the phone it seems to loop between those 2 screens forever (might indicate part of the problem with customs roms....)
I hope this is enough info to go off of I can give you a play by play with the actual files if you need. Maybe a video if needed and I'm feeling extra fancy.
Thanks for your time.
Hey buddy,
If you're trying to make a guide, make sure you call it what it is properly - RSD Lite.
Also, maybe clean up your post a bit so it's a proper guide (as you point out, it's needed) and make a separate thread for your question.
To answer your question, the unactivated phone shouldn't be an issue in of itself - you'll just get the nag screen like you were talking about.
I know there is an issue some are having with rebooting the 4.3 ROM's. Have you tried any 4.2.2 versions of anything? Carbon, CM10.1?
I wonder if your "flash" to Cricket is causing issue, I'm not sure. Let me know about 4.2.
Edit - I missed this part on my first read of your PM. Taking hours to boot is NOT normal. Perhaps remove the SD card entirely, flash using the internal SD... I've never heard of that. Anything over say 20 minutes is probably cause for concern.
Thanks for taking time to answer me.
In no way was I trying to make a guide yet but I guess I could. I just hate posting stuff without useful content so I figured throwing that in was better than nothing. I'll clean it up and set up some links later today. It's frustrating to try and make a full guide before I can post links that would be needed for it. You are totally right though! (complain about crappy guides and kind of make one... )
Part of my point there was that I can't post out of Q and A and this wasn't really a question so I made a question out of it and that's how my post ended up.
I have flashed many phones before but like I said I'll try and put it back on Sprint later today (probably will be a few hours) as I backed up the settings the phone came with. I know it was a wall of text and not the easiest to read so you probably missed it but I also said in my first post that I tried the internal SD card many times and the taking hours to boot isn't the standard and doesn't seem to happen at 99% of the time. It seems to be related to the recovery software I use as it happened a lot more when I was testing TWRP and none when I use clockwork.
What Recovery do you recommend? I swear they aren't made equal...
I tested CM10.1 once and it had the exact same issues as CM10.2 and Pac Man so I didn't test it further but if you want me to test it I can. I just didn't want the Rom.
I don't want Carbon either but I'll test that and AOKP next. It's just annoying that the stock rom works perfect but I can't get these to function at all. I almost wish I didn't get Pac Man to work at all. I'm very particular about my settings and NEED these features after I tried them Pac Man is AMAZING.
Thank you for the help and I hope I can get this worked out.
PS I saw that you were frustrated about working on a rom you don't have a device for. I hope you don't let a little thing like that stop you as, for the little time I have used it, it's all I want. Thanks again.
Blasz said:
What Recovery do you recommend? I swear they aren't made equal...
Click to expand...
Click to collapse
Well, OpenRecovery has probably the most work done for this device specifically. I liked TWRP, but it seems lately it has been unstable - you're not the first who has reported issues lately. I don't think CWM has been updated, unfortunately - but perhaps that's a good thing, it's stable that's for sure.
Blasz- I was just about to start a thread when I found yours, and it very accurately describes the issues I've been having. Here's my progress so far.
I got my Photon Q with Sprint and used it for a few months before Sprint started finding creative ways to take my "$79.99" bill and make it more like $140 a month. Naturally, I refused to pay. So I had a Photon Q with no cell service. This is fine, as I only need it to work on WiFi, not 2G/3G and there is no 4G in the area. Anyway.
At the time, I had Ice Cream Sandwich on it, using the (latest?) ICS firmware from Motorola. This worked very well, but I later tried to use a newer firmware, and all the custom ROMs had shown up while I hadn't been looking. All of these seemed to be based on JellyBean. First off, I tried CyanogenMod 10.2. Worked amazing well! I had literally no problems at all. However, while I was experimenting with different software for the phone, and wanted to see if "Arrrgghh"(sp?)'s kernels would give me some decent overclocking capability. Turns out, the kernel I picked wasn't compatible with the JB firmwares (I probably picked an older one by mistake.) Needless to say, it now wouldn't boot. It'd go to the "Unlocked bootloader" screen and stay there all night (literally, I tried that.)
So, I went back into CWM, which is the recovery I have installed. I erased /data, /cache and /system, and also the dalvik cache and battery stats for good measure. I also formatted /pds and /modem, I believe, which was probably dumb of me since I'm not sure what those do. Then I tried re-installing CM 10.2 from CWM. The installation went fine, and it works gorgeously. However, there's two weird issues:
1) WiFi and Bluetooth don't even BEGIN to work! Neither does Cell, as far as I can tell, because where CM used to be unable to make calls or access the internet (of course, I've not been paying my bill), it now shows an empty signal bar or "No Signal" (the little red X) in the notification bar ... When I try to turn on WiFi using the slider in Settings, it moves to "ON" (stays gray) and pauses for a few secs, then goes back to OFF. Same thing for BT. If I open the WiFi menu where you select an AP, it tells me to turn on WiFi. I do, using the slider up top, and the same thing happens. WiFi and BT simply won't turn on. Tried fiddling with every setting I can find.
Before this misadventure with the kernel/reinstall, WiFi worked great. I connected to a local AP and was surfing the net and downloading apps.
2) The system takes a VERY long time to boot up. It sits at the "Unlocked Bootloader" screen for up to a whole minute. Then it goes to the Cyanogen screen for about 30 seconds. Then it gets to the homescreen. It's fine so long as you let it boot up, but this doesn't seem normal.
Next I tried other ROMs thinking that might help. I installed AOKP, PacMan, CM1.0, Carbon, SlimBean, and I think a few others without results-- they all work but WiFi and BlueTooth are dead. PacMan is the only exception-- it boots up and then endlessly gives me "Blame Tyler" errors until I force the machine to shut off.
I also tried an older ROM, since these are all JellyBean ROMs and I wanted to get back to ICS (I'm not that fond of JB's interface) anyway. I was unable to find any ZIPs I could install through CWM of the stock firmware. I found some IMGs that it looks like I could install via Fastboot, but I don't currently have a PC with admin priveleges (it's not mine) so I can't install the drivers to use Fastboot or any part of the SDK. (I can, however, put files on my SD card, that doesn't require privleges.) The closest ROM I found to stock was "TwistedAsanti" beta-1 or whatever it's called. That installs fine, but again, it takes about 2 straight minutes to boot and it's useless after that:
It gets stuck at "Starting Services..." and will sit there forever, even left there all night. Behind this, a dialog pops up saying no cell networks were found and asking if I want to switch to GSM. (i've been trying GSM and CDMA ROMs all this time, I don't need cell access so I doubt it matters which I use. I'm in the USA.) You can pull down the notification bar and get into the Settings, and even launch a couple programs, but I can't find ANY way to get to a homescreen. Task manager shows Circles is running, which is a widget on the homescreen, so where the heck is that screen? .. I try, again, to turn on WiFi or BT without success. The friggin thing just won't turn on.
Did I eff it up by erasing the "PDS" or "modem" partition? Am I missing something obvious or is my phone just possessed?
In a few days I should have access to a computer where I can hopefully use Fastboot and see about installing a stock firmware (wish me luck). Until then, does anyone have a ZIP file I can flash from CWM to get back to an ICS firmware? I managed to find a copy of the stock firmware, in the form of a dump done from TWRP (in .win files). But as far as I know the only way to install TWRP is using Fastboot, and I've explained why I can't do that. I don't know a way to install TWRP from CWM. Maybe I can do it from CM10.2, if I can put APKs or something on my SD card. I can't get it on the network, so I have to copy all the files manually. Needless to say, it's a pain.
After my frenzy of ROM installing, I got frustrated and decided to see if TwistedAsanti would do SOMETHING if I let it sit at "Starting Services" overnight. To my mistake, I left it under my pillow and the system was quite toasty, and the battery had run dead. Plugging it back into the charger, it made a few worrying clicking noises from the speaker, then the green LED came on. This LED seems to mean "I'm charging, but the battery is too dead to turn on for a while." After it sits there a while, the green LED turns off and it just goes black. Or it goes to BOOTLOADER UNLOCKED and bootloops, or goes to black untilyou fiddle with the power button some more. I can once in a blue moon get to CWM. Sometimes it gets to the homescreen. It will charge up to about 4-7% and no further (battery got damaged by the heat?) It doesn't reliably work when plugged in, it likes to shut off at random anyway.
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Epicenter714 said:
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Click to expand...
Click to collapse
Did you try to use RSD Lite and flash the device back to stock?
arrrghhh said:
Did you try to use RSD Lite and flash the device back to stock?
Click to expand...
Click to collapse
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Epicenter714 said:
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Click to expand...
Click to collapse
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
arrrghhh said:
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
Click to expand...
Click to collapse
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Epicenter714 said:
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Click to expand...
Click to collapse
I have no clue what MiniRSD is - you mean RSD Lite?
If it doesn't show up in fastboot devices, sort that out before trying to use RSD.
As I stated previously, if you were on JB and going down to ICS you have additional lines which are needed to remove.
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
fastboot said:
target reports max download size 31457280 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Epicenter714 said:
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Click to expand...
Click to collapse
I would NOT recommend entering those fastboot commands in the XML file manually unless you KNOW what you are doing.
Sort out why RSD isn't working. adb and fastboot are two different things. If fastboot devices shows the device, RSD Lite should work fine. Try again.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please
Good evening folks. Over the Past week, for some reason, people who downloaded the new Samsung update for A51 have had their phones bricked. FOR SOME REASON, this seems to only be happening here in South Australia. I haven't seen anywhere reporting on this issue other than local news. I have had three A51 phones come into my IT store, all with the same problem.
here is a link to one article talking about it: https://7news.com.au/technology/sam...ng-priceless-photos-vital-contacts--c-9340963
Upon installing the update, their phone will restart then it will not progress past the SAMSUNG logo. I have been able to get each and every phone into recovery mode however I when I try and reboot the phones into bootloader, they simply say "entering fast boot" and then don't progress any further.
Since I have been unable to boot the phone to bootloader I don't have many solutions in front of me, I can either factory reset the phone which has been proven to work, or I can try some alternative method. Simply put, I refuse to take the simple way out and simply factory reset the phone, I don't want my customers to go through the trouble of losing their photos.
The only real option I see is using ADB to install either a new update or new firmware, however, I have had ALOT of trouble finding the necessary software. I have been able to get ADB to detect the devices with a USB connection, so I tried installing some firmware, I found for my device. I didn't trust that this was the correct software, but it couldn't hurt to see if it worked.
Using a515fxxu5gvk6, I was able to find a website where I could download Firmware https://samfw.com/firmware/SM-A515F/TEL I don't believe this to have the correct software but it was the only option I could find that didn't require money or an account.
upon extracting the zip file and typing ADB sideload <file name> it would start the process of installing the software however, it would only install for a single second and then stop working. I would be greeted with the messages: "footer is wrong", "update package took 0.3s", and "signature failed". I believe this means I have either grabbed the wrong software or I have tried installing the software wrong
I really don't know where to find the correct software, and I don't even know if I will be able to update the phone using ADB since I never was able to enable developer tools.
I have already spent quite a few hours on this, and it's starting to drive me insane. I have gone down so many rabbit holes researching different options only to come back up empty-handed. Im lost and really don't know where to turn.
any help would be literally amazing, if someone could even point me in the right direction that's all I need. even if you tell me there is nothing that can be done and I need to factory reset the phone I can at least go to sleep knowing I god damn tried.
Well, one thing you should know is that Samsung doesn't use fastboot to flash software like many other brands. It's unfortunate to say that a lot of the guides you read online are just copy-paste of guides that do use fastboot. Adb doesn't really flash software without elevated permissions afaik.
You can flash firmware using Odin for Samsung devices. There should be plenty of guides online on how to use it, your main goal right now is figuring out how to boot into download mode for Samsung.
What I would do is try to turn the phone off completely if you've been able to boot to recovery. After that, hold both the volume buttons and while you're holding them, connect your phone to a PC. This should force the phone to boot to download mode. Read the screen as it may ask you to press VOL + to proceed.
After that, you can flash the files
AP_XXXX
BL_XXXX
CP_XXXX
HOME_CSC_XXXX (Use HOME_CSC instead of CSC_ so that the phones don't lose any data)
And after that, you should be able to flash firmware
ShaDisNX255 said:
Well, one thing you should know is that Samsung doesn't use fastboot to flash software like many other brands. It's unfortunate to say that a lot of the guides you read online are just copy-paste of guides that do use fastboot. Adb doesn't really flash software without elevated permissions afaik.
You can flash firmware using Odin for Samsung devices. There should be plenty of guides online on how to use it, your main goal right now is figuring out how to boot into download mode for Samsung.
What I would do is try to turn the phone off completely if you've been able to boot to recovery. After that, hold both the volume buttons and while you're holding them, connect your phone to a PC. This should force the phone to boot to download mode. Read the screen as it may ask you to press VOL + to proceed.
After that, you can flash the files
AP_XXXX
BL_XXXX
CP_XXXX
HOME_CSC_XXXX (Use HOME_CSC instead of CSC_ so that the phones don't lose any data)
And after that, you should be able to flash firmware
Click to expand...
Click to collapse
Thank you so much for your reply. I have spent the past few hours setting up Odin and installing the firmware.
I have run into another problem, I select all the firmware I wish to install then click start. It loads for two seconds then says "PASS!". However the phone is still stuck in a boot loop
I believe this is because I haven't turned in USB debugging, since I can't get into the phone I can't turn it on even if I want to.
Is there another option?
USB debugging isn't needed when flashing through Odin. You're most likely just missing the Samsung dev drivers. Try and installing them: https://developer.samsung.com/android-usb-driver