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!
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..
Update:
I just figured it out that it is a kernel (not ROM) issue and hopefully @djvoleur will update UniKernel soon to fix this....
Hey guys,
I am here to seek help for an issue my phone has after I flashed the Renegade OJ1-V1 Rom.
How I flashed Renegade:
Odin OJ1 stock ROM --> Odin Kernel --> Odin TWRP --> Swipe everything (except internal storage) and flash Renegade in TWRP.
Issue I have:
If the phone is off and I try to turn it on, it will get stuck in the splash screen (the screen showing "Samsung Galaxy S6 Edge" even before the boot animation) and will not boot into the system. There is a workaround to turn it on normally: that is, to first boot into TWRP (which is fine) and then boot to system from TWRP.
Some more information:
The "reboot" option still works fine. That is, if I directly reboot the phone (instead of turning it off and manually turning it on later), there is no problem.
If you guys have any idea how to fix this, I would definitely appreciate it.
Flash version 8 of the unikernel
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
Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
zariouh said:
Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
Click to expand...
Click to collapse
Wipe cache before reboot.
cooltt said:
Wipe cache before reboot.
Click to expand...
Click to collapse
I have already tried wipping cache and dalvik cache, I even wiped system and data and installed the ROM again but the phone's still stuck in a bootloop.
Now I'm about to flash through Odin back to stock and see if the phone turns on.
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wiped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
zariouh said:
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wipped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
Click to expand...
Click to collapse
That ROM is in BETA mode, which means it could be lost of things. Your question should be asked on the LOS 17 thread itself but when a ROM is in BETA mode it's very difficult to tell what the problem is. Ask the developer @ivanmeler he might be kind enough to answer you.
Help Me too !!!!
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
I'll try to help
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
zariouh said:
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
Click to expand...
Click to collapse
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Sorry but I don't have enough knowledge to help with kernels, Now from what I understand is that you tried flashing stock ROM and your phone got stuck in a bootloop, Right? And just to confirm could you mention the model of your s7?
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Flashing stock rom will restore stock kernal. Firmware must be correct for device and region.
Bootloop after Odin Flash.
1. After flash boot into stock recovery
2. How to>>> In this sequence hold volume down+home+power. As soon as phone goes off move finger to volume up while still holding home and power. It may take several attempts as you have to time it just right when the screen goes black.
3. Once in stock recovery choose wipe data/ factory reset. Then choose reboot device
4. Can take 5-10 minutes on first boot. Updating and erasing screens are normal during this process as well as rebooting. Just leave it finish.
If this does not work Reflash stock with Odin but this time uncheck "auto reboot" in Odin options before you start.
Once Flash finish, disconnect from pc and follow 1-4 as above.
Kernel Problem
Pls help as I figured out that all the kernels after v3.18.140.5 are not booting on my phone. Can someone help me with this.
Model No: SM-G930FD
Device: Galaxy S7 Flat
BL: 8 (Latest)
File System: ext4
I have already restored stock many times and formatted my device many times. I used firmware from samfw to go to stock.
That is why no Aosp was booting on my phone
Pls Help