Hello,
Yesterday I downloaded the beta of marshmallows for my honor 7 European version PLK-L01. But, foolishly, I started the phone while pressing the volume up and volume down power button (download mode ??) and, once finished the update, the phone went bootloop, rebooting. Then I tried to do a reset from recovery and install the rom stock (b100), but without success as the phone continued to go bootloop. So this morning I decided to unlock the bootloader and let the phone into fastboot mode; then with Huawei extractor tool, I extracted the various image file from stock rom to flash them via fastboot and the program Minimal fastboot to ADB. I flashed the various image files (system, boot, recovery, etc.) but only the three image files listed first and with another 2-3, the process has been successful. So I restarted the phone and it worked. But there a problem, in fact, before starting the system the phone will restart 4-5 times; also no longer recognizes the boot-sim and gives me the error that the program system stopped working. Can someone help me ??? I'd be eternally grateful
Matthew
Related
Hi, I'm not experienced with custom roms, so I bricked my phone trying to install cyanogenmod, please help me
I tried to install custom rom on my xperia p so I unlocked bootloader, rooted and got recovery. Everything seemed to be fine until i tried to flash cyanogenmod, I can't provide link because I'm new user. Using Flashtool I accidentally (not knowing exactly what I'm doing) chose "select system to Flash" and klicked on boot.img from this pack. After several minutes without respond it showed only "Please check the log before rebooting into system" so I disconnected phone. When I try to start, it only shows sony logo for a short while and then it resets, and shows it again and resets... I can only reset it by holding vol+ and power button until it vibrates 3 times, then I can put it in fastboot mode.
Please tell me, what should I do now. And sorry for my bad english.
Flash stock, flash the boot.img in fastboot mode, reboot and flash the zip.
If you did not copy the zip yet boot after flash and copy.
Thank You very much. Everything works fine now, excepting data access via mobile network. I'll try to find the answer in another thread. Thanks again!
Guys I need some help here. I just flashed the 0305 build from the latest CM12 nightly. Unfortunately, after updating to this, I can no longer access the recovery. I've already tried flashing TWRP and Philz fastboot and using the m5 settings and twrp manager but I still cant access the recovery no matter how many times I press the up or down button after the purple led light.
I decided to try and do a factory reset but to no avail. After selecting erase everything, the phone just shuts down and when I restart back it does nothing. So I decided to flash back to stock via flashtool. I already installed all the drivers and Its not the first time I used this tool but I get an error that says:
ERROR - Cannot Identify your device
Tried reinstalling the drivers again but the error persists. But a menu for selecting the device manually pops up and then I manually select the Xperia Z2 D65XX option. But now when I continue to flashing the rom, once I reboot to fastboot, I'm stuck at waiting for device.
Edit 1: I tried erasing userdata and cache via fastboot now I'm on a bootloop and I get a red light before the purple light every reboot. same thing with fastboot, I get a redlight first before the blue one.
Edit 2: It seems I got a softbrick
Advali said:
Guys I need some help here. I just flashed the 0305 build from the latest CM12 nightly. Unfortunately, after updating to this, I can no longer access the recovery. I've already tried flashing TWRP and Philz fastboot and using the m5 settings and twrp manager but I still cant access the recovery no matter how many times I press the up or down button after the purple led light.
I decided to try and do a factory reset but to no avail. After selecting erase everything, the phone just shuts down and when I restart back it does nothing. So I decided to flash back to stock via flashtool. I already installed all the drivers and Its not the first time I used this tool but I get an error that says:
ERROR - Cannot Identify your device
Tried reinstalling the drivers again but the error persists. But a menu for selecting the device manually pops up and then I manually select the Xperia Z2 D65XX option. But now when I continue to flashing the rom, once I reboot to fastboot, I'm stuck at waiting for device.
Edit 1: I tried erasing userdata and cache via fastboot now I'm on a bootloop and I get a red light before the purple light every reboot. same thing with fastboot, I get a redlight first before the blue one.
Edit 2: It seems I got a softbrick
Click to expand...
Click to collapse
can you enter fastboot mode?
Yes but the device is unrecognized by flashtool
Hi all,
I have a Xiaomi Redmi 3 and I tried updating it to Android 6.0 today using a very helpful article from cyanogenmods
It was all going so well until the end when I came to flash the ROM, I downloaded the wrong one!! (I needed the ARM64).
Anyway my phone restarted and now I can't seem to rectify my mistake!
I can't access the recovery mode (Power button and volume up) It just shows me the Xiaomi sign and stays there but I can access Fastboot (Power and volume down) and it can communicate with the PC via CMD.
I'm super new to this and I've been looking online for the past 5 hours with no luck so maybe someone can help me out.
I tried fastboot update open_gapps-arm64-6.0-aroma-20160814.zip
But I got...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions? I've found a few other threads but they're way too techy for me and I couldn't understand what to do!
Thanks in advance
I've realised that my initial post was pretty vague and I don't think I used the correct terminology so I'll explain in the hope that someone may be able to help.
So I wanted to update from 5.1.1 to 6.0.
I found an article from Cyanogenmods and I downloaded the Redmi 3 TWRP recovery, the ROM for Redmi 3 Cyanogenmods 13 and the GApps.
I installed the TWRP recovery,
Copied the GApps and CyanogenMod ROM ZIP to my device
Booted into recovery mode and backed up my data using TWRP,
Wiped data factory reset, Cache partition, Dalvik Cache and Formatted the System partition,
I flashed the custom ROM and it all worked well,
I then went to flash the GApps and thats when it said that I had installed the wrong version (I needed the ARM64 not the 32).
It then restarted and I've been stuck in a bootloop.
I can access fastboot.
I can't get into recovery, the phone just goes to the Xiaomi sign then gets stuck on the Cyanogenmod logo.
A few times it looked like it was doing an update but it was all in Chinese so I couldn't understand it then it briefly went to what looked like a set up screen but then rebooted and got stuck on the logo screen again.
Any help would be great;y appreciated.
I only bought this phone a few days ago, my stupid mistake for wanting to upgrade!!
Ramah.h said:
Hi all,
I have a Xiaomi Redmi 3 and I tried updating it to Android 6.0 today using a very helpful article from cyanogenmods
It was all going so well until the end when I came to flash the ROM, I downloaded the wrong one!! (I needed the ARM64).
Anyway my phone restarted and now I can't seem to rectify my mistake!
I can't access the recovery mode (Power button and volume up) It just shows me the Xiaomi sign and stays there but I can access Fastboot (Power and volume down) and it can communicate with the PC via CMD.
I'm super new to this and I've been looking online for the past 5 hours with no luck so maybe someone can help me out.
I tried fastboot update open_gapps-arm64-6.0-aroma-20160814.zip
But I got...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions? I've found a few other threads but they're way too techy for me and I couldn't understand what to do!
Thanks in advance
Click to expand...
Click to collapse
if i was in your situation i'd probably go fastbootmode > EDL > then flash official dev rom from miui site(ido). from there'd id redo everything unlocking bootloader,flashing twrp,etc.
check out this post:
http://forum.xda-developers.com/redmi-3/development/redmi-3-pro-spacex-rom-t3406919
it has a "How to Unbrick Redmi 3 ? " on the first page.
helped me alot, hope it unbricks ur phone too! cheers!
have you unlocked your bootloader?, its very risky to change to custom rom when your bootloader is locked, if its already unlocked, all you have to do is go to en.miui.com and download official rom for redmi 3 and flash it using Miflash
Edl mode is the best bet to get back to stock. Vol up and down while plugging in if i recall, from an off state. I couldn't get it from fastboot.
Lets try this for reach to TWRP.
First press volume up and down button after press power button and wait.
Phone is going to restart and you see mi icon very short time and screen is going black, immediately release all buttons and wait. You have to reach recovery with this combination.
Open a terminal/command prompt and navigate to where you have the TWRP file. Put phone in fastboot mode and enter this command: "fastboot boot (name_of_TWRP.img)".
Then when you're in recovery, just flash the new Gapps.
Hello all,
First of all, as a disclaimer: I am a total noob in this area. I just got my Ulefone T1, and tried to root it by installing TWRP and then installing SuperSU using TWRP. When I first installed TWRP, it worked and I got into the TWRP recovery menu. However, as the phone had to be wiped, I couldn't install the SuperSU zip anymore. I did a normal reboot to transfer the SuperSU zip to my phone, but when I then tried to turn my phone off and access TWRP, it went to normal recovery mode of my phone. As I wanted to start fresh off again, I went to the settings of my phone and did a factory reset silly.
Now, it is stuck in a bootloop where I can literally do nothing. I cannot access factory mode or recovery mode, all it does is just endlessly boot and turn off. I have managed to turn it off completely, but that's all I can do. Also, the battery is not removable.
Does anyone with a little more knowledge have a suggestion for me? Thanks in advance!
As an update, I got a suggestion to fully drain the battery, but that does not work either. I have tried connecting it to my PC, which is not working, but that was acting weird before. I guess it's just not possible?
did you work this out ? i am stuck in bootloop too ??????
Daviesjosh95 said:
did you work this out ? i am stuck in bootloop too ??????
Click to expand...
Click to collapse
I have no idea what software is necessary to do it for your device but you can flash stock rom, if it uses sp tool or something then download stock rom, use sp tool to flash it. Should be OK after that. As I am not familiar with this device I can't give you any other advice other than flashing stock rom.
Any solutions to unbricking/boot looping?
Have anyone found any solutions to unbricking phone??
Mine also did bootlooping after unlocking bootloader.
I was able to flash successfully but screen fussy and unreadable and not able to touch. I am able to hear but lines are on screen.
I have same problem, please, anyone help, I think I used wrong twrp image
Ulefone T1 Bootloop solution 2019.
I was able to fix the bootloop of my ulefone t1, just flash it with sp flash tool by following this guide:
1. Download the Stock Firmware on your personal computer.
2. Install the USB MTK Drivers (skip if you have it already installed).
3. Download and Launch the Smart Phone Flash Tool (SP Flash Tool)
4. Click the Scatter-loading button to navigate to the stock Rom you just downloaded.
5. Select the Scatter File from the extracted Stock Firmware on your computer.
6. Select the Download Only in the SP flash tool option
7. Click the Download button to start the Formating process.
8. Connect your device via USB to the computer>> holding volume + and volume – button of your device at the same time or holding power button only so that the flashing process will starting working
9. Patiently wait for your device to be formatted.
10. After the formatting is done, a Big Green button will pop up on the SP Flash to show that.
11. Unplug your device and boot it up.
12. If you have a boot loop after booting your device, boot into recovery mode and do a factory reset.
13. Voila, you are all good.
Very important step 8 of the guide.
Hello, My phone (Col L29) is currently softbricked and I can only access fastboot and ERecovery, TWRP when flashed won't boot when using the right process to boot and ERecovery cant download the firmware, I've tried flashing various parts of the stock update firmware to no success, if anyone can help that'd be really good!
Thanks
Andrew
Could you confirm what have you done before leading to this condition? May be can help
shashank1320 said:
Could you confirm what have you done before leading to this condition? May be can help
Click to expand...
Click to collapse
before it was bricked I was going through the process to install a new OS, i was using twrp bekerly (view 10) and it froze on the splash screen, so after a few minutes i held the power button and after that i couldn't access the recovery whatso ever.
I've tried ERecovery via wifi and OTG (not sure if i set up the folder correctly for otg of if otg just doesn't work), flashing stock recovery, flashing as many things as i could from the UPDATE.APP (do note that i couldnt flash ramdisk as that command was "not allowed" as with many other partitions), i have also tried wiping then flashing (be that through ERecovery or Fastboot).
When I try to access Recovery (rebooting after flashing, removing USB cable and holding Vol +), it goes to the Device is not trusted screen and then to ERecovery if i don't let go of the vol button.
I've softbricked my Moto G4 before but man, this is a ***** in comparison.
Try to flash the correct twrp via fastboot and should be fine. You may have incorrectly flashed the erecovery to the regular ramdisk_recovery(probably) which may lead to only erecovery and fastboot.
Erecovery doesn't work in most of the cases for many(though i have success rate of over 90%).
Also, flashing cust.img, version.img and vendor.img helps sometime.