Hello there. I have an Elephone P9000 Lite, which required a re-flash. Fair enough. After I formatted everything then flashed the stock ROM... I tried booting it up, but the boot animation won't show up, instead, it's all just a black screen. It went on like that for 10 minutes, before I decided to stop trying. It got bricked. Now, I decided to try and flash CM13 (I found a ROM on this forum), but I can't flash it using SP Flash Tool (what I used to flash stock) because it's an .img file, so it doesn't have a scatter. I came to the conclusion that I can use:
a) Recovery, which I can't access due to the device being bricked
or
b) ADB, which requires USB debugging to be enabled, but I can't enable it due to my device being bricked.
Can anyone help me?
(I have quite some experience with flashing and stuff, but I have no idea how to flash .img using a PC without having to access the phone's OS)
Related
Hello,
Just yesterday I got my Elephone p5000
I have been setting up applications and so on. I have installed xposed and installed one hand module. It worked OK.
Later I was trying to setup google authenticator and the device just hang and rebooted.
And it went into bootloop.
I can't go to recovery mode: VolumeUP+Home+Power-> Recovery mode just starts another bootloop.
So I tried to flash an official rom from with sp flash tool SP_Flash_Tool_exe_Windows_v5.1504.00.000.
It works OK and completes with green indicator. But I still have the same bootloop.
I tried to flash custom recovery tool: TWRP_Recovery_2850_P5000 it also flashes successfully but no use of doing that. Nothing happens.
I have formatted the device along with bootloader with sp flash tool and flashed with official rom. No use.
The device goes into fastboot mode. I tried to flash TWRP recovery.img with help of fastboot but it gives an error:
FAILED (remote:
partition 'recovery' not support flash)
So far I tried all these things.
I am a newbie in flashing and using android devices. I have been using iphone so far. So sorry if I used wrong terms.
FYI:
The battery cannot be taken from the device. I am clicking on reset button on the back of device to switch it off.
Any help would be appreciated.
Thank you.
An MTK device is very hard to "brick" IF you happen to have the the firmware in SpFlashTool format - there is one on "needrom.com" and use the SpFlashTool v5.11452 or better (so far that is the latest for Octa Core 64bit). I specialises in modding MTK centric ROM , I know what I am saying. If bootloop it probably (guessing only) the TWRP version is not suitable for P5000 , there is always CWM to fall back(try searching on MIUI site).
Although I know a lot of users like to use Xposed but I never ever put any Xposed modules in my mod ROM , I want a working ROM for my users to enjoy their devices. I stayed away from Xposed bcoz I had seen some bad after effect , even after uninstalling the modules there are some stray files left behind. Good luck.
Hello!
I have a bricked phone. When I got him, he was in a state "loaded to the screensaver and stop".
I decided to flash him using recovery (carliv touch recovery 2.2). Thanks to recovery I copied all the files from phone. But all my attempts of flashing were unsuccesful - I've got the errors while recovery did an unzipping.
That because I decided to use SP FlashTool. But I've forever got the same error 5069.
I notice, that I can format my phone and download the preloader. But it's all what I can.
What I tried (what i remember):
to load without and with battery;
to put a battery after beginning of flashing;
to flash with pushed power, volume control buttons - all together and alone
to use another system, cable and computer (2 cables and computers, windows and ubuntu);
to flash different versions (from off site);
to use different versions of sp flashtool
Also I found a video, where propose to do the backup of working phone (prestigio 3400) by MTK droid tool and try to flash this.
I would be very grateful if you help me. Thanks
So, this is my problem: I was using for months now CM13 and TWRP3.0 by EdwinMoq, but the phone suddenly started to drain battery abnormally, I read CM13 was the cause so I installed TWRP 2.7.1.1 to flash Paranoid Android 4.6 BETA. When I wiped partitions to install PA (using TWRP 2.7.1.1), somehow SD Card files were deleted (I didn't select wipe SD Card at any point so I don't know what happened). Then powered off to copy the flashable *.zip again on the SD Card and when I tried to boot recovery, LG Logo appeared but after few seconds phone shutted down (and this happens everytime).
It is a p768 with unlocked bootloader. I can use fastboot just fine, delete partitions, flash them, but I obviously can't flash a system.img via fastboot (it's too big). And I tried flashing different recovery files (TWRP, CWM) and it's exactly the same. I can boot into "S/W Upgrade Mode" too, but when I try to flash any kdz it gets stuck at 15% saying phone is not connected. I tried using another USB port and making Windows install drivers for the device again with no luck.
Drivers are installed correctly (4.0.4 version) and I see phone in the Modems, Ports and USB controllers sections of Device Manager everytime so I don't know what to do. Fastboot is the only thing that's working and I know /system is missing but I can't flash anything.
My issue is kind of like this one BUT, I can boot into S/W Upgrade.
Nevermind, after some quiet crying over the phone I found that my buttons are screwed. I wasn't pressing VolUp right, tricky button. I feel like a retard.
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.
ok hear me out, I'm a newbie, and I missed up, plz help
I was trying to root my device following this tutorial, I flashed twrp and vbmeta and every thing went alright without errors, I booted the phone into recovery to continue as how the tutorial said, but it gave me the orange state error and it restarted into system but now the device is factory reset, I enabled usb debugging and went on to follow this tutorial, every thing went same as before and I couldn't boot into recovery, so I decided to flash the "orange_state_disabler_MTK Only.zip" with adb and every thing went downhill from there, It won't boot to recovery, bootloader nor system, It just stays at a blank screen after the logo and the orange state message, It is recognized by adb as "recovery" and I can do adb commands but I can't boot to bootloader to flash the stock firmware, I found this thread and tried using the tool mentioned there, Faced an error, solved it and the phone still won't boot to any thing.
so, is there any way I can get out of this situation ?
TLDR / what you should know/ idk ¯\_(ツ)_/¯
- did something wasn't supposed to do
- can't boot to recovery
- can't boot to bootloader
- device recognized by adb but can't do fastboot commands
- device is recognized by MTKAuthBypassToolV25
- can't shutdown nor restart using phone physical buttons
- don't know if the below screenshots would help with any thing, but here goes nothing
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
aIecxs said:
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
Click to expand...
Click to collapse
please explain, I don't know what IK is, and if I could flash things with SP flash tools, wouldn't I be able to flash stock firmware?
lk - little kernel. that is the partition where fastboot lives (and was modified by Orange State Disabler).
you need partition image from stock ROM and any flash tool to restore its original state.
i can't do that because i can't boot to bootloader
you don't need bootloader, only preloader or bootrom
ok turns out ima an idiot and misunderstood the entire situation , this is my first dealing with an mtk device so i thought sp flash tool is like odin and you need to be in download mode to flash things so i panicked, and didn't read well how to use the tool.
flashed stock firmware and the phone is up and running again
thanks for your help man really appreciate it and sorry for wasting your time