Hey guys ,
I´m fairly new to the scene and tried to get TWRP on my old device. When i unlocked the bootloader, i didn´t realised the phone was on factory version. I flashed a later versions boot.img and recovery.img (TWRP) which caused a bootloop when i was trying to enter recovery mode. Now i dont know which version´s boot.img to flash. And can the bootloop be fixed with the file?
Hope somebody can help me, as i do not find anything about a factory versions kernel or something on here.
Related
Question on rooting.(Not bricked lol),so about a week ago I got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before rezipping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
WhatTheAndroid? said:
So about a week ago I rooted my phone,got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before recapping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
Click to expand...
Click to collapse
I know it happened for me -- Sometimes it wont enter recovery for me even in the bootloader and I have to Power+Vol Down to get it back into the bootloader. But it makes sense this would be a normal process because if you flash the boot.img without any OS files to load after it will just boot-loop.
Once I get back into bootloader and can get back into recovery and flash the ROM everything goes well after -- although I'm not sure if you would classify this as the "norm" but it certainly happens for me
WhatTheAndroid? said:
Question on rooting.(Not bricked lol),so about a week ago I got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before rezipping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
Click to expand...
Click to collapse
I didn't have a bootloop. Mine just sat on the first htc bootscreen and did nothing. I had to do a simlated battery pull to get it to shut off. Generally I flash the rom in recovery then reboot to fastboot and flash the boot.img. This way you don't have to worry about the bootloop or simulated battery pull.
your just supposed to extract the boot.img not the whole rom. you should never be rezipping anything. if you are on windows i hope your using a real archive utility like 7-zip or winrar. just open the zip and drag the boot.img out which extracts it. flash the boot.img in fastboot then flash the rom in recovery.
getting into recovery from bootloader can be a problem at times but i haven't had this problem once since changing over to twrp 2.3.1.0.
Ok so today i tried to flash the JellyBam ROM 6.3.0. I read in the comments that first i had to go into bootloader mode and flash the boot.img that was in the ROM .zip when i did that it said it successfully flashed the boot.img but then when i tried to reboot it just got stuck in a bootloop. I was able to eventually get back to twrp with the fastboot boot recovery.img command but when i try to flash my old ROM (ViperXL) the Aroma installer comes up but with a weird blue gradient over it. And when it finishes it just goes right back to bootlooping. How do i fix this!? please help! thanks in advance.
All you did was flash the boot.img.
You have to flash the actual ROM also.
i forgot to mention that i did flash the rom when i was able to get back to recovery but i still got the bootloop
Sounds like a rom/kernel conflict. You flashed a cm kernel, and you can't run a sense rom (Viper) over that.
so what should i do then?
Factory reset and flash the apporpiate combo..
Hi my phone came with 4.4.2 V100R001C00B119 and i tried some things and ended up with bricked device.
The only thing that is working is TWRP recovery, i tried lots of stuff even flashing full room over fastboot img by img but no luck.
Currently phone can go into fastboot and there i can flash TWRP, and thats it. Bootloader is unlocked. It just shows huawei logo and rebots and its like that for last 3h.
So from what i discovered i need to flash recovery that was originaly there when i took the phone to play with, but its just that it is impossibile to find this firmware out there.
Any help will be much appreciated.
Thanks
Alex
hey folks, yesterday i flashed a new rom, during flash i got an error (dont rember which one). i flashed a few other roms didnt work also, so i flashed a new recovery. i rebooted to recovery but i dont get anything except the oneplus logo. i dont have a recovery or os. i can get into fastboot. i already flashed a few recoverys with fastboot. my recovery flashed succesful with fastboot. the problem is i cant boot into recovery. not with commands with fastboot, not with the volume buttons. so please help me because my phone is unsuable now.
i used this guide (i cant post links) so youve just bricked your oneplus one, reddit
i did all the steps of soft brick cant acces recovery. everything goes succesfully except booting to recovery.
nathan_b87 said:
hey folks, yesterday i flashed a new rom, during flash i got an error (dont rember which one). i flashed a few other roms didnt work also, so i flashed a new recovery. i rebooted to recovery but i dont get anything except the oneplus logo. i dont have a recovery or os. i can get into fastboot. i already flashed a few recoverys with fastboot. my recovery flashed succesful with fastboot. the problem is i cant boot into recovery. not with commands with fastboot, not with the volume buttons. so please help me because my phone is unsuable now.
i used this guide (i cant post links) so youve just bricked your oneplus one, reddit
i did all the steps of soft brick cant acces recovery. everything goes succesfully except booting to recovery.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view
Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Disable any antivirus otherwise you'll get false alarms.The program should automatically boot your device to recovery.
im amazing
wow im so glad. i unzipped a rom and flashed each file one by one and it works its fixed!!
Hi all,
I tried to uninstall Magisk yesterday and ended up stuck in bootloop. I tried wiping the data using twrp, not working, then i tried factory reset using twrp, also not working and worse for some reason my TWRP is not opening anymore after that
Hence i was looking around for the firmware, i found one, extract the update.app and get the boot.img, system.img, cust.img and recovery.img. I flashed it directly using ADB. And it got worse! Only then I realised from the forum that the firmware did not work! Sob2....
Now i'm stuck with a phone where the whole system, boot img, etc is wrong. Can anyone please share with me their firmware? Especially the four img that i messed up....
Really appreciate it...
If you can find the original boot.img which is backed up by magisk, then you can flash it and update to b120 through TWRP