Hi,I have a XT1033 indian dual sim model(for specifics),It was running cm13 nightly latest,twrp 3.0.0-2 and bootloader 4.18
So I was watching youtube when suddenly the cyanogenmod booting symbol came,At first I thought I may have been holding the power buttton but after muh time i force shutdown it and restarted but it has been in bootloop since then, so I thought maybe it was problem with cyanogenmod and I thought of reinstalling cm13 fresh,so I booted into TWRP and chose wipe, advance wipe and selected to erase all partitions, it says erasing was succesfull but nothing has been erased,So i thought of flashing stock firmware using fastboot and I did everything was successful so I reboot the system but it still showed cyanogen mod bootlogo and it was still in bootloop.I thought it was a hardbrick and tried to use the bootloader bricker and use flash-blank.bat but bootloader bricker too does not work. Please help me,I have a busy week and my phone is very important to me.
Related
I have a Moto G 2013 (XT0133).
I was trying to install CM12 on it using TWRP recovery. I used this (youtube: /watch?v=ix7rrKS4keI) method.
It failed. Now I'm stuck on the "Bootloader unlocked" message and my device won't boot. How can I fix this? Do I have to wait for the battery to drain and then recharge my phone, boot into TWRP and flash the backup? Or is my device just bricked?
Can you boot into recovery? If you can, try wiping cache, Dalvik, and data to see if it boots.
If the phone doesn't boot, I suggest flashing back to stock 4.4.4. Do not flash anything lower than 4.4.4. Try to find your ROM here: See if you can find the stock 4.4.4 ROM from here: http://www.filefactory.com/folder/c6...how=100&page=1
Did you update your bootloader from Kit Kat to Lollipop before trying to install CM12?
I can't stop it from booting, it is just stuck on the "bootloader unlocked" screen. I made a backup, wiped everything except for internal storage (CM12 and GApps .zips were there) and then tried flashing the CM12 zip. After it failed, it said "no system" and the phone rebooted.
whatgabe said:
I can't stop it from booting, it is just stuck on the "bootloader unlocked" screen. I made a backup, wiped everything except for internal storage (CM12 and GApps .zips were there) and then tried flashing the CM12 zip. After it failed, it said "no system" and the phone rebooted.
Click to expand...
Click to collapse
There is some 2-3 seconds when device is off, when creen goes dark then turn vol- and power and after 3 sec left power off
You can't boot into fastboot? Booting into fastboot does not show the unlocked warning.
Hi guys, that's my first theard.
I installed CM13 a few days ago, the 20160102 nightly, but its didn't like me so much, my past ROM Slimsaber 5.1 had more features so I preferred it, and today restored my backup from that ROM.
It boots well but when finished to configure all apps it reboot into bootloop, i tried to wipe cache/data but nothing happened.
Then I tried to flash the firmware that I was using (BRAZIL 5.1 retail) and it flashed ok, with no problems. But when I reboot it stays in "bootloader unlocked" image. I tried to flash it again and didn't stay at the "bootloader unlocked" image, but its shows me a screen with a broken Android with the phrase "No command" and immediately disappeared, and then again, like an infinite loop. I don't know if this is useful but, when I turned off the phone to restore the backup I did it with the advanced Reboot menu into Recovery, is it related?
I know that it said, in the CM13 theard that IT CAN NOT BE DOWNGRADED, so I did the backup with TWRP, but I don't know why it bricked. Also I though it could be downgraded by flashing.
Thank you. I hope you can help me!
If you need some info about my phone please request it.
PD: Sorry for my bad English, is not my native languaje.
Edit: Now I connected it to my PC in bootloader mode, and force a reboot with fastboot and its shows the screen with a broken Android and the phrase "No command" and immediatly dissapered, cause if I try to "Normal Powerup" in the bootloader mode its shows the white screen of the unlocked bootloader.
Edit 2: Also I tried to install TWRP, and when I reboot with fastboot, the phone goes directly to TWRP, so I think is bugged or something, since I did reboot to recovery in marshmallow.
Have u fixed ur Moto G ?!
Hello guys, i did a lot of research before coming here and nothing seems to help me.
The Story is.. I updated to nougat, unlocked it, flash twrp, flash supersu and it showed no sim. So i tried wiping the phone and flash nougat again. Phone keeps booting on TWRP. So i flash Xiaomi.eu 6.12.1(the one i use before update to nougat). Still booting on TWRP, i read somewhere if your phone keeps booting on twrp, get to fastboot and type "fastboot continue" , and the phone finally boot to miui and now im on xiaomi.eu 6.12.1 bootloader locked.
The problem is when i try to update using updater, the phone reboot to MI logo and shuts the phone down .When i turn it on its still not updated and the rom.zip is deleted, i tried different version same thing happens. TIA!
I attempted to switch custom rom and end up in a brick situation.
What actually happened:
I rooted my device and installed twrp successfully.
Then I found this thread: https://forum.xda-developers.com/mi-4i/development/rom-lineageos-15-0-t3671815
I was really interested in switching to custom rom and downloaded all necessary stuff.
(Here comes my mistake) I boot to twrp and flashed the latest firmware (8.1.5.0), wipe cache, latest rom build (LOS 15.1),wipe cahe,gapps,wipe cache and reboot to system. (all process altogether)
Now device stucked at MI logo and never booted to system again. And unable to boot to twrp mode too.
What i tried to resolve(but failed):
Device was showing lineage battery icon but nothing else was happening. So i decided to return back. I flashed my device with latest stock flashboot rom "ferrari_global_images_V9.2.3.0.LXIMIEK_20180414.0000.00_5.0_global_680c582f20" and successfully flashed it as while charging i got led light back and stock battery icon but issue remain the same. Stucked at boot loop.
I also tried Fastboot Flash Through CMD-Prompt https://in.c.mi.com/thread-334-1-0.html
But still not working. I think it must be due to firmware upgrade to oreo and if downgrade is possible, issue can be resolved but not sure and don't really know how to execute that.
Please help me in solving this issue and whatever suggestion you give please provide proper guidance or link to guidance as I'm still new to all this.
Video showing bootloop on mi4i device : https://drive.google.com/open?id=1ufwk8TNIUmycJUdjTmDBXj38-1cPCrBu
How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/