Related
THIS IS A SPRINT INTERCEPT!!!!
So I loaded UB droid onto my intercept now for whatever reason it decided to load stock recovery and hang at UB load screen. Now the phone wont boot to android and is stuck and bootloops. Heres what i have at my disposal.....
1. A copy of SW Update, but its the copy for the moment......I tried to connect to my intercept but it searches and cant find it.
2. The ability to get to stock recovery and download mode.....So its a soft brick if i had a signed update pack that worked i could load that over it. or a way to turn of the check for signed zips? I tried loading the update.zip file that they gave us when the first one bricked our phones but it didnt work said (status 7)????
3. A computer with ADB fully loaded...if i need to i can use that to help unbrick the phone.
4. I also have the following files DLO5 completely stock.zip (unsigned), UB4, the update.zip file for the intercept (signed), the mr which is in a tar.md5 file.
Heres what ive tried....
1. Using SWupdate to load the ship MR:
Problem with this method is that the SWupdate cant find my phone..and the intercept is coming up as a unknown device.
2. Loading a stock update.zip file... Comes back with installation aborted....see above.
Any suggestions?
http://intercept-root.googlecode.com/files/interceptRoot.apk this is how i did it over the phone to a friend i had him download and install the intercept root and cmwflsher then install the almost stock rom" then just wipe davic and install ud6 then the super kernal package it works well and has support for teathering ! should be set!
unlocked bootloader att. atrix. honeycomb rom. faux oc kernal
The same thing happened to me, and this was the perfect solution. Just download the almost stock, apply it in CM01, then after that wipe EVERYTHING!!
But unless you can charge your phone every couple hours, i wouldnt suggest UB6. It destroyed my battery life... I redid that almost stock and my phone hasnt needed to be charged for almost 2 days... UB6 is a battery raper, but its a sweet ROM
I ended up getting in download and flashed a stock image from there I rooted it loaded recovery etc.
Sent from my MB855
i screwed my phone too cuz im a noob ofcourse. i tried rooting my phone using inxane0381intercept.tar with SWUpgrade and then i put a custom recovery on it, and it wont boot
i can get into the custom recovery and the SWU download mode.
please help me
its all good if no one feels like helpin, i shoulda never messed around
Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2471370
The program get's stuck at analyzing device and doesn't flash or download anything. It would be nice if I can perform at least a factory reset in case something wants to blow up in my face. If anyone has some ideas (ridiculous or not), feel free to let me know.
slicknessessity said:
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
Click to expand...
Click to collapse
Hey man you could try just using Flashify to flash a recovery...its a app...then boot to recovery
I tried using that method. It gives me the same thing. Maybe somewhere in the recovery location (or associated locations) seem to may have gotten damaged somehow during the bad flash? Flashing the phone completely I'm sure would do the trick. I came from the droid 4, so sbf/fastboot flash would solve all my problems. Searching around landed me to a kdz, which seemed to be an equivalent, but isn't working or maybe I'm doing something wrong? Any advice on this would be greatly appreciated.
I went and did a full flash using this method: http://forum.xda-developers.com/showthread.php?t=2448960. Since I couldn't find a recovery fix per se, I decided to flash the whole thing and start fresh (oh well).
It downgraded to 11A in the process, so the same can probably be said for 10B for compatible custom builds.
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Get a new phone. Unfortunately I think it's some hardware that is broken. But in case it's not try to flash b05 instead?
I don't see anything else you could do since adb doesn't seems to work. I'd just RMA it with the warranty still being in effect. And if it was purchased trough amazon you'll probably just get a new one ! (that's what happened to me last time).
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Choose an username... said:
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I think something is wrong with the hardware. I had a similar problem as u with my last phone a honor 8, it frozed up and it was nothing I couldnt do other than go back to the store with it. I got a new one.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
I was gonna suggest that, but a read-only SD card wouldn't provoke that. I had one that got read-only after using it as swap for a long time, and you would only notice in twrp (booted in ~2 minutes). If he was able to try to install a system update through the recovery, he was able to write to the SD card --> it's not dead
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
It lags the same. Regardless a sd card is inserted or not.
Choose an username... said:
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Click to expand...
Click to collapse
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
nsabir said:
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
Click to expand...
Click to collapse
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
jw1985 said:
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
Click to expand...
Click to collapse
The problem is axon 7 is not available in our country. If he has to rma it then he has to send it to a relative in Sweden. Then the relative can do that for him. That's why he asked me to do what i can to revive the phone. RMA is the last resort for him.
Now, i guess i will give up and tell him i did everything i could.
Anyways, thank you all for helping.
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
can you at least get the phone to fastboot mode?
microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.
Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help
same problem. after twrp flash x626 not boot