No matter what kernel I flash, the phone crashes on the recovery splash screen (besides new cyanogen recovery). Unlocked bootloader, had cyanogenmod 11 previously but it started having problems...
Previously it was working fine, until today. I'm not sure what happened. Tried installing Kitkat rom because Lollipop is dependent on SDcard and all my SDcards are corrupt (fat32 fine but ext4 broken). Lollipop ROM Cyanogen recovery boots fine, but when I try installing kitkat rom it says footer is wrong. Both CWM and TWRP from KK recoveries crashes on the splash screen.
Suggestions? Very serious issue and I can't boot to ROM without recovery...
Related
I have a real frustrating problem with my Canadian Rogers Note 3. I'm rooted and running CM11, but I was looking for a ROM that might be more stable than the nightly builds. I wanted to try a TW-based ROM so I downloaded BobCat, JediElite, and FireNote ROMs.
I copied the ROMs to the SD card, booted into CWM Recovery and tried flashing one of them (don't remember which). The installation seemed to go fine, no error messages or warnings. But when I finished and rebooted the phone just stopped at the Note 3 boot screen. No boot animation, no loading, nothing.
I went back to CWM Recovery, tried the other two ROMs, and got the exact same results. Then I tried flashing the stock Rogers Note 3 ROM. CWM refused to flash it and spat out some garbage about a corrupt zip file (re-downloaded it with the same results). I eventually gave up and restored the CM11 image I'd backed up.
At this point I began to reason maybe CWM wasn't suited to installing TW ROMs, so I decided I needed TWRP instead. Goog.Im and TWRP manager both refused to install TWRP however. So I dropped the TWRP Recovery zip on my SD card and tried flashing it using CWM.
Here’s where it gets really freaky. When my phone rebooted I got a "recovery booting" message, but the recovery never loaded. The screen just froze at the Note 3 logo. If I pulled the battery the phone would again display "recovery booting" and sit there endlessly. The only way I could break the cycle was booting to Download Mode, then exiting so it enters a normal ROM boot.
I let the phone boot up fully and then opened ROM Manager. It showed TWO recoveries installed, one CWM and one TWRP, apparently side by side. Is this even possible???
So anyway, I went back to playing around between ROM Manger, Goo.Im, and TWRP Manger, trying to re-flash it to either CWM or TWRP, but not both. Nothing worked; every time I tried booting to recovery the system would hang at the “recovery booting” message.
I eventually tired of this and decided to get out Odin. I flashed TWRP Recovery successfully (according to Odin), but it still won’t launch. I then tried flashing CWM Recovery with the same results.
So completely out of options, I tried flashing the stock Samsung Recovery. It boots just fine. So I try again flashing the custom recoveries, but they still refuse to launch. Each time I have to reinstall Samsung Recovery.
And that’s where I am currently: I have a (badly) working CM11 nightly ROM on my phone. I have the stock Samsung Recovery installed. I’m afraid to try flashing any zips using Samsung Recovery because my backup image was created using CWM, and if I can’t get CWM recovery to work I won’t be able to restore the backup.
Have I broken some law of the universe by trying to go from CWM to TWRP? Would TWRP work better with TouchWiz ROMs? And can I even install TouchWiz ROMs after hacking my phone to CM11 nightlies? Lastly, how can I get this $#@& Samsung Recovery off my beautiful phone and install a working custom recovery?
I was using JB liquidsmooth rom. I updated TWRP to flash liquidsmooth kitkat ROM.
I did a wipe, started to flash the ROM but mid-install the device rebooted then got stuck into bootloop.
when I try booting into recovery it will display the TWRP screen but then the device reboots.
any ideas how to fix this?
Install cwm or reinstall twrp. The recovery is probably corrupt.
Hi,
I've just tried and failed to install the "cm-12-20150218-NIGHTLY-nicki" ROM on my phone. Specs are:
Official Android 4.3 Firmware
Model: C1904
Timeline:
Unlocked bootloader according to instructions at http://forum.xda-developers.com/showthread.php?t=2484428
Phone then got stuck in official boot animation (the colourful one)
Didn't bother flashing the "Elixer" kernel as suggested in above thread
Used fastboot to flash the boot.img from the CM zip file
Booted to recovery
Wiped data & cache
Flashed CM & GApps from external SD card
Restarted phone
Phone showed big Android robot animation and then went back to CyanogenMod Recovery
Looking at logs showed "Cannot load volume /misc" error
Found a forum post saying this thread helped with the above error: http://forum.xda-developers.com/xperia-m/development/cwm-twrp-recoveries-cm12-lollipop-t2979752
Tried flashing TWRP recovery (http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507) within CyanogenMod Recovery, but it said the file integrity was bad or something
Used "fastboot flash boot FOTAKernel.img" to flash the above, which worked
Tried to wipe data from within TWRP, but got "failed to mount /data" errors
So the phone is now in a state where:
I can only boot into TWRP
I can't use ADB since the program on the computer won't detect the phone
Fastboot still works
I can't boot into Android
Something seems wrong with "/data"
Any ideas about where to go from here?
I was able to use Flashtool to flash the official firmware back on and boot into it as normal. After doing that and restarting the procedure to install CM12 2015-02-19, this time it installed just fine.
Although I still got errors about "Cannot load volume /misc". Hopefully they don't matter...
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
xa.fr said:
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
Click to expand...
Click to collapse
Yeah; it's installed and working fine. When I flashed the official firmware, (Android 4.3) I told Flashtool to flash everything including the kernel. That seemed to put the phone back into a good state, which allowed me to install CM12.
I'm not sure what caused the problem in my case. Maybe it was unlocking the boot loader.
Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Lip0ly said:
Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Click to expand...
Click to collapse
Just had an similar issue,
Try flashing first boot.img from the rom you will flash
then flash the recovery twrp big
then do the wipes ..
then flash boot.img and then rom
I thought this worked for me. (i flashed with the unboxed rom)
Just tried it, didn't work for me.
Bump
I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now