Ive run into a problem and need some help.
im running stock 5.0 with multi-boot and have autodroid 1.2 as a secondary rom for nethunter.
all was running well untill i used the "flash image gui" while booted into autodroid to flash the m4xx3dout .img
now my internal 5.0 rom will not boot it just loops at the circular-wavy-dots lol, i can still boot autdroid however. so still have access to storage and all my data (thanks multi-boot). autodroid rom is still showing as kangaroo kernel.
ive tried flashing the kexec_50_final zip in the "flash img gui app as well as in multiboot recovery to no avail.
any ideas?
No one?
Despite all of my efforts, I cant even flash any custom rom, including custom hydrogen and custom oxygen os, the only thing I can flash is stock Oxygen OS. Nothing works. I can flash even kernels, but not a recovery.
same problem with me i have recovery but every custom ROM is on bootloop and only OXYGENos is working
Are you sure that your storage is not encrypted ?
yousuf.shareef said:
same problem with me i have recovery but every custom ROM is on bootloop and only OXYGENos is working
Click to expand...
Click to collapse
Nice @abhisek1994 you've created two thread (this one and this one) for the same problem, in 3 hour interval: what's the goal to this?
One of the most popular custom ROM projects of the last few years, Paranoid Android lost many of its core developers to OnePlus in February 2015. OnePlus recruited them to develop its in-house, following its breakup with Cyanogen. Predictably, PA releases slowed to a crawl, with the last major release, based on Android 5.1, [coming out in July. In October, project lead Matt Flaming announced what pretty much everyone had been suspecting for a while – the Paranoid Android project was on hold.
Now the Paranoid Android project is back into the spotlight, with over a dozen new team members and a new feature-packed release that’s been nine months in the making.
Features coming in this release, some of them familiar and some new, include an improved floating window mode, immersive mode, on-the-spot controls for the behavior of the notification dropdown, a polished quick settings re-order mechanism, battery style, an advanced power dialog, support for Paranoid OTA updates, a theme engine, and support for layers. For certain devices, including OnePlus and Oppo phones, the release offers advanced features like an enhanced kernel, advanced gesture control, and support for the alert slider and fingerprints scanner.:laugh:
Flashing Instructions:Using Twrp
Boot into recovery
wipe/System/Data/Cache/Dalvik
Flash latest Cm Nightlies
Let it boot
reboot to recovery
Wipe system/Data/cache/dalvik
Flash Pa and gapps
Reboot.
Win.
OnePlus One Paranoid Android 6.0 2016 ROM Review! Thanks to @nrp31
www.youtube.com/watch?v=V89296fkzc8
Paranoid Android g+ Page(post your bugs and comments):https://plus.google.com/+ParanoidAndroidCorner
Link: http://get.aospa.co/official/bacon
Source: Android Authority
Some revival. I flashed it and I'm stuck at the OnePlus logo. Apparently someone with a OP2 had the same problem and he fixed it by flashing the system partition before flashing the ROM. I did the same and my phone still won't boot up. Oh well.
I used both TWRP 3 and 2.8.7.0 and am also coming from an unaltered COS 13.
Same issue as @aarthyn. Wiped data, flashed it stuck at OnePlus logo. Used TWRP 2.8.6.1 and came from Sultan's Unofficial CM13 (6.0.1) May 26 build. Restored my backup and now it comes up with a SIM Card not found error.
Not happy.
ch4o5 said:
Same issue as @aarthyn. Wiped data, flashed it stuck at OnePlus logo. Used TWRP 2.8.6.1 and came from a custom rom. Restored my backup and now it comes up with a SIM Card not found error.
Not happy.
Click to expand...
Click to collapse
The download page is blank. Where did u download from?
Stuck on boot logo. Came from cos13. Wiped everything except internal storage.
ch4o5 said:
Restored my backup and now it comes up with a SIM Card not found error.
Click to expand...
Click to collapse
Oh great, I was hoping that wouldn't happen. Looks like I'll have to do the full fastboot works to make sure everything's the way it should be.
At least I know it's not just me.
pa1281 said:
The download page is blank. Where did u download from?
Click to expand...
Click to collapse
From here, but it looks like it's just not working on the OPO for now.
rom is awsm booted for me 9/10 battery life is good just need a bit improvement on charging and camera ! daily driver rom for sure!
aarthyn said:
Oh great, I was hoping that wouldn't happen. Looks like I'll have to do the full fastboot works to make sure everything's the way it should be.
At least I know it's not just me.
From here, but it looks like it's just not working on the OPO for now.
Click to expand...
Click to collapse
Thanks . how did u flash? Did u flash over COS?
---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------
Dhairya said:
rom is awsm booted for me 9/10 battery life is good just need a bit improvement on charging and camera ! daily driver rom for sure!
Click to expand...
Click to collapse
How did u flash? Ppl here are reporting that ROM is not booting..
Booted fine . coming from omni 6.0.
Here are some screens
http://imgur.com/a/j86BA
pa1281 said:
Thanks . how did u flash? Did u flash over COS?
---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------
How did u flash? Ppl here are reporting that ROM is not booting..
Click to expand...
Click to collapse
the normal way which we always flash was on cos 13 use twrp 3.0.0.1 and rom is ssly having dam slow charging thats the issue ! nothing else !
How to flash PA rom....
1. Boot into recovery
2. Flash latest CM nightlies (optional)
3. Factory reset
4. Flash PA rom and Bank's Gapps
5. Reboot into system
6. Setup your devices
7. Reboot into recovery
8. Flash SuperSu
9. Wipe Cache and Dalvik
10. Reboot into system
11. Done
Only PA rom and Bank's Gapps can be flash together....if you're planning to flash SuperSu or Custom Kernel you need to reboot into system first then boot back to recovery to flash them (wipe cache and dalvik after flashing them)....
People who are coming from CyanogenOS 13, check your partitions. They might be formatted to f2fs, which may be why your phones don't go past the bootanimation. Mine were formatted to ext4, and I had absolutely no problems doing a clean flash from SultanXDA's latest CM13 build.
iPusak Gaoq™ said:
How to flash PA rom....
1. Boot into recovery
2. Flash latest CM nightlies (optional)
3. Factory reset
4. Flash PA rom and Bank's Gapps
5. Reboot into system
6. Setup your devices
7. Reboot into recovery
8. Flash SuperSu
9. Wipe Cache and Dalvik
10. Reboot into system
11. Done
Only PA rom and Bank's Gapps can be flash together....if you're planning to flash SuperSu or Custom Kernel you need to reboot into system first then boot back to recovery to flash them (wipe cache and dalvik after flashing them)....
Click to expand...
Click to collapse
custom kernel which custom kernel would work here ! ?
#define said:
People who are coming from CyanogenOS 13, check your partitions. They might be formatted to f2fs, which may be why your phones don't go past the bootanimation. Mine were formatted to ext4, and I had absolutely no problems doing a clean flash from SultanXDA's latest CM13 build.
Click to expand...
Click to collapse
Take it you were on the June build of SultanXDA's build @#define? I was on the 26 May version and I got stuck at the OnePlus logo screen.
ch4o5 said:
Take it you were on the June build of SultanXDA's build @#define? I was on the 26 May version and I got stuck at the OnePlus logo screen.
Click to expand...
Click to collapse
Yes I switched from the June 3rd build.
Dhairya said:
custom kernel which custom kernel would work here ! ?
Click to expand...
Click to collapse
i have no idea which custom kernel work for this rom yet as i only tested this rom on stock kernel in PA rom....
iPusak Gaoq™ said:
i have no idea which custom kernel work for this rom yet as i only tested this rom on stock kernel in PA rom....
Click to expand...
Click to collapse
yeah charging sucks in the stock kernel need to know which are the customs one !
wow there's a 6/8 build for the OPO already at PA!
You need to change your filesystems to ext4 before flashing the rom.Otherwise it won't boot.But I cannot see any customization in the rom!
iPusak Gaoq™ said:
How to flash PA rom....
1. Boot into recovery
2. Flash latest CM nightlies (optional)
3. Factory reset
4. Flash PA rom and Bank's Gapps
5. Reboot into system
6. Setup your devices
7. Reboot into recovery
8. Flash SuperSu
9. Wipe Cache and Dalvik
10. Reboot into system
11. Done
Only PA rom and Bank's Gapps can be flash together....if you're planning to flash SuperSu or Custom Kernel you need to reboot into system first then boot back to recovery to flash them (wipe cache and dalvik after flashing them)....
Click to expand...
Click to collapse
can i use open gapps ??
Hey guys, A few days ago multirom was working with almost all ROM.But now with the updated ROMs multirom isn't working. I don't know if my procedure is wrong or some thing. I asked for help in multirom thread but no aswer till now.
My procedure:-
1) flash primary ROM .
2)flash berserk kernel.
3)flash multirom-twrp.image
4)reboot to recovery
5)flash multrom-twrp.zip
6)reboot to recovery
7) flash secondary ROM from add rom button.
Tried the same method with another redmi 2 prime (same model with mine).....working .But in my device doesnot working.
same probs here
i also tried but not working. plz send multirom twrp 2.8 or older version
the procedure is
0.Backup all current partitions
1.Flash multirom twrp img
2.Flash primary rom
2.5.Flash kernel (with k-exec support)
3.0.Flash multirom wt88047.zip
4.0 Add secondary rom(s)
Just recently the CM14 nightlies have been put up for this phone. I'm currently running CM13 and was wondering if it's possible to "dirty flash" CM14 or alternatively wipe everything and flash a backup of my data?
Do a full backup with cm
13 in twrp then try a dirty flash up to cm14.1 if it doesn't work do a full wipe and Flash cm14.1 then do a restore of data from cm13 backup
Sent from my iPhone 4s using Tapatalk I also own a g900v
[email protected] said:
Do a full backup with cm
13 in twrp then try a dirty flash up to cm14.1 if it doesn't work do a full wipe and Flash cm14.1 then do a restore of data from cm13 backup
Click to expand...
Click to collapse
Okay, thanks!
The guide Says To Flash Gapps At The same time.It's a little buggy though. I'm having screen rotation issues.
It is in nightly status right now it won't be stable till a snapshot build comes out
Sent from my iPhone 4s using Tapatalk I also own a g900v
I can't enable wifi after Updated to CM14, clean install (cm13 to cm14.1).. Flash CM14.1 rom and then reboot to recovery mode again and installed GAPS, but wifi couldn't be enabled by any trial.. I went to back to CM 13.... Will wait some more time...:crying:
You did it wrong you flash ROM then immediately nougat gapps in custom recovery do not reboot in between
Sent from my Nexus 4 using Tapatalk
Win0416 said:
I can't enable wifi after Updated to CM14, clean install (cm13 to cm14.1).. Flash CM14.1 rom and then reboot to recovery mode again and installed GAPS, but wifi couldn't be enabled by any trial.. I went to back to CM 13.... Will wait some more time...:crying:
Click to expand...
Click to collapse
There's a new nightly and wifi "works", but if you reboot after the initial boot after installing the zip it doesn't work anymore. Using cm-14.1-20161130-NIGHTLY-kltevzw.zip