After almost each ROM I flash, I add "Pimp My ROM" tweaks, and every time I flash it with TWRP it just freezes while choosing the tweaks, is it a known bug or...? I tried 3 versions of TWRP, each one had that problem, but the official Recovery worked just fine (tested few times with no problems).
The problem is that I really love TWRP's UI and functionality, which the official Recovery doesnt have but I also love "Pimp My ROM"... They seem to not work well together...
Any ideas?
Related
I have a very strange problem with my N7100.
All ROMs based on the DLJ2 fails to work properly.
The interesting detail is that BatteryPlus 0.2 works normally together with the Perseus kernel. So when the DLJ2 ROMs fail I return to this ROM and it works good.
I have followed this procedure for flashing:
1. Wipe data/factory reset
2. Format /preload
3. Format /system
4. Wipe Dalvik
5. Wipe cache
6. Format /SDCard (internal)
This has been done with both CWM 6.0.1.5 and the TWRP.
I can flash BatteryPlus 0.2 with those measures without any problems. It works normally simply put.
When it comes to DLJ2 ROMs, the situation is different since the following things happens (with both CWM and TWRP):
Omega 7.3 (full installation, wipe or no wipe):
It simply hangs on the bootscreen. The Omega animation is active but nothing happens at all.
CrashROM 3.1:
This ROM can boot up but the Setup Wizard is extremely unstable and crashes often in connection with the Google account setup or when the Dropbox details are to be added.
Another problem is that very aggressive SODs occurs. This happens already during first boot, if the screen goes black, an SOD will most likely follow.
The phone process crashes too.
Android Revolution HD 5.0:
Very aggressive spontaneous rebooting happens.
The common denominator with the DLJ2 ROMs I have tried is especially a lot of crashes, reboots and SODs - or an unbootable device.
The problems occur immediately during initial boot and it doesn't matter if I flash mods (240 DPI, Kalagas Mixed Theme 2.0) or not.
Even stranger is the fact that BatteryPlus 0.2 works properly. If I for example encounters a DLJ2 ROM that crashes already during initial setup, I can do the wipes and flash BP 0.2 without any problems and get the device to work properly.
Before I decided to try some DLJ2 ROMs today, I had an uptime of more than 2 days on BatteryPlus so the stability is OK with that ROM.
I am at a complete loss with this.
The only similar situation I had was back in the Touch Pro 2 days when I had an older HardSPL and new ROMs were extremely unstable because of compatibility issues (with that old HSPL). After upgrading the HSPL to a newer version, everything started to run properly again (with new ROMs).
Could there be some kind of bootloader compatibility problem in this case?
To me, it is a bit strange that all DLJ2 ROMs I try fail while the ALJ3 based BatteryPlus works normally.
It is worth to mention that I don't experience any problems with root etc under BP 0.2.
I would be happy for all kinds of suggestions since it would be nice to be able to use DLJ2 ROMs with the new 240 DPI mods.
Edit: It is also worth to mention that I encountered SODs and stability issues with Paranoid Android too, return to Battery Plus worked and the stability came back.
It's like the device don't accept anything else than 4.1.1-based ROMs.
Edit: It is worth to mention that I have checked the MD5 for all ROMs and the flash itself works normally. The transfer of the ROMs has been made through the Android File Transfer application on the Mac.
Greetings,
Starting with the first release of the combined PAC/PA/AOKP rom I have been unable to install most AOSP roms for the T-mobile Note II. Currently I was able to get AOKP 4.3.1 installed but no Paranoid, Illusion, or PAC/PA/AOKP hybrid will run. They install fine but I get all FC's once it boots. I have updated recovery, tried multiple wiping including sys, cleared cache and dalvik just before first boot and after flash, tried fixing permissions which always fails, and I tried flashing without GAPPS as well... still no dice. Any ideas? On a side note, do any of you have a good S-pen app setup while running AOSP roms. I dloaded a handful of apps but nothing feels cohesive.
Thank you
EDIT: This issue just went away on it's own. For some reason I can install whatever now and I changed nothing.... crazy.
I have a Verizon GNEX, been running an older version of PA for quite a while, went to update to the newest version and on first boot during the initial setup it would freeze and reboot. I have tried everything i can think of, different roms, ODIN, different kernels, but it still will freeze and reboot after a couple taps, TWRP and the bootloader work fine and havent frozen once, I'm doing most of this through the Nexus Toolkit but I just cant get it to work at all.
Ive seen some people have had similar issues and they seems to be hardware related I'm really hoping thats not the case and its just an obscure issue that I cant seem to pin down
Any help would be greatly appreciated.
Most likely is the new CM theme engine bug included in most of the KitKat custom ROMs out there including PA. I found SlimKat to be stable because they're building their own theme engine instead.
Merry Christmas to all!
JLM, have posted similar on your other site.
Having a problem with the BrokenPop 5.0.2 on my L900 (Sprint Note2)
I can't seem to dial out with this rom. I get popup saying 'Unfortunately, Dialer has stop"
Are others seeing this problem? Is this an rom issue or a setup issue on my end?
I don't expect a daily driver from an early alpha of this rom and do expect issues but I would hope that I can at least make phone calls, after all, the Note 2's primary function is a phone
What I have done so far.
DL and installed rom twice. Both DL check via MD5 OK
Using Philz 6.07.9 recovery
1. Backup internal sdcard to pc
2. Factory reset / Install new rom option
3. Wipe/format internal sdcard
4. Reboot recovery (selected yes to restore root notification)
5. Install rom
6. Boot rom
7. Boot into recovery
8. Flash Gapps
9. Did minor setup of things like Wifi, Google Login, Play Store, DL ES File Manager.
10. Try to make phone call using dialer (phone icon) and get 'Unfortunately, Dialer has stop"
11. DL another free dialer from Play Store.. same error message.
I'm open to suggestions on how to get this to work.
I do like what I see from my little tour around this rom, but not being able to make calls is a major issue for me even for an alpha release. For now I have fallen back to my trusty Community Rom 4.4.2 which has been rock solid for me.
Thanks
bump.... a few people have viewed this posting .. anyone else having this problem? I have since try to install once again.. had some limited success with dialer, but then problem returns. even made a nandroid of when it was working.. still my favorite early lollypop rom for the l900
I installed Broken5.0.2, ran it for 24, and found it seemed to be one of the least reliable functioning loli roms for L900. I personally am preferring the LiquidSmooth 12-23 nightly. The LS rom has overcome the wifi/screen off hotboot bug, the keyboard bug, but still needs the manual GPS fix. Right now it offers hands down the most functioning options at this particular time and the phone is semi reliable??? Lol its doesnt FC but its buggy.
My two cents ... Cheers!
I've tried LiquidSmooth 12-23 nightly also.. one thing I had issues with was I have a OTG usb drive and did not find a way to unmount it. Did you find that function anywhere in LS?.. Other issue I have is no XPOSE support right now.. and I'm not a fan of the AOSP messaging pgms. Lots of things I don't like about TW .. but they make a nice messaging pgm
I did see a semi-workaround where you click on the carrier setting and it kinda resets the capability to make calls.. kinda hokey.. but it seems to work.. Lolllypop is still very early.. and I guess these are the growing pains for being alpha testers. Hopefully over time it will get more mature. Back on 4.4.2 for now.. everything works.. the thing is huge.. over 2gb nandroids using high compression.. but hey, everything works.. Thanks for responding.
Hello developers and tech geeks i am not a pro in these stuffs and sorry for my english too so here it is my problem When ever i install any custom recovery or Rom,my touch stops working... and after re installation of stock rom it gets perfectly fine. at first i tried installing CM 12 through TWRP and touch was in responsive at that time (twrp is a touch based recovery) then keeping in mind that cwm might work because of its hard button functioning i tried it too hence rom installed perfectly .. but again touch issue was there in CM 12.... i have never faced this kind of issue.. plese help...