Related
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.
PAST SITUATION
I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.
PRESENT SITUATION
This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.
HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.
WHAT I TRIED TO FIX IT
1) A clean installtion, did a task 29 and installed everything again. Same problem happens.
2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! Even with that version it still gets stuck on the Android logo screen.
I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
did you get things sorted?:cyclops:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
I'll post my results here soon.
SpoonyVoid said:
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
Click to expand...
Click to collapse
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
SpoonyVoid said:
Well not yet. I am working on it. Does anyone
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
Click to expand...
Click to collapse
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.
WHAT I DID THEN
I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.
So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.
Nigeldg said:
Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
Click to expand...
Click to collapse
Thanks for the reply. I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.
And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.
I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated.
I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant I don't have any actual experience with Windows Phone though, so I wouldn't know.
As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
SpoonyVoid said:
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
Click to expand...
Click to collapse
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Nigeldg said:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Click to expand...
Click to collapse
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
SpoonyVoid said:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
Click to expand...
Click to collapse
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.
As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
Sent from my Nexus One using xda premium
A logcat would be really useful when:
-ever your ROM gets stuck after a reboot.
- You face any random force close.
I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.
Was the market working prior to this problem?
Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)
You could also give cLK a shot, and see if the problem persists.
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse
Hello all.
I was having major crashes and issues with the latest two versions of the Samsung OS, so I decided to use CyanogenMod... Well, that didn't go too well; I had issues with the camera and Youtube apps which made them unusable (others weren't suitable either). I had a number of problems with how apps and the OS worked and couldn't find solutions to all of the problems, so I decided that I'd go back to the stock firmware, but from a few months ago before I had any issues.
So, as I've done before, I plugged the phone in, opened ODIN and selected the official ROM that I downloaded, started the thing and 10 minutes later, I was back on official firmware. But I kept getting "Google Play Services has crashed", along with a couple of other services occasionally crashing too. So, I tried stopping the Google Play Service and somehow made it worse.
Not only that, but it didn't seem to clear anything; all of my apps were still installed, all of my files were still there and I think that may have had something to do with the crashes.
I guess the above two issues were something to do with the fact that I went from CM on 4.4.4 and went back to Official on 4.4.2.
So without doing any research, I just decided to press "Nand erase all" and tried again, thinking that it might simply wipe the old OS and data. Now it's stuck at the SAMSUNG logo (starts just fine but stops after a second or two). So, I went to Google!
I found a few threads with similar issues, but I can't seem to find things that have a solution.
This one seems most helpful, but I can't find any "PIT" files, or anything of the like.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
What would you experts suggest?
Thanks in advance.
Do you even read before you start messing with your phone?
All the errors you had could be solved by wiping properly in the recovery.
You can find the .pit file here.
http://forum.xda-developers.com/showthread.php?t=2265477
I would suggest following the same steps as the member in the thread you posted.
Lennyz1988 said:
Do you even read before you start messing with your phone?
All the errors you had could be solved by wiping properly in the recovery.
You can find the .pit file here.
http://forum.xda-developers.com/showthread.php?t=2265477
I would suggest following the same steps as the member in the thread you posted.
Click to expand...
Click to collapse
Thank you. Unfortunately, no, I didn't read much. It seemed so simple; perhaps too simple.
I shall just try it now and see how it goes.
EDIT: Works perfectly now, thanks!
Original thread "https://forums.oneplus.net/threads/root-op5-twrp-dissaster.742632/"
Video of current STATUS "https://youtu.be/GBWbid59f1E"
Current state of my problem -- STUCK in a screen at Drive Screen "an empty modal opens" Also looking for -- OnePlus 5 OxygenOS 4.5.15 rom --
OP5 EUROPE (if this helps to know what kind of phone I got, I know there are some differences in countries, dont know if it happens with OP specifically)
Currently trying to fix this using:
twrp-3.2.1-0
OnePlus5 Oxygen 4.5.15
-----------------------------------------------------------------------------------------------------------------
After reading plenty of other Threads with similar problems, I am clueless of whatelse to do but to exhibit how I disgraced my phone in hopes for somebody to help me.
I know I am 100% guilty of all that happened but I still somehow hope to get help.
Now the proper what happened.
After the purchase of some apps that seemed to encourage me to root my phone from Android Store, to get more features, I decided to give it a go.
So I got myself:
twrp-3.1.1-0
The Rom from Cyanogen
SuperSu v2.79-20
Granted myself access to booting and usb debugging after becoming a developer (granted by the university of tap your phone screen like a monkey smashing buttons, I figure this is even an inside joke from actual Devs)
I followed a tutorial that said next thing was installing twrp and stuffing my rom and my super su in my phone after rooting it, here is when things turn dark after installing the rom.
I saw my data was wiped and thought I had erased its memory, and instead of just putting back the things that I had to install I clicked on another tutorial of a had that had a similar problem (I can provide links later if requested).
In this tutorial the person, said that I should go to Advanced Settings -- WIPE and try and reformat my SYSTEM and my DATA, (heres when I wish my future-self would have come and stopped me because after this it all spiraled into madness)
After this happened my phone said I had no OS, so I didnt know what to do, I had no idea, I tried recovery mode but there was nothing to recover.. , I tried plenty of things really. reformating, downloading more ROMS , when I tried to install any of this Roms a new surprise awaited for me, my phone didnt know it was a OnePlus5 anymore it decided asume a misterious identity now he was " " instead.
I googled this, and a guy had a work around in wich I had to go into the rom and into the META-INF --COM -- google -- android -- updater-script
and inside this very archive delete the script that validated wich phone I had, this solution wouldnt work with any rom I had because they all said "updating the img was unsuccesful" at this point I was asking myself only one thing "WHAT IMAGE?!?!" a second ago there was no OS at all and now there was an image to update?.
I kept trying roms until one worked the stable official version, now I managed to install the rom rebooted, to find that the OS seems to have been installed, but.. when I introduce my pin things begin guetting funny again...
My SIM doesnt seem to be recognized its called "Slot 2" and when I enter the pin it and "SWIPE UP" as the phone suggests it gets stuck at a panel called "Drive".
I am guessing I am having an issue with the drivers but this is only a guess, I really have no Idea how to fix this, I tried to look up if somebody else was strugging with a FREEZE at DRIVE.
but it seems that nobody else fell into the spiral of foolishness I did, please help me find a way into a solution.
When I try to recover from the phone and install from "internal storage" doesnt allows me as there was no such thing.
use codeworkx twrp
Use a Keurig and just breathe
try flashing a twrp recovery. then boot to recovery. then push via adb a recent oneplus rom. then install the rom. then reboot to system and see if it is working.
G'day all,
Hoping someone can help. (firstly I've searched on here over and over and some things have really helped, but can't find this issues on here)
Samsung Galaxy S4 GT-i9505 (originally with Vodafone rom)
Back story, I managed to put google rom via WINTEAM at some point in time (I don't recall how I did this now) this file - crdroid-6.0.0-20151208-jfltexx.zip (I still have this but not a md5 file)
Anyway, I wiped it under settings and basically stuffed it right up. Loops on WINTEAM (this part I had found in search and downloaded Odin3 v3.13) and Samsung Rom and a couple of others.
I9505XXUHOJ3_I9505VAUHOJ1_I9505XXUHOJ3_HOME.tar.md5
I9505XXUHQK1_I9505MAXHQK1_I9505XXUHQK1_HOME.tar.md5
I9505XXUHOL3_I9505TELHOL2_I9505XXUHOL3_HOME.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
The last one actually fixed up the google install but was hoping to place the original Samsung ROM back on and now it doesn't help at all when I run again.
The top 3 are Vodafone, Telstra and Max a forum had suggested (from a page on here somewhere). All of these say pass in Odin3 when installing onto phone. But once it gets to the Samsung with what looks like dots shooting out from the word it never gets past this at all.
When I power up the S4 phone, to get to download screen. I have volume up to download or volume down to restart phone. Some places I've read say to select wipe, I don' t have this option at all.
I saw an option to install s8 rom to s4 which I would like to do, but the how to do that requires working software first and install TWRN or something like that.
I'm not sure if this will run fast or ok on this phone, but it isn't a MD5 file either.
I would like Samsung ROM back on as it (for me cleaner than google or maybe just what I've been used to). I'd like to give to my youngest child as their first phone.
I also had tried to place zip files and also unzipped files on the SD card on the phone, nothing worked for me as it looks like it is expected ODIN3 to work.
At this stage of the day, I would just like to have it functioning again with anything that works.
Any advice on what to do now would be greatly appreciated, also I'm truly sorry if this problem has been documented, I really did try to do my research first before putting this up here. I've been on this for weeks now
So quick update. through more research, I have managed to install TWRP and now have access to additional utilities through WINTEAM. I've now tried to install ROM through the Micro SD card.
I think it comes up with a mount error, but has rebooted and still stuck so can confirm just yet.
I've managed to go through the entire process of installing the PurifieD+ROM+v3.5.zip through the micro SD card in the phone. Asked me about all the options etc during the install. There didn't appear to be any errors at all. Asked to reboot. etc....
I even had sound on the bootup, Now I have the Samsung word on the main screen with a blue backlight just flashing. Been like that for nearly 10 minutes. Not looking good.
Have I got bad memory or am I doing something wrong?
I managed to do a wipe after I did an install and it booted up find. I had no WiFi but than installed the vodafone install that should be the original and all works now.
The amount of time I had been working on this, I really didn't think I was going to get it going. I honestly thought I had some hardware error going on.
In the end it runs now, I can setup and had to my child
so I've managed to now use several different ROMs but now I can't root the phone (it should be able to, has been before)
When I run Motochopper I get this error
error: only position independent executables (PIE) are supported.
Seems to happen no matter what rom I've installed. I can't seem to find an older rom running android version 5.01 now
Any help on how to root this. Would be great
Now says it has been rooted, but I do not get the teamwin boot menu option at all. more like just a text style menu for wiping and loading other roms.