Well, I have this device with problems a few weeks ago, it was working normally, then it unloaded and hung up, when I put it to load it took a while to connect, but after a few minutes it turned on but in infinite loop ... So I thought I burned the room stock, I did that, and it installed everything right, but it did not change anything, it installed the TWRP 2.7, I tried to make the wipe and burn others room, but it did not continue the same way. I tried fastboot, rsd lite, sdcard, and everything and nothing. I tried to install a new version of TWRP, it says it installed everything right too, but when it opens it continues in the same version. When trying to make the wipe dalvik cache the error.
In short ... I install the rooms normally and nothing happens, the same with other recovery.
I think I lost the device forever, please help me.
Sorry, I'm using the translator. Thanks for reading this far.
marcosjord said:
Well, I have this device with problems a few weeks ago, it was working normally, then it unloaded and hung up, when I put it to load it took a while to connect, but after a few minutes it turned on but in infinite loop ... So I thought I burned the room stock, I did that, and it installed everything right, but it did not change anything, it installed the TWRP 2.7, I tried to make the wipe and burn others room, but it did not continue the same way. I tried fastboot, rsd lite, sdcard, and everything and nothing. I tried to install a new version of TWRP, it says it installed everything right too, but when it opens it continues in the same version. When trying to make the wipe dalvik cache the error.
In short ... I install the rooms normally and nothing happens, the same with other recovery.
I think I lost the device forever, please help me.
Sorry, I'm using the translator. Thanks for reading this far.
Click to expand...
Click to collapse
Can you put a better explanation and say what rom you were using and some more info would be nice. Also was your bootloader unlocked when you flashed TWRP.
Related
Yeah, i finally made it. I bought a TMO-DE One S (With S4 Processor) 5 Days ago, unlocked the Bootloader (HBoot 1.09), rooted and SuperCID´d it, installed CWM Touch and installed TrickDriod V8.0 incl. its Tweak Package. After that i installed another Radio and everything was fine. It could have been SO easy, but i just HAD to do more, and now its soft-bricked.
At all TrickDroid is a really good ROM, but i hated the thingy that it shows G symbol instead of H when getting HSPA speeds. So i decided to dump it and go for a 4.0.4 / Sense 4.1 Stock Rom without branding instead until a JB / Sense Rom comes out. And thats were the trouble started. i flashed the stock rom with CWM, installed the boot.img that came shipped with it and booted it up. I did a full wipe before flashing. It booted up, Sense Stock Background Image came on and it showed "Unfortunately Wiper App is closed" at the "Preparing phone storage" stage. After OK´ing that another Screen came up about some system service wouldnt respond (dont know the exact Text anymore) wich i could close or wait for it. No matter what i do, or if i do nothing, after ~20 seconds the phone crashes and restarts. After the first restart the phone only boots into a black screen but with the Android bar at the top is working with time, battery-charging and a warning smybol. But the Phone wont react to anything i do except for lockscreen button. When its "online" i can push files via adb to the internal SDCard so i thought it wouldnt be a big problem. i pushed ONE MaximuS V2.5 ROM to the SD Card, booted into CWM and installed it. then flashed the boot.img of it via fastboot and booted it up. but nothing happens. still black screen with bar on top and not reacting phone that reboots every 20 seconds. i allready tried full wipe, cache wipe, dalvik cache wipe and i dont really know what to do now.
A broken SD Partion cant be since i can push files via ADB to it and install them with CWM. But whatever i try to install every ROM boots only in this blackscreen. its clearly not hanging in bootloader, but in android itself. I dont really know what to do, and returning to my dealer is no option since Rooting, SuperCID´ing and flashing another ROM. You maybe have a Idea what to do now?
Peace
TK
PS: Sorry for my bad english, hope you can understand it
Edit: Okey, i got something. i formatted everything i could in CWM, and now (as its now supposed) it hangs in bootloader since no system is there for booting. The good thing is in CWM i get ADB Connection so i can still push files to the SDCard. Im now trying installing a ROM again. So at least i have a starting Point if it fails again
Edit 2: Okey, found it. The "Stock" ROM is broken, not my Phones Fault. and MaximuS just doesnt install right so nothing was changed. Installed TrickDroid again for testing and everything is fine again. Close this one...
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
I'm just gunna give you the whole story.
I'm using TWRP Recovery.
I'm coming back to my d2vzw after a couple weeks of not using it (I got a different phone through work). I'm now back to using my GS3. I decided to update to the latest ROM version. I installed the slimROM stable that was just released, it was slow and they animations were choppy (which is really weird for slim). So I decided to try a different ROM. I've used carbon before, and I really like active display and HALO, so I decided to install that. It installed just fine, installed all my apps, rebooted. It froze on the initial splash screen, didn't even get to the boot animation. So I figured it was just a bad install, so I formatted and flashed from my external SD. Again, first boot just fine, then froze on second boot. So I put a https://plus.google.com/+AlexKruger/posts/dJGXsrAZvj4 in the ROM's community. They suggested that it might be a bug from installing it from my external. So I formatted, then moved the files over to internal, and flashed again. It booted fine, I got to the home screen and restarted before I did anything else. Froze, again. Then someone suggested, that I format, install it, boot all the way, reboot into recovery, wipe cache/dalvik and dirty flash from internal storage. Did it, froze on reboot. So I formatted one more time, and went to boot into recovery while figured out what to do, I accidentally booted into the system. It booted just fine, I went through the set up and activation screens, and it worked. So I rebooted, froze. Then someone suggested I switch recoveries, so I installed the latest CWM recovery, and tried everything all over again, still freezes on reboot.
I know I could just use a different ROM, but it's gotten to the point that I need to fix it. I want to get it to work because F*** you.
Please any help would be appreciated. Thank you.
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
Hi there!
After about a week ago, I’ve turned off my Note 3. Then two days later, when I wanted to use it, I’ve turned it on. After CM logo appears, its says:
“Android is starting
Optimizing x apps of x”
I know this is because of ART, but after it finishes, my phone reboots, and CM logo appears again, and nothing happens. After a while, it starts optimizing apps again. Now I left it for 2 hours, my phone didnt boot up.
What should I do? I didnt flash any new kernel, rom, recovery or anything else. Im on CyanogenMod, with CWM recovery. I dont want to factory reset, because of my photos and videos.
Even I tried to start in safe mode, but I couldnt get to it, and Im not really sure that I tried to enter safe mode properly.
Please help!
Just dirty flash the rom again through cwm.
See if it works
It's high time you flashed TWRP already.
Bence98007 said:
Hi there!
After about a week ago, I’ve turned off my Note 3. Then two days later, when I wanted to use it, I’ve turned it on. After CM logo appears, its says:
“Android is starting
Optimizing x apps of x”
I know this is because of ART, but after it finishes, my phone reboots, and CM logo appears again, and nothing happens. After a while, it starts optimizing apps again. Now I left it for 2 hours, my phone didnt boot up.
What should I do? I didnt flash any new kernel, rom, recovery or anything else. Im on CyanogenMod, with CWM recovery. I dont want to factory reset, because of my photos and videos.
Even I tried to start in safe mode, but I couldnt get to it, and Im not really sure that I tried to enter safe mode properly.
Please help!
Click to expand...
Click to collapse
Ahh I would suggest you to get TWRP, The world has moved on and I think you should too! It's just a little better at things overall. TWRP can be flashed through ODIN. As for the Bootloop, try dirty flashing the ROM. Just wipe the dalvik/ART and cache and leave the rest as it is.
Dinara° said:
Ahh I would suggest you to get TWRP, The world has moved on and I think you should too! It's just a little better at things overall. TWRP can be flashed through ODIN. As for the Bootloop, try dirty flashing the ROM. Just wipe the dalvik/ART and cache and leave the rest as it is.
Click to expand...
Click to collapse
What do you mean on “dirty flashing”? Do I lose my data if I flash my rom again?
Bence98007 said:
What do you mean on “dirty flashing”? Do I lose my data if I flash my rom again?
Click to expand...
Click to collapse
No you don't, dirty flashing = installing the same ROM without wiping or resetting any data sets, just reflashing that zip again, JIC some files got corrupted, if that doesn't help you might have to give it a fresh start.