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!
Related
I was trying to install EagleBlood ROM to run Gingerbread on G2x, and followed all instuctions, installing ROM manager, using that to flash to their recovery, then deleting caches, then flashing the ROM. After a reboot, EagleBlood is stuck on a bootloop, displaying an image of and android surrounded by a sparkly blue circle. If I take out the battery and then try to boot into recovery, the recovery image is displayed for a while, but then resets and goes back to rebooting without opening recovery. I am very scared that I may have bricked my brand new phone and do not want to pay for a repair. Any help is very much appreciated.
XDvinSL said:
I was trying to install EagleBlood ROM to run Gingerbread on G2x, and followed all instuctions, installing ROM manager, using that to flash to their recovery, then deleting caches, then flashing the ROM. After a reboot, EagleBlood is stuck on a bootloop, displaying an image of and android surrounded by a sparkly blue circle. If I take out the battery and then try to boot into recovery, the recovery image is displayed for a while, but then resets and goes back to rebooting without opening recovery. I am very scared that I may have bricked my brand new phone and do not want to pay for a repair. Any help is very much appreciated.
Click to expand...
Click to collapse
I would suggest that you NVflash clockworkmod by reading the thread here. Once you do that, you can access your recovery via volume down and power. If you do not have CWM installed via NVflash, for now, you should be able to reset everything by pressing the volume down and power to restore your phone to a factory state.
Thank you very much for that tool! Booted up the recovery and am currently recovering from earlier today on the stock ROM. If this is my last post, it was a success!
XDvinSL said:
Thank you very much for that tool! Booted up the recovery and am currently recovering from earlier today on the stock ROM. If this is my last post, it was a success!
Click to expand...
Click to collapse
Now, when you install a rom through CWM, i would suggest wiping data (if you are switching between roms) and cache. This will prevent you from going into bootloops. I would also suggest after flashing a new rom, going into CWM > Advanced > Fix Permissions. You should now be golden.
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..
When I flash merely anything, my tablet gets stuck on the Samsung boot logo (I have waited, and waited, and waited, until the battery dies). Sometimes even installing ClockWorkMod Recovery (official) will do this. But I managed to get the latest official CWM flashed. But I can't get ANY other rom to work. Even roms I have successfully flashed before.
Note: If it flashes it gets stuck at the Samsung boot logo. But I have also had it not flash sometimes too, giving me error code 7 in CWM which is an authentication/permission/certificate problem.
I am going to try right now using Odin to flash to stock, and work from there, maybe it will completely clean out any crap in the memory.
My tablet is the P3113 model.
Ok! So after flashing stock rom, then cleaning all the cache stuff, then attempting to install CM it fails with CWM Error code 7. And when I just reboot system, it gets stuck at the boot logo. Damn, I get stuck there without even flashing!!
Well, I may have figured it out..... ummm i guess *cough! cough!* I somehow changed kernels *cough! cough!* dang, my allergies! Hahaha, anyways, I flashed a kernel compatible with stock rom and cm10.1 and it has gotten past the flash of cm10.1 and seems to be booting up right now.
Im trying to flash magiorom beta 2 on my phone. When ever i flash the rom i always get a boot loop. It boot loops for a while then goes into android. How would i fix this boot looping problem? First i sideloaded the rom, then i wiped cache, then i flashed the rom, then i rebooted into bootloader and last i flashed the boot.img . I dont think im doing anything wrong. Please help!
resolved​
I was trying to flash a gsi but when I boot into twrp it just goes back to the booting screen again when I press anything, I tried reformatting in wipe before it went back to booting but after that it's even worse. I went into odin and reflashed twrp but same thing. I flashed its firmware from samfx but one ui doesn't even want to boot, it just shows an endless charging logo. The only thing I can boot to currently is the default recovery and download mode. I really need help quick because I need to do some work on my phone.
iintc said:
I was trying to flash a gsi but when I boot into twrp it just goes back to the booting screen again when I press anything, I tried reformatting in wipe before it went back to booting but after that it's even worse. I went into odin and reflashed twrp but same thing. I flashed its firmware from samfx but one ui doesn't even want to boot, it just shows an endless charging logo. The only thing I can boot to currently is the default recovery and download mode. I really need help quick because I need to do some work on my phone.
Click to expand...
Click to collapse
When you install a GSI, the only partitions you should be messing with are /system and /data.
Did you mess with anything else?
Use Odin to perform a clean flash of the firmware, including a data wipe.
V0latyle said:
When you install a GSI, the only partitions you should be messing with are /system and /data.
Did you mess with anything else?
Use Odin to perform a clean flash of the firmware, including a data wipe.
Click to expand...
Click to collapse
No I don't think I messed with anything else. Also flashing stock firmware again works somehow even though I already tried flashing it before, anyhow, I greatly appreciate your help
PS still not sure what caused twrp to bootloop