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.
Related
Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.
Hopeful bump =)
Hi all,
I own a Desire GSM version and been running a pre-rooted stock ROM for quite a while and have been very happy with it. I have been running this with an ext3 partition and ran app2sd+ script to make use of it. All good.
My sense of curiosity got stronger and always wanted to try a custom ROM so I tried Cyanogenmod 7 RC1 on Monday.
I have been running the latest Radio (32.49.00.32U_5.11.05.27) so didn’t have to update that for CM7.
I formatted the DATA as well as the CACHE before flashing the CM7 ROM, then applied GAPPS to the ROM then restarted the phone.
All went OK and I loved this new ROM, except that I have been experiencing very strange connection issues whether I am on WiFi or 3G (Vodafone AU). The phone will establish connection; however sometimes will not be able to get data out of a request as simple as getting emails, opening a webpage through the stock browser etc …
The workaround to that was to tun off wifi and turn it back on, same for 3G …
I re-flashed numerous times the ROM (formatting the CACHE/DATA each times) but was still experiencing these issues, when sometimes I couldn’t even set my Google account at the first start of the phone…
After a couple of days of scratching my head I did find a potential solution that was suggesting updating the /system/lib/libhtc_ril.so file with the one provided in the nightly build. This had no effect what so ever to the situation.
I then decided to go back to FroYo () so re-flashed the pre-rooted ROM, but then I experienced the exact same issue!! I then re-flashed the Radio ROM thinking this may have been affected by all these changes but no changes at all …
I am a bit at a loss here and don’t know how to fix that really …
Is there any setting that resides on the phone relating to Radio ROM even if I format both Data and Cache each time I flash the ROM??
Thanks for your help guys.
Any ideas on this issue at all ??
I noticed that in every single ROM thread it says to wipe data and factory reset before flashing..
but one time i forgot to do it and just wiped cache then flashed a new ROM, and so on, and so on..
After i booted my phone i noticed that all my data and settings was exactly how it was before i flashed the new ROM..
i have done it this way with Juggernaut 5.0 and SlickMod 3.6 RC1 and never experienced a bug or anything unusual by doing it this way.. (although every time i tried an ICS ROM I followed the instructions perfectly)
it sure saved me a lot of time setting up my phone again
my question is ... has anyone seen bad results by doing it this way?
Theres more to it than that. The problems arise when you flash system data on top of another rom's system data. The ROM maker may have put tweaks in that mixed with another ROM's tweaks could cause unwanted effects. For example, TDJ builds his roms and kernal specifically for his roms, and states if you use another kernal his tweaks wont work.
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.
So I've recently been having an issue with my phone that I haven't been able to fix through various standard fix methods. I've tried searching for this exact issue but the only thing that seems to work for other people (albeit they were on different devices when they had this problem) hasn't fixed my issue.
Long story short, I went from SlimROM 2.2 (and many other 4.3 based ROMS) to ForkMyLife 4.4.2 to try out KitKat, and I eventually wanted to go back to SlimROM.
I always full wipe (System/Data/Cache/Delvik) and then flash my ROM (in this case it was Slim), a reboot netted me a bootloop/boothang on the bootanimation. Wiping Cache+Delvik cache will get me to Optimizing Apps, but then it hangs at Starting Apps. At which point I can battery pull, restart, and it will restart just fine (typically, I did have one time where this didn't work). But I'd have to do this series of events every single time I reboot. I've tried multiple ROMs, multiple kernels, but everything ends up doing the same thing after a reboot. I've even done a full Stock 4.2.2 Image flashing (full SDCARD/DATA wipe an everything) using mskip's Toolkit, re-rooted and re-did my entire phone to Liquid 2.37 booted up the first time no problems, but the boothang was back on the very first reboot.
What is somewhat odd to me, is that I can run a 4.4 based ROM with no boot issues though. I ran FML 4.4.2 for a few days and numerous reboots, and the same for OmniMetal 4.4.2 to see if it would lead to any boothangs and I had no problems with either.
Any ideas or thoughts from anyone on why reverting back to 4.3 after a 4.4 ROM would cause so many issues?