Before trying to flash a custom ROM, I have previously rooted my phone through TWRP. I forgot to do a backup, and wiped the whole phone (except the SD card). After flashing the ROM, my phone has been stuck in a bootloop, but it can still boot to TWRP. The ROM I was trying to boot was CM 12.1 and I am using a Lenovo A5000. I still don't know if the phone can be recognized by a USB. Is there any way to fix this? Thanks for the help in advance.
Edit1: I just confirmed that the phone can be recognized by a USB.
Edit2: Just fixed this problem. If you downgrade the OS, it will boot properly.
Related
I was running Cyanogenmod9 on my SGH-I727R when I got into a bootloop. I reflashed stock Rogers Rom and still stuck in a boot loop. Any help please?
Scarecrow Legion said:
I was running Cyanogenmod9 on my SGH-I727R when I got into a bootloop. I reflashed stock Rogers Rom and still stuck in a boot loop. Any help please?
Click to expand...
Click to collapse
Can you please be more specific?
What screen are you exactly getting, the boot logo then a reboot? are you getting a recovery screen or do you bootloop not into the system but into ClockworkMod recovery?
The boot boot logo then restart. same thing with the stock rom it would boot into the Rogers logo then restart
Have you tried formatting through recovery? formatting can be found in mounts and storage.
yup, when I get back home I'll see if I can darkside wipe. see if that will help
That should help a lot. It should definitely work, make sure you install a Custom ROM and not a Stock ROM.
Make sure in future situations you don't install a stock ROM if your current ROM is a custom ROM, this can cause problems and will not fix problems. If you want to revert back to Stock ROMs after installing a Custom ROM I highly recommend you use Fastboot to flash the image. However there are tutorials and instructions on how to use Fastboot efficiently and properly so you don't mess anything up.
Cheers
Thanks again, darkside wipe worked. I have no clue what bricked it in the first place though
Scarecrow Legion
No problem Wiping everything would've worked too lol!
I rooted my ZTE Supreme about a year ago and didn't install any custom ROMs. I didn't make a backup because I never thought I'd need it, and I didn't install CWM recovery. I installed a custom boot animation and got stuck in a bootloop. I can boot to default recovery, but not CWM recovery. I have no way to fix this issue with ADB or anything else computer related because the USB port on my phone broke (the charger bent a bit too far and broke it). Is there any way to fix this, like installing CWM on an SD card and installing it with default recovery, or am I stuck with a brick? Any help would be appreciated!
So recently I've taken my hand at attempting to install Cyanogen on my phone. But I believe something went wrong.
I installed CWM onto my phone and wiped my SD card clean. Then via ADB, I transferred the files required into my phone and installed the firmware. However, upon loading it, I ran into multiple errors so I decided to format the system/sdcard again and reinstalled it.
Now whenever my phone turns on, it just goes straight into recovery. I've attempted to use multiple ROM files to install onto my phone but nothing works. My phone is an LG Optimus G Pro ("e980") using CWM recovery if that helps. I'm honestly a little scared that I permanently damaged this phone. The only real thing I can accomplish is installing a ROM into the phone, so I know for a fact that if I can pass this loop, there's an OS waiting for me. :/
veez21 said:
You flashed the recovery as boot, you can flash your boot img or reflash the whole rom...
You should be able to boot properly
Click to expand...
Click to collapse
With the assistance of TWRP in a zip file, I was able to flash my outdated CWM away.
Thank you for the confirmation, was scared if I flashed a recovery in a recovery, I would of lost something.
Great that you solved your problem.
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/