Related
[Warming up]
I've been having problems lately trying to figure out the problem..
So, first i suspected the SD card, doesn't seem like my original 16GB card was the problem, because i bought 2 new 32GB Micro SDHC cards already, same problem..
[Now the problem]
80% of the times when i reboot and go into recovery and flash a couple of roms, or reboots in general, i for the most part get stuck in Bootscreen, if i try to wipe Cache and Dalvik-Cache, it sometimes solves the problem and 20% of the times i can get into the system, the other 80% of the times that i actually succeed into getting the rom to load up, i mostly get stuck there aswell, untill it reboots the phone, and im back at the imfamous bootscreen...
So, i've figured, is there anyway for me to log the stuff that is happening at the boot screen? because im curious to what the problem might be..
[The things i've done already]
Everything is formated as EXT4, and has been so since Mike introduced it with his rom..
i've tried Mikes rom, Unity, Honey roms, Coredroid, RCmix, all the same on all of them.
I always wipe my phone fully before i boot the rom, mostly with Mikes Super Wipe Script, but sometimes with the wipe zip mentioned from the Rom Dev explicitly telling me to use that..
I always let the rom boot 2 times before i start flashing themes and stuff..
Just going Stock rom doesn't help either, i've tried that aswell, no change.
I've cleaned the phone, from top to toe.. (brushed and cleaned with special liquid)
I've tried different Micro SDHC cards, 1 of em was a counterfeit card, the newest one works just flawlessly, i've benchmarked, checked for errors and even done a Bluff check on it, all working 100% nominal.
CPU running at 998Mhz, just incase..
[Ending]
So, does anyone have any suggestions?.. Does anyone have any way for me to get logs of the Bootscreen (as its a wallpaper, i have no chance in actually seeing what is happening)
Are there any ADB commands i could use to check errors in bootscreen? Any diagnostics tests?
Maybe even a way to refresh the Bootloader with ADB commands?..
ANY help would be greatly appreciated!!
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Have to agree on that
Do you still have warranty?
drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Thanks man, very much appreciated!
I'll run some logs tomorrow and see whats up with the phone, i actually got the phone running optimal again with yet another fresh rom flash and it all seems to work, have only restarted the phone 2 times, as im afraid of restarting the phone and get stuck again..
If i do get stuck, im stuck forever, and have to try above mentions i've done before, wipe cache and dalvik-cache, sometimes this works, most of the times it doesn't, and i end up fully wiping a couple of times and reflashing roms untill it works.. (I know this might sound like an SD card problem, but its not, i've gone thrue this with a couple of programs)
Anyway, a thousand thanks for that link, will probably help me quiet some..
madmaxx82 said:
Have to agree on that
Do you still have warranty?
Click to expand...
Click to collapse
Aye, this phone i have in my hands right now has already been in for repairs before and they changed the PCB of the phone, got a new IMEI number and all that..
But i do have warranty left for it, but i have to iron out the problem before i send it in, don't wanna risk being sent back to me and i have to pay lots of $ for their trouble (you know how HTC 3rd party repair centers works).. Plus they might actually scratch my screen some more as they did when i last sent it in...
Well, i have another "minor" problem with the phone aswell, not sure if its my phone or a general new cosmetic problem occurring on phones sent in for repairs, as i haven't noticed it on my earlier phone (Well theoretically the same phone).. Is that when i look at the screen in pitch black moving screens, i can see a distinct line going from Top Right to Bottom Left corner, and the Top Left side of the screen is black, and the lower right part of the screen is black/grey, you can see the difference, but not noticeable when your actually booted up, only in the Bootanimation part is it visible, i've tried different Bootanimations and everyone that has a Black background has this cosmetically problem.
Aah crap, Wall of text..
Haha just gonna add that i installed both apps you mentioned earlier, and the phone feels more like a Dev phone now, but anyway, it all worked great, not sure if it logged anything yet, didnt find anything in the app yet if it does..
I noticed something strange though, Gsensor Enabled, then right before bootup, Gsensor Disabled..
Have no idea why it does that, have no problem with Gsensor though..
Edit:
6 successful restarts!! That's something new!
I have no idea why its behaving this good.. Well time will tell..
(Tittle changed from *Phone won't boot with sdcard inserted*)
I woke up this morning and my phone was just dead over night. I thought well the battery just drained but no. First it wouldn't charge, no red led lighting up on the power button. After 15 min. in the wall charger and no sign of charging i hooked it up on my netbook. About five min. went on and then the red led shined and i thought yes and tried booting but just a vibrate once and a black screen.
I was running latest 4.0.A.2.368, rooted, unlocked bl, doomlord's kernel and @thomassafca's samsung theme when this happened.
Tested fastboot mode and flash mode all good there, blue and green light.
Then i re-flashed doomlords kernel and it rebooted to the point of *sony ericsson* on the screeen and went black and then the charging icon and orange led.
Took out the battery and inserted it again and booted up. Again only vibrate once and then black screen.
Then flashed kernel.sin with flashtool, still the vibrate once and black screen.
So i was a bit lost and took out sim and sdcard and flashed 4.0A.2.368 ftf file posted by @thomassafca and it booted fine. Then i turned it off and inserted the sim and booted up. It booted just fine. Then inserted the sdcard and again vibrate once and black screen.
Then formated the sdcard extFat still no boot, tried Fat32 no boot, tried a card from my old nokia wich should be formatted correct since it also run on a linux base (maemo) no boot.
I'm a bit lost on what to do to make my phone boot with sdcard again.
Have been working with no issues at all since i flashed the new firmware/unlocked bl/flashed kernel/rooted.
Any help will or if someone could explain what happened will be great
Regards Dousan...
e: Ok a slight change in this. The phone when turned of won't boot again unless i take out battery and insert again. When booted into the phone i inserted the sdcard and mounted it and now it boots with the sdcard, but still the same issue of having to take out the battery to boot when turned off?
e2: Tried adb reboot and it seems to go in a bootloop. It connects to the pc and disconnects (windows sound plinging connected disconnected) and i can adb devices and a connected device number appears after the first pling and after the second pling there's no device to be found with adb and then it just goes on and on till i disconnect and pull the battery and boot? All this is with a black screen not even *sony ericsson* appears.
e3: Reflashed it with the latest fw and without pulling battery it booted right up and i thought, yes, problem solved. Went through setup and then turned it off and booted the phone and still vibrate once and a black screen. Pulled out battery and botted again and still vibrate and black screen? So pulled it out again and sdcard and it booted up fine. Inserted the sdcard when on and mounted it and it works, but still the boot problem?
After the reflash the vibrate felt different, stronger, and after i pulled the battery it's weaker.
e4:Flashed doomlords kernel again and rooted, still same issue?
e5: Solved problem by flashing doomlords kernel v2 for fw 4.0.A.2.368. After flashing it booted with the kernels new boot txt and then it turned off and the charging icon showed. Then booted into cwm and wiped dalvick cache and battery stats. Then rebooted from cwm and it booted up. To make sure problem was resolved I tried 2 times in a row to reboot with quick boot and it booted without me having to pull the battery Thanks all for your suggestions
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
AndroHero said:
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Cheers mate for the surgestion, but that was a no go, didn't help
Back on 4.0.A2.368/unlocked/doomlord kernel/rooted... With a reboot problem
Regards Dousan...
Could be related to the doomlord kernel?
Sent from my R800
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Deoxlar said:
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Click to expand...
Click to collapse
Not likely as i only OC'ed to 1400 the first feew days i had the kernel and then 1200 and when it happened stock clock.
My incident is isolated and your point is?
@captain67, yes it might be related to the kernel, could be?
Regards Dousan...
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Dousan said:
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Click to expand...
Click to collapse
And it turned out that there was a point to it, problem solved
First post edited (e5
Regards Dousan...
Had the same problem
It was solved by magic though
Sent from my Xperia PLAY R800i using XDA App
And then the problem reappeared and this time i couldn't fix it myself and has just gotten my play back from service today (one and a half week they had it). It turned out to be some hardware problem and i've got a new screen, top cover and some other stuf.
Flashed the latest FW and locked the bootloader before handing it in and just told them what happened. Woke up and turned the device on and it froze and then it turned off with the backlight on. Tried rebooting but just a single vibrate and then a black screen.
They fixed my issue but created another. The volume button is now broken and i have to go back tommorow for a second time. Just booted the phone this evening and wanted to hear some music, but couldn't turn up the volume without pressing a pionty thing on the rocker. Down works fine. Bit annoying that a broken volume button can leave the service place, that should've been seen by the service person in the shop before it was ok'ed.
The screen is nice and crisp and the old one had a backlight issue i just lived with... untill now
Regards Dousan...
So a little update on this:
As i said they broke my volume button while repairing it for the stuff i wrote about above (didn't want to turn on).
It took me a week to go back with my play and in the meentime i descovered that it would randomly turn off during the night and wouldn't turn on unless i pulled the battery and charge it untill the charging symbol showed on the screen. It would then boot and first i thought it was the battery that was drained, but when on the lockscreen it showed that there was plenty of juice on. One time it was 35% and another it was 62% and no way it could've charged that much in 1-2 min.
Another thing i descovered was that when turned off it wouldn't turn on again unless i pulled the battery.
Anyway i went to pick it up yesterday and here i saw that they've broken my R-trigger Those idiotic service people even ticked of a box on the service papers that they've checked that all buttons where working (i don't think so, slackers). They did this on both occations
My play had no juice on it so i wasn't able to see if they had fixed my problem about not being able to reboot without pulling the battey and the random switch off's. Further more the service papers that came back with the phone didn't mention it at all? They did fix my volume button or atlest it seems they did as i couldn't turn it on and check if it did actually work.
So once again i'm without my play, but this time they're processing it express
Regards Dousan...
As long as you can use your phone,its all good
Cat_On_Droid said:
As long as you can use your phone,its all good
Click to expand...
Click to collapse
Yeah i know, I'd rather have them fixing it though, than having a fualty device. In the end it might go to SE and let them see if they can fix the issue. Hope not, don't want to be without my play once again Got the iches for gaming and now EA got free games, bummer
Regards Dousan...
Well just need to vent a little.
Starting rant:
So I got my phone back today for the third time. They did fix the R-trigger they recked the last time it was in for service, but they didn't fix my issue with the random rebooting/turning on without pulling the battery.
They claim it worked fine before shipping it, but when i unpacked it and let it charge enough to power on guess what it didn't turn on i had to pull the battery to get it to turn on lol They shipped it without checking if they fixed it. Hell i don't even think they tried at all cuz then they would've cought it straight away. They're full of BS and when googling them and reading their trustpilot it's also full of dissatisfied customors with the same type of problem as me, no fixing or pour fixing or even more breaking of the device or simply lieng it was water damaged
Hey that sound's familiar to me, not fixed and more broken, those C*NTS.
I'm pissed and nothing i can do but a claim with the place i made the purchase.
Rant ended
Regards Dousan...
End of story...
Well the last update on this.
I made a claim with cdon.com where i bought it and sent it of to their service center for repair and once again it was returned non repaired. Still wouldn't turn on without pulling the battery. Then they sent it of to SE and they couldn't fix it either and sent a new device to cdon.com, but i chose to get my money back instead of a new device.
The cons of this device ended up being more than the pros. Relly liked this device though and what it was supposed to've been. I was just not the big gamer i used to be and mostly played RB6 online and found the lag of analog touchpads support in fpse annoying and psxperia converter tool didn't work with the games i liked to play.
Anyway it was a fun ride while it lasted and mostly a friendly helpfull crowd I encountered here in the play sub forum. Must say that it has been the best forum I've been submitted to so far
Thanks to all of you and I might see you around
Regards Dousan...
What are you going to buy in the end?
Logseman said:
What are you going to buy in the end?
Click to expand...
Click to collapse
I ended up with the Lumia 800. The N9 seemed nice and have good specs and a familiar OS, but tried it out a few times in a shop and didn't get that wow feeling. Further more read a few things on TMO (talk.maemo.org) in the N9 sub forum that convienced me not to pick up the N9. Even read some danish users experience with the device and it wasn't good all in all. Though the N9 has it's openess and a lot of modding potential i didn't want to go for a 'half finished OS' as i see it from reviews from users. On TMO hardcore N900 users that shifted to the N9 was dissapointed in the N9 as it's gone more mainstream and comercial in how Nokia build the OS.
As of now the Lmia suites my needs much better and I do like the WP7 feel and looks.
It was hard to choose between the two devices as they both have good things going for them.
Regards Dousan...
Alright, here's the deal, this happened about a month ago (ive been stuck with the hero since lol).
I was running ERA EH06 Leak 1.1 (name of the file, i think it was the unnamed rom at the time) which was running perfectly for a few days until I get the google services etc force closes. Anyway I get home from work, I go to switch to stock and reflash to something else (at the time I was flashing roms like crazy lol). Anyway, as im odin'ing to stock, I accidentally pull the usb from the phone in the middle of it and the phone is stuck on the download screen, so I pull the battery and try again.
Now the phone isnt connecting to my computer, and its not even turning on. It wont show anything when I have it plugged into usb, I cant go into recovery or download mode. I saw on another thread a power cycle reset thing that didnt work.
I took it into the sprint store to have them see whats up and they said the usb was pulled off of the motherboard. I open it up myself (im semi experienced in this, and i found a good tutorial online) and nothing is noticeably wrong and the usb isnt pulled off the motherboard.
Also, the battery indicator is red because of "water damage" ( i have taken it in the bathroom with me as I showered, but that was only a few times and I stopped weeks before this happened, so I dont think water damage could be the main problem).
So basically has anyone else had the same or similar issue? Or at least can point me in some direction?
No dl mode? Try taking the battery and SD card out, and holding power and 1 THEN plugging it in still without the battery or SD. No odin then, well...
sent from my epic 4g. with the key skips.
holy s*** its in dl mode, i havent tried anything yet, but i didnt expect that lol
Lmao I assume you know what to do from there. But yeah, I always odin with the battery out after I found out you could
sent from my epic 4g. with the key skips.
Sweet, yeah I got it up n running, thanks yo! I looked up all over the place and couldnt find anything saying to go into dl mode then plug in the usb! Oh well its working now!
Okay so here is the deal. I just picked this sweet Epic up and started rooting it and I can't get it connected to the pc to get into the files. I set the phone to debugging, and even tried it with it off as well, then I connected the usb (and yes I tried alt cords too) to the pc and selected mass storage (I tried charging too). The pc says it's installing the drivers and even says completed and ready to use but on my computer screen it only shows my hard drive . I downloaded the starter sdk and tried those drivers as well. Even though I could not get it to recognize I started Odin and while phone was on it showed 2 ports, but once I turned the phone off and set it to download mode I get zero, zip, nada for ports available. Now I did see somewhere to set the code back to PDA and top to Modem so I did that as well. Still no luck. I am running stock Froyo EC05 2.2.1 and 2.6.32.9 kernel. Can someone please help me out? I had a Moment before this and never this many issues. Is there a way to just put the card in a reader and install the files and then put it back in my phone and run recovery from there? I've never had to do that before so I was wondering if it's an option if I can't fix this. Last thing is the charging time is way long and the hold isn't lasting long either. I'm no expert or developer, but I'm flashed many ROMs on my moment so I guess you can say I know a little. Please no tech jargon/lingo though to prevent unnecessary communication issues. Suggestions on GB ROMs would be nice too. I tried RandomKing but the links were no good. I hate the stock garbage on there and would love it if someone could help me get them off so I can continue with my rooting agenda.
Try with USB debugging on, connect to the computer then go into control panel and device manager, find phone entry, probably samsung android, then hit update drivers from Windows Update. Takes a while to load all drivers, sometimes more than 30 minutes. Then reboot computer and phone and try it.
As for ROMs they are ALL good. Read the description of each to find out what's in it and if you like it, try it.
Sent from my SPH-D700 using XDA App
Thanks for the reply. I tried that (unknown device) but I just keep getting windows has decided your driver is the best message when I even disabled, re-enabled, removed and re-installed all drivers. It's really bugging me and I'm not one to give up but I spent over 6 hours on this last night and I'm stumped. BTW what 2.3 ROMs do you know of that are stable with the least issues? Just suggestions of course as everyone has their own style...
Stick to the EG22 ROMs since EH06 and EH17 caused many phones to random reboot. After a few days EH17 started disconnected my calls. I have been using a ROM not listed on XDA. It is Bonsai B14 EG22 based. You can google Bonsai Android or click my signature. There are a few good ones in the development section here too.
Sounds like it is definitely a driver issue. There are samsung drivers floating around here. If you don't find a working set I will hunt them down tonight for you.
Sent from my SPH-D700 using XDA App
You can try the drivers in the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1052813
Thanks...
Cool I will try that out when I get home since work computers are usb restricted
Thanks for all your help and I'll update you tomorrow.
By the way I was playing a HD game on it today while charging and I got a charging paused, battery too hot or cold... Is this a problem with the EG22 build?
Another thing to make sure of is if your dial ##8778# it will bring up a menu, make sure your device is on pda.. believe it or not this helps some people
* PDA should be selcted under the USB Section.. the other section should be on modem
Sent from my old but still kickin Epic 4g
Yeah that's what I was talking about that I tried.
Now I did see somewhere to set the code back to PDA and top to Modem so I did that as well.
Click to expand...
Click to collapse
rooted!!!
Got Odin working and downloading now... Had to sneek my laptop into work to get her done but... LOL... Now time to get rooting!!!
Thanx guys... Will let you know what ROM I went with later today...
Working on putting on 2.3.4 EG22 v. Alpha "Hawk" [Journaled] EG22 AIO Volume/Hotspot/Lockscreen/Overscroll/Lag Fix but the download is taking over 2 hrs!
Phone isd not working at all now...
I put it through Odin and was following the prompts on the odin page that said to put victory_8G_100528.pit in pit and the tar in, hit start it went through and said something about partition and then the phone shut off and never came back on. It won't even charge now... NO life at all.
Fixed...
Okay I took the battery and sd card out, and then plugged the usb in while holding 1 & power down. That put it into download mode. From there I just put the battery and card back in and installed clockwork. BTW the only cord that would work was the one that came with the phone. Took me 12 hr to figure that one out because all the forums said to not use it. UGH
Thanks for all the help.
Also watch out for launchers that hide you notification bar, this can bork USB/sdcard detection, I just made a tip thread.
smartbeatz said:
Okay I took the battery and sd card out, and then plugged the usb in while holding 1 & power down. That put it into download mode. From there I just put the battery and card back in and installed clockwork. BTW the only cord that would work was the one that came with the phone. Took me 12 hr to figure that one out because all the forums said to not use it. UGH
Thanks for all the help.
Click to expand...
Click to collapse
There is a manufacturers cord that is the same connector but doesn't work, not sure which one but I use my old Palm Pre cable and a lot of others use Blackberry cables.
Oh so nice
Okay the new ROM is running great and is oh so sexy, fast and powerful, although I do not like the home page dock layout. I see no issues yet and I'm switching back to the Epic today after I beef up my old moment (which I had swapped to for the day because I thought I soft bricked the Epic beyond recovery) I promised to my mom. I'd like to find a stable GB build for her too but it doesn't look like the programmers have figured that one out yet.
BTW the cord I have is the one that looks a little weird on the end you plug into the phone and seems to be real stiff. I got more phones to mess with so thanks all...
Anyone know of any good tutorial sites that teaches how to develop and write codes? Flashing is one thing but getting to know the nuts and bolts to help others out is where I want to be.
so ive had my s2 for a couple years, i wound up dropping it the other day, threw it into a constant reboot.. seemed like a power button issue. i tinkered with that a little but little results. i was able to get it to boot up and did a twrp backup of everything. but since then ive been unable to get it to run for anything more then that, IF even that long. a factory reset aswell locks up just after app optimization. its like.... it get to a certain point on the phone and locks up.. i was able to pull my misco-sd out and get the files off it. but i'd like to get to my internal storage as thats where my camera was saving eveything too.. when i switched roms earlier this summer it must have used different save to locations.. its my photos are what im after.. booting into recovery i can see all my files, plugging in and trying to mount yields no results.. im going to try on my laptop aswell but on my pc its doing nothing.. Im curious if anyone has had the similar situation , near that, or better luck with CWM.. any other info or insight would be awesome.. much thanks..