Related
Just got my n5 and decided to unlock and root it, everything went well until I wanted to flash a rom, no matter what rom I flashed I got all kinds of issues from all apps force closing to bootloops, soft keys not working ect. I've tried flashing stock img, factory reseting ect, nothing seems to work. I'm not sure what's going on here, any help?
I am probably already asking you questions you have already done but... Have you reformated the system, data, and cache partitions prior to flashing? Also are you checking the MD5 of the ROMs you are trying?
Yeah tried all of that, md5's are correct, thanks though
what recovery and version are you on?
what wipes exactly are you performing?
you've checked the md5?
Ok. just trying to narrow things down. When you flash the stock image from https://developers.google.com/android/nexus/images#hammerheadkrt16m are you running the flash-all script? And after that before even adding any apps or changing anything does it give you issues?
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Xolith said:
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Click to expand...
Click to collapse
are you flashing a gapps add-on package with your custom roms? the right gapps?
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
simms22 said:
are you flashing a gapps add-on package with your custom roms? the right gapps?
Click to expand...
Click to collapse
Yeah, tried a few including banks, PA 0-day, psx gapps
neomorphix said:
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
Click to expand...
Click to collapse
They appear right after I flash the rom, tried with both the included and with a custom one
Tried a few days later and it worked, weird haha. Thanks though
So I was using Calkulin's stock 33R with AK kernel, which has been running fine. I deciced that I should try PA, so i did my regular thing of making a nandroid backup, wiping /data, /system and /cache. Flashed PA and the relevant Gapps, and got stuck on PA bootscreen. So I tried it again, and upon closer inspection, in, the flashing of Gapps failed because it was unable to find build.prop.
So I tried it all over again just with PA, no Gapps, no anything else. Same result, just the PA boot animation staring at me for over 20 minutes.
I then tried flashing Clakulin's stock again, and no luck, still stuck on OPO logo screen. I thought perhaps my partitions were messed up, so I wiped everything and flashed stock 33R from CM. Well, at least that booted and my EFS data was intact. I then tried reverting to Calkulin's stock by sideloading, and it never went past the boot screen.
Bottomline: I cannot use any ROM apart from stock 33R. Installing a kernel on top bootloops, installing root bootloops, installling a ROM bootloops, almost anything I flash bootloops. This is driving me nuts.
I am using the latest Philz recovery and my BL is unlocked. I am also a very seasoned flasher and I know what I am I am doing. Yet, this issue is boggling the crap outta me.. I know the solution is probably simple, yet I'm overseeing it.
PLS DON'T KILL ME FOR NOT PROVIDING A LOGCAT. I'll provide anything requested by those helping.
EDIT 1: When I say flash stock 33R, I am referring to the factory image provided by CM on their site. Also, remmeber the nandroid backup I made? That failed to restore. Yea, it failed hard on me.
EDIT 2: I remmeber reading in another device forum where his recovery was mounting the wrong partition when flashing, which makes sense since Philz's recovery produces an error where gapps can't find build.prob. I checked the recovery settings and the only mount I can change is SD from /media/0 to /media/
EDIT 3: I want to shoot the phone, and then myself.
Perhaps try using TWRP, just to rule it out?
EddyOS said:
Perhaps try using TWRP, just to rule it out?
Click to expand...
Click to collapse
Tried TWRP, no error on flashing the Gapps, but still stuck on boot animation.
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
EddyOS said:
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
Click to expand...
Click to collapse
I meant the stock factory image. My nan droid failed to restore.
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
EddyOS said:
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
Click to expand...
Click to collapse
All md5s matched with the files. It IS really bizzare indeed. I searched about this problem for several hours, even on other devices. But no luck!
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
gavin-phelan said:
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
Click to expand...
Click to collapse
Tried that too. Started off from 25, moved to 30 and still no luck.
I have encountered a strange problem. Please help.
1. I was running CM12 nightly (April 10 build). I also have TWRP backups of Apr 8 image and my old CM11S (44R) image.
2. I downloaded OxygenOS to try it out. Booted the phone into TWRP and tried flashing the ZIP.
3. Got an error while flashing the ZIP.
4. Rebooted the phone into recovery and tried restoring the Apr 10 image.
5. Restore says it is successful.
6. On reboot, the phone stays on the "Powered by Android" screen. It does not boot up into the ROM image. It boots up into recovery instead.
7. I tried the same process with Apr 8 image and the same issue.
8. Finally, I restored the backup image of CM11S and that works well.
Can someone please advise how can I get my backup ROMs to work?
I have now tried backing up ROMs for Cyanogen CMOS12 as well as Oxygen. None of the restores are working. I am backing up all partitions. Where am I going wrong? The restore does not give any error, but the boot is stuck at the logo. When I restore CMOS12, it gets stuck on the screen that says "Cyanogen". When I restore Oxygen, it gets stuck at the boot animation of Oxygen.
I am using TWRP 2.8.6 for restore and Online nandroid manager for backing up.
Is it possible that OnlineNandroid manager uses a different version of recovery for backup?
Please help.
.
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
JeffDC said:
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
Click to expand...
Click to collapse
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
see if this link has any relationship to your general issue
https://forums.oneplus.net/threads/...cm12-1-nightlies.300277/page-78#post-11010591
read around a bit as some folks seem to have had the same issue as you, there is also an xda topic for the nightlies, as well which may be a good place to search
indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
Did you wiped cacha/Dalvik? I personnaly do these wipes before and after flashing/restoring.
If I were you, I'd try to flash the latest cm12 nightly "on" you restore, maybe it could help..
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
real_sl4cker said:
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
Click to expand...
Click to collapse
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
indoliya said:
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
Click to expand...
Click to collapse
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
real_sl4cker said:
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
Click to expand...
Click to collapse
Finally resolved this by going to Online Nandroid app and changed the shell to default and busybox to default. Now the backups taken with these settings are getting restored successfully.
Hi, im new here and i have problem with booting up my TF700t...
I did the process uncountably many times with clockwork and twrp recovery, i wiped out completely everything and i can say i tried everything to make it work... but when tablet tries to boot, there appears asus logo, then the four penguins show up with some codes, the last one is "preinit : finished - booting your operating system" ... sometimes there appears another two codes under that, but only sometimes. Then the crombi kk animation shows up and get stuck. This is repeating without end. I tried everything on all the forums i managed to google out but the problem still resists. It looks like my last chance is to post my problem here.
Thank you and sorry for my bad english
did you reformat partitions, and did you make a mistake of formatting anything else to f2fs other than /data? which rom and which kernel?
I have been flashing crombi kk and i dont really know anything about f2fs and kernel... I wiped out everything because the OS didnt boot up so i was forced to try that.
Much thanks for the reply...
You gotta check the basics first:
Have you enabled signature verification in TWRP to make sure you don't have a bad download?
Which TWRP version are you using?
If you didn't do it yet, format - not wipe - data and reinstall the rom.
I enabled signature verification, i tried different versions of twrp, now i am using the kang's 2.8.5.1 and i also tried to format and reinstall the rom as you say. Now i mentioned that there are multiple versions of crombi kk, is it possible that i have been using the wrong one?
marcq352 said:
I enabled signature verification, i tried different versions of twrp, now i am using the kang's 2.8.5.1 and i also tried to format and reinstall the rom as you say. Now i mentioned that there are multiple versions of crombi kk, is it possible that i have been using the wrong one?
Click to expand...
Click to collapse
I have the same problem and I too enabled signature verification.. I read that wiping everything and than reinstalling from external storage will help, but it did not.
I ran into a bit of a problem recently. My phone suddenly froze, and didn't want to wake. This happens occasionally, so I did what I always do: hard reboot the phone. Hard rebooting resulted in a bootloop, I got stuck in the bootanimation. So at this point, I figured wiping the phone and reflashing would do the trick. Guess what? It didn't. I thought this was a bit odd, so I started to (clean) reflash earlier builds of TugaPower, but nothing seemed to help; every build resulted in a bootloop, except for TugaPower N5. So I decided to just run N5, new N8 build was released though, so I tried flashing that build, still stuck in bootloop.
At this point I lost all hope in TugaPower and decided to flash the official CM14.1 build; no dice, resulted in a bootloop. At this point I tried resetting everything, wiping my complete phone, but nothing helped. Then I tried flashing kwoktopus/updateing AOSP build, which did boot fine! I really want to run CM14.1/TugaPower though, but my phone just refuses to boot on both. Any ideas?
It is worth noting that I've tried almost everything (in TWRP) recovery at this point. From formatting system all the way to running adb to fix the persist partition. Nothing seemed to help. CM14.1 builds don't boot, but AOSP boots fine. WHAT IS WRONG WITH ME? MY PHONE?
Useful info about the phone:
I'm not running multirom;
I am using latest TWRP recovery;
I wasn't deliberately using F2FS or EXT4 memory, partition, whatever (I didn't know what they both did)
TugaPower N5 build ran fine, after that build everything bootlooped
CM13 boots, CM14.1 bootloops
Kwoktopus/updateing AOSP 7.1 build boots fine
Try checking if your /cache partition is formatted to f2fs, it sometimes automatically does that
f41lbl0g said:
Try checking if your /cache partition is formatted to f2fs, it sometimes automatically does that
Click to expand...
Click to collapse
It wasn't, it was in EXT4 format...
Which gapps?
giaur said:
Which gapps?
Click to expand...
Click to collapse
Open Gapps Pico, 7.1 of course. But I quit flashing it after a while, figured I'd keep that out of the equation when I was triangulating the source of what caused the bootloop. It definitely isn't because of Gapps.
Maybe you need to flash a different firmware?
Thepromodder said:
Maybe you need to flash a different firmware?
Click to expand...
Click to collapse
How would I need to do that? I (re)flashed the latest firmware for the TugaPower rom, but I figured that flashing a (new) firmware for the CM14.1 builds wasn't necessary.
Managed to fix it using this link: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I don't know what causes this to happen, but now you guys know how to fix it.