Hello guys,
I own a Allview X4 Soul Pro Xtreme, i think is a copy of GIonee A1. Yesterday, i flashed twrp, but i think i did flashed a wrong version, and custom recovery is gone, aswell as stock recovery. The phone was unrooted, but bootloader is unlocked, and everytime i open up the phone, it's just shows me an message: " Orange state, your cevice has been unlocked and can't be truster, your device will boot in 5 seconds". It just keep rebooting, without let me go into download mode, or even recovery mode with the keys pressed + power button. At this point, i can't even use adb fastboot because whenever i connect the usb to my laptop, it just shows me the message with orange state, and keep rebooting. I was thinking to use sp flash, but i can't find a room for sp flash. The phone is using Mediatek 6757 Helio p25 platform.
Is there any way i can fix it? Or i just have to buy a new one? Because i bought the phone 15 days ago...
Thank you!
Related
Hi guys
I tried to install a custom ROM on my huawei ascend g610-u20 android 4.2.2 with mobileuncle tool
my phone was rooted but I forgot to unlock bootloader, anyway after rebooting phone with mobile uncle tool(and selecting recovery.img (CWM method)) it's gone in to a crazy state!!
I searched internet and I figured out that it's huawei boot loop :|, I downloaded the official ROM from huawei website and tried To flash it,
I get error 2004 ( I've installed Meditak Vcom and my device usb driver)
when I turn on my phone with battery it reboots every 5 second , so windows and sp flash tools can't recognize it.
I tried to flash it without battery,when I pressed volume down phone turned on by vibration and after a while it turned of by vibration again!
I can't access to bootloader menu when I press " volume up +volume down + power button" nothing happens! it just turns on phone!( and crazy loop boot circle happens again!)
I'm using windows 8.1 last update , every thing is Ok and my cable is Ok my sd card is Ok and I've downloaded Right ROM for my device(MT6589) and also I'm using sp flash tool last version!
**** I've got access to fast boot mode ****
My main problem is with Error 2004! help me out PLZ!
I couldn't put any screen shot cuz I'm a new user, Sry!
any idea?
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
I'm in the same situation with a BQ X5 plus, I think the only way is to get the phone to the BQ service center
Did you get the phone working again ?
Nope i handed it over to the support and got a New one because guarentee was still valid
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
yes you have to install qualcomm drivers and see in what mode the phone are.
9006, 900E or 9008
solved
I HAD the same problem with my BQ Aquaris X Pro.
Running the lineage OS 15.1, rooted with AddonSu installed.
This is how I was able to wake it up again.
1) I unplugged the phone from the USB loading cable
(don't know if this step is needed - the battery was definitely not totally empty, when this red flashing LED thing occurred. However, i don't think the phone charges when the LED red light flashes.).
2) I took the sim card out (don't know if this step is needed).
3) I pressed for about 2 [minute] power and volume (don't know if up or down) button together. And then it woke up again.
Maybe this is the special boot recovery mode option mentioned here?
What ever it is, it worked for me.
+ https : / / wiki.lineageos.org/devices/bardockpro
Good luck!
ElmBeech
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
Hello,
I've got a Wiko Jerry 2.
Wanted to root the device because the apps it comes with used up more then half the space.
So, Had some experience with Flashing, ADB and Fastboot with a other device.
Searched a tutorial and followed it.
Unlocked the bootloader, flashed and restarted the device.
It rebooted and showed the Android logo and Wiko logo, with orange code: warning your boot is unlocked and can't be trusted, reboot in 5 seconds. (It didn't reboot)
It stayed in this boot, removed the battery and went back into fastboot to flash the factory rom back.
After flashing the stock rom it ended in a bootloop with the same logo's and code orange.
Meaning it went wrong again. The problem I'm facing now is that I can't get the device in fastboot. not even with ADB.
ADB doesnt recognize the phone.
EDIT: The phone is showing in device manager. But it's refreshing the device manager every 2 seconds meaning the device is getting connected/disconnected every 2 seconds.
A bit lost here, someone got some ideas to try?
Thanks in advance,
Floeske.
recovery custom rom from wiko site official
Floeske said:
Hello,
I've got a Wiko Jerry 2.
Wanted to root the device because the apps it comes with used up more then half the space.
So, Had some experience with Flashing, ADB and Fastboot with a other device.
Searched a tutorial and followed it.
Unlocked the bootloader, flashed and restarted the device.
It rebooted and showed the Android logo and Wiko logo, with orange code: warning your boot is unlocked and can't be trusted, reboot in 5 seconds. (It didn't reboot)
It stayed in this boot, removed the battery and went back into fastboot to flash the factory rom back.
After flashing the stock rom it ended in a bootloop with the same logo's and code orange.
Meaning it went wrong again. The problem I'm facing now is that I can't get the device in fastboot. not even with ADB.
ADB doesnt recognize the phone.
EDIT: The phone is showing in device manager. But it's refreshing the device manager every 2 seconds meaning the device is getting connected/disconnected every 2 seconds.
A bit lost here, someone got some ideas to try?
Thanks in advance,
Floeske.
Click to expand...
Click to collapse
if your phone brick at restart try to download wiko Jerry 2 recovery custom rom you can find in the wiko official site web i resolve it but i have a problem twrp recovery touch dont respond
Hello everyone!
I bought a Meizu Pro 7 recently and unfortunately I happen to have bricked it.
When I received the phone, it was using the 6.3.0.0A firmware (so it was Chinese) and I wanted to change it to 6.3.0.0G.
I followed a tutorial on chinahandys.net in order to do it, and it worked! (I cannot post the link since I am a new user on xda but it is called "Install Global ROM on chinese Meizu Pro 7")
But now I turned it off, and now when I try to turn it on, the Flyme logo shows up and it keeps loading for forever.
I tried accessing recovery mode by pressing volume down + power and this is what I get (this is the same screen that shows up when you boot the phone normally, but at the bottom of the screen it is written "=> Fastboot mode(sec,lock,rooted)"):
up.kuraip.net/0515P8dy3984.jpg
Do you have any idea how I could fix this issue, I just bought the phone and I don't really know what to do to fix it :'(
Kuraip said:
Hello everyone!
I bought a Meizu Pro 7 recently and unfortunately I happen to have bricked it.
When I received the phone, it was using the 6.3.0.0A firmware (so it was Chinese) and I wanted to change it to 6.3.0.0G.
I followed a tutorial on chinahandys.net in order to do it, and it worked! (I cannot post the link since I am a new user on xda but it is called "Install Global ROM on chinese Meizu Pro 7")
But now I turned it off, and now when I try to turn it on, the Flyme logo shows up and it keeps loading for forever.
I tried accessing recovery mode by pressing volume down + power and this is what I get (this is the same screen that shows up when you boot the phone normally, but at the bottom of the screen it is written "=> Fastboot mode(sec,lock,rooted)"):
up.kuraip.net/0515P8dy3984.jpg
Do you have any idea how I could fix this issue, I just bought the phone and I don't really know what to do to fix it :'(
Click to expand...
Click to collapse
Did you join the Flyme Forum? there is a lot of information there on problems flashing the Pro7. There are different model numbers. My Pro7 has the H version with the latest G version rom. I think that there is an A version Pro7 which is for the Chinese market and there is a specific G rom for that phone.
Kuraip said:
Hello everyone!
I bought a Meizu Pro 7 recently and unfortunately I happen to have bricked it.
When I received the phone, it was using the 6.3.0.0A firmware (so it was Chinese) and I wanted to change it to 6.3.0.0G.
I followed a tutorial on chinahandys.net in order to do it, and it worked! (I cannot post the link since I am a new user on xda but it is called "Install Global ROM on chinese Meizu Pro 7")
But now I turned it off, and now when I try to turn it on, the Flyme logo shows up and it keeps loading for forever.
I tried accessing recovery mode by pressing volume down + power and this is what I get (this is the same screen that shows up when you boot the phone normally, but at the bottom of the screen it is written "=> Fastboot mode(sec,lock,rooted)"):
up.kuraip.net/0515P8dy3984.jpg
Do you have any idea how I could fix this issue, I just bought the phone and I don't really know what to do to fix it :'(
Click to expand...
Click to collapse
Hold Volume Up + Power to get into recovery mode, Volume Down + Power = Fastboot Mode