So I flashed the Malludus ROM and got Keyboard errors so I flashed his package again and now its consistently only booting to TWRP. I do have some data on the internal memory but I can't get passed TWRP. Have tried PC suite getting error code 43.I've tried other Roms but can't get passed TWRP.
Related
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.
Device - oneplus 3
Secure Boot - enabled
Device State - Unlocked
recently wanted to update my rom (Resurrection Remix-N). When I boot into TWRP, I get an error 7. I was also having issue with titanium backup (keeps crashing) so I was thinking it was the ROM since I haven't updated in a while. Since I couldn't update with TWRP and error 7, I decided to switch ROM.
I did a nand backup, then proceeded to factory reset in TWRP, reboot recovery (habit of mine).
And now I was stuck with at TWRP decrypt Data because my previous pattern is not working. Gives me a "pattern failed, please try again!")
My question, is there a way to at least get my data off the device (backup to laptop and restore later)?
I can boot into fastboot. but I can't see device storage on laptop.
okie03 said:
Device - oneplus 3
Secure Boot - enabled
Device State - Unlocked
recently wanted to update my rom (Resurrection Remix-N). When I boot into TWRP, I get an error 7. I was also having issue with titanium backup (keeps crashing) so I was thinking it was the ROM since I haven't updated in a while. Since I couldn't update with TWRP and error 7, I decided to switch ROM.
I did a nand backup, then proceeded to factory reset in TWRP, reboot recovery (habit of mine).
And now I was stuck with at TWRP decrypt Data because my previous pattern is not working. Gives me a "pattern failed, please try again!")
My question, is there a way to at least get my data off the device (backup to laptop and restore later)?
I can boot into fastboot. but I can't see device storage on laptop.
Click to expand...
Click to collapse
A method thats worked for me in the past is to use fastboot to re-install TWRP. Use TWRP 3.0.4-1 and reboot your phone to recovery.. You'll be im MTP mode so you can transfer files onto your phone for flashing.. If you get code7 in TWRP, use a different FIRMWARE+Modem version.. If you want the latest RR use 4.0.3.. Your data should be safe..
hagar006 said:
A method thats worked for me in the past is to use fastboot to re-install TWRP. Use TWRP 3.0.4-1 and reboot your phone to recovery.. You'll be im MTP mode so you can transfer files onto your phone for flashing.. If you get code7 in TWRP, use a different FIRMWARE+Modem version.. If you want the latest RR use 4.0.3.. Your data should be safe..
Click to expand...
Click to collapse
I have already tried that unfortunately, it didn't work. Flash twrp-3.0.4-1-oneplus3 but I am still asked to decrypt data. My internal storage show as 0MB I also have MTP enabled but still not showing on laptop. It shows device connect but no storage.
okie03 said:
I have already tried that unfortunately, it didn't work. Flash twrp-3.0.4-1-oneplus3 but I am still asked to decrypt data. My internal storage show as 0MB I also have MTP enabled but still not showing on laptop. It shows device connect but no storage.
Click to expand...
Click to collapse
I had that once when i messed about with f2fs.. Only way i found was to flash stock ROM and recovery, reboot and fastboot TWRP again.. Now my laptop could see my phone and i could start from scratch again.. I'm sure there is a better way but this worked for me.. Sorry i cant be of more help
Flash all 670 img's till one works :laugh:
I think error 7 is related to firmware flash 4.0.3 and then your rom of choice should be fine
hagar006 said:
I had that once when i messed about with f2fs.. Only way i found was to flash stock ROM and recovery, reboot and fastboot TWRP again.. Now my laptop could see my phone and i could start from scratch again.. I'm sure there is a better way but this worked for me.. Sorry i cant be of more help
Click to expand...
Click to collapse
You were lucky. I flashed stock recovery so I can flash stock rom but still no luck. I miss samsung odin.
Thanks anyways for ur contribution.
Down graded to Oneplus 2 until I fix my phone.
Was trying to update the supersu binary by installing the updated zip in recovery. On reboot it was stuck in a boot loop. First off nothing else worked, then fastboot worked and then 10 mins later twrp recovery started working. I tried to restore a backed up image but still got boot loop. Then tried to flash a rom I had on sdcard - still boot loopy. Tried to go the miflash tool root but couldn't get it to find the phone despite it appearing in explorer. Copied stock miui zip onto sc card from pc and installed but still same problem. Standard dalvik/cache wipe before and after each install. Now I'm struggling to get recovery up.
Help - haven't managed to totally brick something despite many years of tinkering. :/
PS. I can still get fastboot up. Now when I try to get recovery up the screen goes black and I have to reboot.
Hi
I've tried 3 different twrp images, all supposedly bumped (take this one for example), but when I try to boot to recovery with any of them I still get the boot certification verify error and can't get into recovery
running rooted 5.0 stock wiped, installed by instructions in linked threads
Thanks
update: used autorec, can now access recovery... but it's twrp 2.8.6... can I install fulmics on this version, or how do I update it?
update 2: TIL that you can update twrp from inside twrp and it still works, but that still leaves me confused with the above problems
So, I installed philz recovery on my htc desire 816g. And decided to flash this rom-
https://forum.xda-developers.com/de...-1-slim6-v0-9-htc-desire-816g-mt6592-t3448796
The recovery showed that there is an error in the file. I had completely wiped my stock rom and had forgot to take backup. After showing that error, the recovery automatically rebooted the device without an os. It is now stuck in bootloop and it is not being detected by my laptop via adb. Please help!!