Hello all,
I recently picked up a ulefone armor 2s and was attempting to root it and ended up bricking my device... i followed a guide for flashing the 2 variant not the 2s. I found a stock rom and ended up flashing it and got the device back to working status. I do want to root my device with twrp but i am unable to flash it because there is no bootloader on the device at the moment.
Powering up the device i get a message that says device is in a red state i am not sure what that means. I have found a copy of trwp that is corresponds to my chipset and kernel and want to flash it. Attempting to enter download mode or recovery just gets me to a black screen.
I have tried to flash the device using adb, adb doesn't detect my device. I have all the proper drivers, usb debugging is enabled and is oem unlocking.
Cpu-z says that i have an unknown bootloader and when i try to access it nothing happens
Is there a way to put a bootloader on it?
Thanks
-Malice
Related
I'm new to rooting and all of this type of thing, i figured I would first start with my HTC Flyer. I successfully unlocked the bootloader, and installed SuperUser, upon installing greenify and i tried to install the Xposed Framework, and my device now is stuck in a boot loop.
When enter the bootloader and do a factory reset or try to enter factory it completely freezes, and when i try to connect it to my PC via fastboot the PC says that the USB device that is connected cannot be recognized and fastboot will not work. Did i completely fry this device? Also if you have time I couldnt figure out a proper way to flash a custom rom so if anyone has a guide for that I would appreciate a link to that as well.
Thank you so much!!
I used SP Flash Tool to update the ROM of my Umi Iron (deselected preloader, as advised), it stopped at 18%, gave an error and since then, my phone is in a bootloop. Can only get to stock Recovery (the android on its back). After a while in recovery, the phone reboots automatically, showing the Umi symbol for a few seconds, rebooting again back to recovery...
Fastboot and adb don't seem to find the device in this state. Installed the MT65x3 USB VCOM drivers, anything else I need?
Anyway to enter the bootloader or use adb/fastboot in any way? Sure hope I'm not completely screwed...
I was trying to flash modified recovery image using magisk after that my phone is dead almost.
My phone don't boot in to android. I can't charge my phone because I get message on the beginning
my system is moddifyed my phone shut down automatically after 5 seconds, also i can't unlock bootloader via fastboot i get information "unlock operation is not allowed" .
I have Leeco 650x with mtk helio x27.
I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
Is here any powerful person to solve the problem.
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
I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com