Phone bricked after CM 14.1 update - cant access fastboot - Xiaomi Redmi 3 Questions & Answers

Hi,
i woke up this morning and the CM updater offered me to update for CM 14.1, i thougt welll, why not. mistake :crying:
Now the phone is stuck on the flashing CM logo,
if i try to go to fastboot, than i see the fastboot screen and than black screen and the phone goes back to the flashing CM logo.
Any thoughts?

guytsur7 said:
Hi,
i woke up this morning and the CM updater offered me to update for CM 14.1, i thougt welll, why not. mistake :crying:
Now the phone is stuck on the flashing CM logo,
if i try to go to fastboot, than i see the fastboot screen and than black screen and the phone goes back to the flashing CM logo.
Any thoughts?
Click to expand...
Click to collapse
do u have access to recovery?? if u have, then u can just flash previous build without wiping data..

Think if you press vol+ vol- and power and then use the button combo to boot into TWRP you will be fine, takes abit of messing to get it right.

http://en.miui.com/thread-277276-1-1.html
TRY THIS

saikatmitra71 said:
do u have access to recovery?? if u have, then u can just flash previous build without wiping data..
Click to expand...
Click to collapse
Did you try this solution? Did it work? Did you lose your apps/data?

Solved
Eventually managed to get onto twrp using adb (it was a bit of a statistical process... Didn't always work)
From there I just flashed cm 14.1 again, and it looks OK now
Thanks you all for the help!

Like I said earlier failed flash by CMxx doesn't overwrite TWRP, you can boot back into recovery just have to try a few times. Happened to me pressing both volume buttons and power switched phone off then I used button combo and it booted into TWRP.

Might have to grab a usb cable and use ADB to boot into fastboot. It happened to me and that was the only way for me.

seos83 said:
Might have to grab a usb cable and use ADB to boot into fastboot. It happened to me and that was the only way for me.
Click to expand...
Click to collapse
Don't worry Follow This one No fastboot, no edl, no test point, best way to Recover Xiaomi Device, prepare by me and 100% working {tested}

Related

[Q] Xperia P stuck on boot

Hi,
Hope someone can help. I've tried to install a custom ROM today and I'm afraid I managed to brick my phone (Xperia P). Here is what i did:
I started out according to the Starters guide:
-Rooted phone
-Installed CWM
-Made a backup
-Unlocked Bootloader
-Installed JB Moonbreaker 3.5: at this point I was actually still following the starters guide, as in: wiping cache, wiping data,wiping dalvik cache and then installing from zip.
-The phone is currently stuck on the loading screen that comes after "Sony" and "Xperia" (the colorful swirling thingie)
-I can only shut it down by pressing and holding the power and volume up keys until it vibrates 3 times in a row.
-Starting with pressing volume down key repeatedly will not bring up CWM (also gets stuck on the same screen).
-Will also not fastboot anymore properly. (waiting for device for "fastboot.exe -i 0x0fce getvar version"; LED on device will not even light up as blue, goes to green instantly)
-In Device Manager I can see it as "Android" with a yellow exclamation mark.
-Sony PC Companion gives me the "My Sony Xperia P LT22 is connected" popup every 15 seconds but will actually not show the device as connected
I'm wondering if I can flash a stock rom on it to recover it or if there is anything else that can be done.
Thanks in advance
huvikman said:
Hi,
Hope someone can help. I've tried to install a custom ROM today and I'm afraid I managed to brick my phone (Xperia P). Here is what i did:
I started out according to the Starters guide:
-Rooted phone
-Installed CWM
-Made a backup
-Unlocked Bootloader
-Installed JB Moonbreaker 3.5: at this point I was actually still following the starters guide, as in: wiping cache, wiping data,wiping dalvik cache and then installing from zip.
-The phone is currently stuck on the loading screen that comes after "Sony" and "Xperia" (the colorful swirling thingie)
-I can only shut it down by pressing and holding the power and volume up keys until it vibrates 3 times in a row.
-Starting with pressing volume down key repeatedly will not bring up CWM (also gets stuck on the same screen).
-Will also not fastboot anymore properly. (waiting for device for "fastboot.exe -i 0x0fce getvar version"; LED on device will not even light up as blue, goes to green instantly)
-In Device Manager I can see it as "Android" with a yellow exclamation mark.
-Sony PC Companion gives me the "My Sony Xperia P LT22 is connected" popup every 15 seconds but will actually not show the device as connected
I'm wondering if I can flash a stock rom on it to recover it or if there is anything else that can be done.
Thanks in advance
Click to expand...
Click to collapse
Keep the stock fw ready to be flashed using flashtool, enter into flashmode and flash it !
Sent from my Xperia U using xda app-developers app
Can't seem to get it flashed from flashtool. I'm pressing the back button and connecting the USB and I'M just getting the same stuff on the phone, while flashtool is waiting for the phone.
I did manage to enter fastboot again though. Should I be flashing CWM from here (since I can't enter it). Or kernel then rom? I'm a bit lost.
huvikman said:
Can't seem to get it flashed from flashtool. I'm pressing the back button and connecting the USB and I'M just getting the same stuff on the phone, while flashtool is waiting for the phone.
I did manage to enter fastboot again though. Should I be flashing CWM from here (since I can't enter it). Or kernel then rom? I'm a bit lost.
Click to expand...
Click to collapse
Its volume down key and Plug in USB, to enter flashmode
Not back button.
Or flash a kernel by fastboot mode, enter CWM and install the ROM (assuming you have the zip file in the SD card )
Sent from my Xperia U using xda app-developers app
No luck. I get a green LED and nothing happens. If I hold down volume down for really-really long then I'm back to the same boot animation.
huvikman said:
No luck. I get a green LED and nothing happens. If I hold down volume down for really-really long then I'm back to the same boot animation.
Click to expand...
Click to collapse
yes green LED it is,
i hope you had the flashing process ready at the PC right ?
First make sure your phone is shut down. long press power+vol up until you feel 3 vibrations.
From there you can try fastboot mode or flash mode.
Utensils vioment
Alright done all that, still is the same. I've started to play with other USB ports and I noticed that when I get connected it tries installing the SEMC Flash device driver. It fails with "device unplugged" message exactly at the same time when when the Sony logo appears. Then it tries installing MTU USB Device as well. Reinstalled flashtool drivers and tried in different ports. It seems as if the phone is not staying in flashmode?
huvikman said:
Alright done all that, still is the same. I've started to play with other USB ports and I noticed that when I get connected it tries installing the SEMC Flash device driver. It fails with "device unplugged" message exactly at the same time when when the Sony logo appears. Then it tries installing MTU USB Device as well. Reinstalled flashtool drivers and tried in different ports. It seems as if the phone is not staying in flashmode?
Click to expand...
Click to collapse
I recall I had that issue with wundows 7 at the beginning, what I did then was to boot my windows xp and managed to flash from there.
I have tried many things since, and if I am not mistaken it's installing flahtool drivers that fixed it finally.
I think there are 3 drivers there you need to install.
nifileb Naval
you can use emma flash tool by sony to flash your device once u get into flashboot mode(vol down den insert usb cable)
you will find it at sony developer site
did you tried to flash the rom over ICS, if yes then thats why your p got stuck at boot, coz i too got the same prob, when i tried to flash the JB moonbreaker over ICS, so what i did was pressed the power button and volume up button till 3 vibration, start flashtool and flash stock ICS firmware, but don't uncheck wipe data, otherwise you will get bootloop, after flashing is complete, now download and flash stock JB firmware, root your phone using doomlord's easy root kit or any other way you know, install cwm and now reboot into cwm flash JB stock or custom kernel and then the rom, thats it, just let me know if the prob is solved, thanks
garvitdelhi said:
you can use emma flash tool by sony to flash your device once u get into flashboot mode(vol down den insert usb cable)
you will find it at sony developer site
Click to expand...
Click to collapse
Managed to get the phone back to working with this, thanks! Now just a couple of questions left . Do I have to reroot and reinstall CWM after this? I guess BL is still unlocked right?
maknom66 said:
did you tried to flash the rom over ICS, if yes then thats why your p got stuck at boot, coz i too got the same prob, when i tried to flash the JB moonbreaker over ICS, so what i did was pressed the power button and volume up button till 3 vibration, start flashtool and flash stock ICS firmware, but don't uncheck wipe data, otherwise you will get bootloop, after flashing is complete, now download and flash stock JB firmware, root your phone using doomlord's easy root kit or any other way you know, install cwm and now reboot into cwm flash JB stock or custom kernel and then the rom, thats it, just let me know if the prob is solved, thanks
Click to expand...
Click to collapse
It was on JB stock. I'll check if I cano boot to CWM now or have to redo all that stuff and then try flashing Phantom Kernel and then Moonbreak. Will let you know
xperia p
huvikman said:
Managed to get the phone back to working with this, thanks! Now just a couple of questions left . Do I have to reroot and reinstall CWM after this? I guess BL is still unlocked right?
Click to expand...
Click to collapse
yup bl will always be unlocked regfardless of what rom you flash unless you relock it
yup if you have to install cwm again then if you want it and you have to first root it again as well
------------------------------------------------------------
Xperia P PAC rom jb 4.2.2 user
hit thanks if i helped
Thanks everyone for the input, issue resolved, kernel and rom flash was successful.
Stuck on boot
Guys I have the same problem.
I wasn't satisfied with the rom I put on my phone so I went on to put another one on it.
Flashed the kernel with fastboot, went into cwm, deleted system, cache etc. and went on to flash the rom, but there was no rom zip there, and I was sure I had put it. It was probably an error during the copy procces and it just stopped, I assumed it copied.
Well, now it is just stuck on the boot screen. I can get into fastboot and cwm, but I have nothing to flash.
I tried using the Sony recovery "Emma" but it just stays blank when I connect the phone..
Is there something else I can do?
rocker55555 said:
Guys I have the same problem.
I wasn't satisfied with the rom I put on my phone so I went on to put another one on it.
Flashed the kernel with fastboot, went into cwm, deleted system, cache etc. and went on to flash the rom, but there was no rom zip there, and I was sure I had put it. It was probably an error during the copy procces and it just stopped, I assumed it copied.
Well, now it is just stuck on the boot screen. I can get into fastboot and cwm, but I have nothing to flash.
I tried using the Sony recovery "Emma" but it just stays blank when I connect the phone..
Is there something else I can do?
Click to expand...
Click to collapse
The rom probably won't work if you delete /system so reflash stock JB first maybe this will help: http://forum.xda-developers.com/showthread.php?t=1849170
Facing exact same issue i think
garvitdelhi said:
you can use emma flash tool by sony to flash your device once u get into flashboot mode(vol down den insert usb cable)
you will find it at sony developer site
Click to expand...
Click to collapse
Hi
I think im facing a very similar issue, i m very new to this and therefore didnt understand the solution. I did visit the developer site for emma, but can you tell me the exact thing to do after starting Emma. I mean, when do i connect the phone and how, what commands to give. Below is explanation of how i got into this and what all ive tried.
OK i ve been trying to flash a new custom rom on my Xperia P, i looked at a number of guidelines and doing things step by step.
Since im very new to this i downloaded a few Roms. I was following the guide "http://droidors.com/2014/07/08/update-xperia-p-lt22i-to-android-4-4-4-kitkat-with-slimkat-custom-rom/2/" and everything was going fine. I reached the step to "fastboot flash boot boot.img", i did that and then went on the next step to boot in CWM Recovery and install the zip rom and the Gapps. During the Zip Rom install i got status 7 error.
Now, i noticed that i might have flashed the wrong Rom so rechecked the guide and installed the correct Rom which is mentioned in "http://forum.xda-developers.com/xperia-u/p-development/rom-slimkat-4-4-2-release-candidate-t2657795" . But now THE PROBLEM IS, AFTER I FLASHED THE INCORRECT IMG, MY PC IS NOT RECOGNISING THE XPERIA P SAYING IT DOESNOT RECOGNISE THE DRIVERS, therefore im not able to copy the ROM Zip on the SDcard, to then run it from CWM.
After sometime i tried the below
Ok, now i tried to flash the stock Rom through this link "http://forum.xda-developers.com/xperia-u/p-development/ftf-firmware-xperia-p-generic-world-t2322163", through flashtool to bring my phone back to life. I installed the drivers as per instructions from drivers folder, but for some reason the pc is just not accepting. I did install through this exact method yesterday night and it worked perfectly.
Please suggest. I hope im asking at the right place.
Urgent help please
I forgot to mention, after I flashed the SlimKat Rom, and things went out of hand ( till this point i could see Slimkat logo at boot and could also go in CWM Recovery ), I tried to restore through Nandroid Backup i had done. As soon i selected the restore option and then the backup file, within 2-3 seconds the phone went off, and then on boot all i can do is see "SONY" on screen. Nothing else happens.
I ve tried all this on a different machine, with different wires and different USB port, no luck
Kindly advise, im stuck with no spare phone.
Solved i guess
OK Brother,
I downloaded EMMA and am currently downloading the service. It is very self explanatory. What was amazing is when i recognised my phone "What a sight "
Flashtools wasnt able to do that, so i guess the manufacture tools are damn important ( i wasnt exactly of the opinion before )
Also it is downloading Android 4.0.4 Build 6.1.1.b.1.54, which first came on the device, which also makes me think may be i should have tried that rather than trying to flash with the JB Rom all this while.
Man, i was scared. Thanks for this thread Bro.
God Bless
Will inform once the phone is booted up to confirm it worked.
Emma Worked
OK guys, I can confirm its EMMA "Flash tool for Xperia" fixed the problem for me. It installed 4.0.4 on it.
Also there is a pdf in the Download which guides about the usage.
Sigh
Correction- it installed the latest stock ROM jb

[Q] I-9300 bootloop and no recovery

Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..

boot loop flare s play

anyone can help me? I've tried to root my cherry mobile flare s play, I've flash twrp on it but it always boot in recovery it doesn't boot in system partition so I tried wiping the cache and dalvik cache, still doesn't boot so I tried flashing another recovery/rom and it just get worst it's now stuck in boot loop I've already tried the abd reboot-bootloader and always fall in error: device not found., I hope someone notice my case. thanks
Hello, this happens when the system is actually corrupted
you may reflash stock then twrp then root again
or just get a custom recovery for your device
you must go in bootloader for stock rom or twrp for custom rom, and that's fine your phone just needs a rom and its good to go
good luck
TheShadowMC said:
Hello, this happens when the system is actually corrupted
you may reflash stock then twrp then root again
or just get a custom recovery for your device
you must go in bootloader for stock rom or twrp for custom rom, and that's fine your phone just needs a rom and its good to go
good luck
Click to expand...
Click to collapse
but how can I boot it on bootloader? key combinations like vol+ and power or any combo doesn't work, only if someone can teach me how to boot it on bootloader or fastboot then there would be no problem for me, I don't know what to do now
Hello again, take out the bettery then put it back and use the bootloader combo
if it didnt work take out the bettery and flash through sp flash tool
nothing to worry about, i didnt notice that your phone can be flashed through sp flash, since it just requires the phone to be off
not really such a scary situation
TheShadowMC said:
Hello again, take out the bettery then put it back and use the bootloader combo
if it didnt work take out the bettery and flash through sp flash tool
nothing to worry about, i didnt notice that your phone can be flashed through sp flash, since it just requires the phone to be off
not really such a scary situation
Click to expand...
Click to collapse
will it work even if my device don't have battery on it?
kiltot24 said:
will it work even if my device don't have battery on it?
Click to expand...
Click to collapse
sp flash for my knowledge would work even when the battery is out it doesnt matter, just load the scatter press download button and connect the phone with battery off
good luck again:highfive:
-Hope- said:
sp flash for my knowledge would work even when the battery is out it doesnt matter, just load the scatter press download button and connect the phone with battery off
good luck again:highfive:
Click to expand...
Click to collapse
in my case I can't flash even a recovery image using sp flash tool. any help? sorry if I look like an ignorant any way thanks for your help guys, I really appreciate
no no problem, however what's the problem ?
I'm trying to flash a custom recovery on it but it doesn't work, I'm trying to flash twrp, the one I've flash before, because I don't have the stock rom of my device so I'm doing the process partially. I'm aiming to flash twrp and then restore my saved back up.
Hello,
i think your device stock frimware is there on google, however when you try to flash what error does it give or what happens ?
It doesn't show any error message and not showing any progress at all. my device just blink showing that the battery is charging though the battery is not present.
if it didnt detect it try pressing the volume up or volume down to make sure while connected ( and download button is pressed
just blink until it reaches time out.
I'm sure that my cable is working, it works on other device. I already install all the drivers I need.
is there a way to stop my device from simultaneous booting? it appears to be detected on device manager but just for a few sec, then reboot and appear again.
ensure the ROM is loaded properly in the flash tool.
Switch off the phone and remove battery.
press the start button in the flash tool to initiate the ROM flashing process. The process will be in hold, waiting for the phone to accept the new firmware.
Now connect the phone to computer.
Try these. Press and hold VOLUME DOWN OR VOLUME UP OR POWER+VOLUME UP OR POWER+VOLUME DOWN. One of these should work and the flashing process should start.
can I obtain the stock rom from the same device? I have the same model and it works properly. I can't download the stock rom from mediafire it always fail due to poor internet connection so I'm looking for another way.
I tried updating my driver then my device was recognized but when I flash the recovery image it displays 100% but in red color.
kiltot24 said:
I tried updating my driver then my device was recognized but when I flash the recovery image it displays 100% but in red color.
Click to expand...
Click to collapse
are you using the latest sp flash tool ?
yes thanks my device works fine now thank you for your help, the only problem now is how will I restore my device imei, it can be changed in engineer mode using at+ command but it be deleted again once conduct a factory reset in short it just set a temporary imei for my device, is there a way to change my device imei permanently?

OnePlus X soft brick. All I can access is fastboot mode.

Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide

Phone bricked after wiping twrp

(this all happend 3 years ago and im asking now as i need a backup phone )
i flashed twrp and pixel experience well dum me clicked reset in pixel experience settings then it bootlooped into twrp for eternity now dum 2019 me thought that wiping twrp from fastboot would force it to boot into the system well it didnt work and even now whatever i try it does not boot (it just vibrates but will not boot i tried all combinations possible and also tried the miraclebox guide which didnt work)
Zainullahk1234 said:
(this all happend 3 years ago and im asking now as i need a backup phone )
i flashed twrp and pixel experience well dum me clicked reset in pixel experience settings then it bootlooped into twrp for eternity now dum 2019 me thought that wiping twrp from fastboot would force it to boot into the system well it didnt work and even now whatever i try it does not boot (it just vibrates but will not boot i tried all combinations possible and also tried the miraclebox guide which didnt work)
Click to expand...
Click to collapse
Try first charging the battery and installing the stock ROM (the latest) through SP Flash tool.
SubwayChamp said:
Try first charging the battery and installing the stock ROM (the latest) through SP Flash tool.
Click to expand...
Click to collapse
ill try that but i dont expect it to work due to it not booting
Zainullahk1234 said:
ill try that but i dont expect it to work due to it not booting
Click to expand...
Click to collapse
Well, this is the whole idea to flash a stock ROM, if it is an issue at software level it has to solve it. Check carefully some things that could help to diagnose the brick level, like device is vibrating, device can boot till bootanimation, logo is showing some letters and so on.
SubwayChamp said:
Well, this is the whole idea to flash a stock ROM, if it is an issue at software level it has to solve it. Check carefully some things that could help to diagnose the brick level, like device is vibrating, device can boot till bootanimation, logo is showing some letters and so on.
Click to expand...
Click to collapse
it wont do anything but vibrate when i hit the power button
Zainullahk1234 said:
it wont do anything but vibrate when i hit the power button
Click to expand...
Click to collapse
Try flashing the firmware and see what happens, and if, which modes are available for you, fastboot, recovery.

Categories

Resources