Hi Guys, I tried flashing a custom rom on my zenfone selfie and now it wont boot to rom it will just go to recovery whenever i tried to reboot the phone.
Well if you can get in to recovery, then either re-download that rom (could be corrupt) or flash a different rom.
Sent from my ONE A2003 using Tapatalk
i already tried flashing different roms but still the same
Related
Hello,
I am trying to install a custom ROM, but none are working. I install it using TWRP and it boots, but it gets stuck at the splash screen for the ROM. I've tried both ParanoidAndroid and CM10.1 and its the same with both of them. It does boot when I go back to stock though. I've tried reinstalling, I've tried using both TWRP and CWM, I've even re locked and unlocked the bootloader. If you have any idea what I can do please let me know.
What steps are you taking to flash the ROM.. Are you fully wiping?
Sent from my Nexus 4 using Tapatalk 2
you need a factory reset for the first flash. you cant just install.
flamadude said:
Hello,
I am trying to install a custom ROM, but none are working. I install it using TWRP and it boots, but it gets stuck at the splash screen for the ROM. I've tried both ParanoidAndroid and CM10.1 and its the same with both of them. It does boot when I go back to stock though. I've tried reinstalling, I've tried using both TWRP and CWM, I've even re locked and unlocked the bootloader. If you have any idea what I can do please let me know.
Click to expand...
Click to collapse
Make sure you do a full wipe before flashing the rom and if your installing paranoid make sure you use the Gapps ..
Hi,
Guys I need your help on this one.
I sold my A500 almost a year ago to a friend of mine. At that time I flashed it with a HC ROM and Recovery 1.3.4.
Last week the new owner of the tabled asked me for help updating the ROM to JB. Since now I use a Samsung Galaxy I completely forgot on the correct procedures to update the Acer A500. I simply downloaded a 4.2.2 Rom and tried to flash it on recovery mode.
After that I'm stuck with an endless loop. The tabled boots, pass the Acer logo, shows the ROM logo screen and than boot again.
Since I can still acess the recovery screen (it still shows 1.3.4 recovery) I tried flashing other ROMs with no sucess. Every room that uses the Aurora installer freezes as soons as Aurora Installer message shows on the screen. So I wasn`t able to flash a new Rom or a new Recovery (since all the Roms and recovery that I have found uses the Autora installer).
I also tried to install an older room (Tried the Lightspeed 2.1 ROM) and although I was able to flash it and reboot from recovery, it stops on the boot screen after that (I waited for 4 hours).
Can you guys help me with this one? Also, do you guys know if I can install a new Recovery using Odin?
Thanks
Anyone?
Maybe you should try flashing stock rom. Download 》rename it to update.zip》install from sd card or use EUU roms.
poslato sa elmag radija
Note 910C UK N910CXXU2COL2_N910COLB2COL1_THL ROM = can't install any other ROM - HELP
I'm in the UK and recently had some problems with bootlooping N910C, I then installed N910CXXU2COL2_N910COLB2COL1_THL to get the phone working.
I now want to install a different ROM - probably CM13 or Sixperience - I'm very open to suggestions of a low bloat mature ROM - if any exist....
Is there any obvious reason why my attempts at installing different ROMS all fail ?
Thanks for reading....
Is anyone out there ?
How are you trying to install roms? I think you have flashed a locked bootloader so won't be able to to odin any earlier base but custom roms should still flash through custom recovery. What errors are you getting?
Sent from my SM-N920C using Tapatalk
sawdoctor said:
How are you trying to install roms? I think you have flashed a locked bootloader so won't be able to to odin any earlier base but custom roms should still flash through custom recovery. What errors are you getting?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Hi sawdoctor,
I followed these instructions:
1) Put the zip file in your SD Card
2) Reboot in Recovery Mode (use Twrp or Philz Recovery)
3) Wipe Data, Cache, Dalvik Cache and format /System (If running Philz Recovery use the "Clean before install a new rom" option)
4) Install the ROM
5) Reboot.
From Philz and got a bootloop, 3 times so far.
I then have to install THL 5.1.1 from Odin as nothing else seems to work - also I can't get a nandroid backup from current ROM or back up EFS - so experimenting is a bit risky....
Which rom are you trying to install? Also are you sure it's bootloop, if you flash a deodexed rom through recovery then first boot can take 15 mins
Sent from my SM-N920C using Tapatalk
sawdoctor said:
Which rom are you trying to install? Also are you sure it's bootloop, if you flash a deodexed rom through recovery then first boot can take 15 mins
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
After a fresh install of a custom rom it could take as much as 20+ minutes, I know because it took my note 4 910c that long to boot into erobot v12
Hey guys
i was using cm13 for a while but decided to go back to the stock rom
but when i flashed the stock rom back using fastboot [mi flasher], it doesnt boot up at all
i've tried 3 different builds of stock rom
it just gets stuck on booting up
but if install cm13 again it boots up fine
please help
I have searched everywhere and end up with the same problem every time I try to install a custom recovery. I try many different recoveries and only old TWRP recoveries will boot but will not allow me to flash roms. I was using a modified custom recovery for the longest and was the only one I've managed to use, it was 3.0.1 IIRC by kinglilrowrow. Using this recovery I could flash roms. Now I can't find this recovery anywhere. Currently I can only boot into recovery using First Aid from the forum but have not been able to flash any roms.
Finally was able to flash TWRP 3.0.2-2 not sure how it worked. Went back to stock recovery and oxygen rom then followed the same guide but it worked this time. All the info and files from XDA so big thanks to the site and developers.
Sounds like you where stuck on the old bootloader, which would explain why newer recoverys didn't want to boot. Should have been solved by updating to OxygenOS 3. ?