NVM didnt see it in dev when i looked (please delete) - Verizon Samsung Galaxy S III

So I have been bouncing back and fourth between jellywiz and my stock nandroid (whatever the latest JW on the weekend and stock so I know I have no issues during work week)
Just getting ready to crash and I pick up my phone and clockwork is running and trying to flash something and keeps repeatedly failing... WTF?? Last I had touched it was about an hour ago and was playing amazons FAOTD from 2 days ago. Nothing else.. didnt hit anything, touch anything, just sitting there plugged in.
So I mash the no button on clockwork becasue its asking me if I want to try flashing again, and reset the phone. When it powers back on and fully boots up it tells me software update failed (much like an OTA message)
Everything else seems fine, but im just curious as to OTA or WTF becuase I have never had a phone that booted into clockwork by itself and attempt to flash something.

Yes, there is.....
Here is one of a few threads: http://forum.xda-developers.com/showthread.php?t=1887081
Check the General section.....

Related

[Q] Gingerbread will not install

i dont know what im doing wrong but last week i could install gingerbread with no issues other than the market. because of the market issue i use NVflash to go back to square 1 and start over. so i installed VEGAn 5.1.1 with no problems. after about a day i was reading up on other gingerbread roms so i went to try one and it would install but never finish booting. so i nandroid back to were i was and try the rom i had before with the market issues, that one didnt work either.
what am i missing?
ps i cant get logcat to read any farther than from recovery.
in recovery logcat says "/sbin/sh: logcat: not found"
[solved] got it ^.^
ok dont know what the [email protected]# i did but i got it working.
for any of you that care on how it started working its going to be a long post.
basically on my quest to fix this damn thing i decided to use nvflash which didnt work the first 5 times, so i used the original recovery image rather than the rooted one. that semi-bricked it so it would only boot into APX mode. so after an hour of searching XDA i just flashed the enhanced image (like in the guide on the dev forum) and holy crap it worked and installed VEGAn 7 without updating.
dont know how it fixed it but it did.
Mods can you please delete this thread

MIUI 2.3.5 1.9.23 - No soft keys after succesfull flash

Appologies for not replying to the original MIUI thread. I am not a new user and i am very experienced in flashing roms etc, especially on samsung devices. I have been around for a while now but this is my first post so i cannot post in the dev section yet.
Last night i flashed MIUI to my infuse. I followed the instructions in the op here exactly.
http://forum.xda-developers.com/showthread.php?t=1278053
I had no problems flashing and everything was successfull, however there were 2 major issues. First being the soft keys. The four buttons menu, home, back, and search buttons did not function at all. They werent even backlit. The volume rocker and power buttons functioned fine. I reflashed from blue cwm twice and still nothing.
This is where i ran into my second issue. There were no posts about anyone having the soft key issue however i did notice alot of people losing their recover and being stuck on the samsung boot screen. This eventually happened to me.
I went to samfirmware and downloaded 2.1 and odin'd it, then odin'd the community kernel to get ext4 and red cwm then restored my nandroid so i am back to normal. I wanted to post about my soft key issue but as i said i had to post in q&a due to my lack of posts.
Any suggestions? if not, i at least wanted to inform the dev of the issue.
Thanks
have you tired CM7, just asking cuz they have almost the same bugs....so i would curious to see if your softkey issue transfers to that rom as well. and if not........
i would try loading up CM7, wiping from the orange CWM and flashing MiUi from there. it Should have worked the way you did itk if you were coming from stock. but who knows maybe seeing if it happens on Cm7 will lead to your answer.
just an idea though
no i havent been able to try cm7 yet as i dont have a build environment set up anymore and havent seen a release yet, would love to give it a shot if someone wants to send me a zip.
i really hope it doesnt have the same issue or ill have to donate this thing to my fiance and get a gs2 or something lol.
Check your mail, you seem to know what your doing so test it out see what happens.
Happy Flashing
Happy flashing indeed, thanks for this im going to give it a go right now, bbl with results.
Hell the only reason i was flashing miui to begin with is b/c i am currently unable to build cm7 so hope this works..
Thanks a ton!!
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
powdered_donuts said:
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
Click to expand...
Click to collapse
Glad it all worked out.....

[Q] jt's ICS v4 reboots to endless nonrecovery loop

getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
You're asking this at the wrong forum dude. You wont get any support here. Everyone's moved to Rootzwiki
http://rootzwiki.com/topic/15859-ics-b4-was-100-rebooted-and-bootloop-on-samsung-logo/
Yep but when fishing it helps to have multiple lines in the water...
Past experience
From what ive found out, once you have ICS flash on ur phone, ur not going to want to use the three finger salute. If you want to boot into recovery, only do it by rebooting into recovery through ics

My phone fail flashed and I can't get into Recovery, can someone help me?

I don't know what to do next, and I need my phone. I can answer any questions, but I wouldn't know what to start with. Can someone help??
Quick questions to answer:
1. What Rom were you on prior to flashing?
2. What Rom were you flashing to?
3. What do you see on your screen?
4. Do button presses give any reaction?
1. http://forum.xda-developers.com/showthread.php?t=1136128 v5.0, it's Gingerbread.
2. I was flashing to CM7, but it didn't flash, so I did what was probably a mistake and went straight for http://forum.xda-developers.com/showthread.php?t=1625619&page=1.
3. I see "DevilKernel" Samsung Galaxy S.
4. If I hold down the volume and power buttons, the DevilKernal boot screen will flash. If I keep the power button held down it resets, if I don't it just flashes and nothing else.
By the way, thanks.
Ok, here's what happened:
The first bootloop you were seeing with CM7 is actually a normal occurrence. You usually have to flash CM-based roms twice to get them to "take" (the first time sets up MTD over BML, the second time installs the rom).
What you're seeing now is the devil kernel trying to load up the CM9-based system, but not having all the parts in place.
Thankfully, you're not in that bad of a place. The easiest thing to do right now is to grab an Odin- or Heimdall-based one click Gingerbread stock package without bootloaders. There's a sticky in the Development section that has them, or you can grab the one in my signature.
Flash the one-click, go to recovery, and flash either CM7 twice or TWICS twice.
That should fix you up.
When I tried flashing the CM7, it said it failed. I'm not sure what went wrong. The TWICS I planned on flashing twice, but it got stuck.
Hard to say - it could be something as simple as a bad download of the flash file.
But you think if I Odin it and try TWICS again it'll work?
It should. Doing the Odin one-click will reset everything back to a factory state, which should remove all the obstacles that would normally stand in the way of a successful installation.
Hey man, for that ROM, this theme will work, right?
http://forum.xda-developers.com/showthread.php?t=1095911
I don't know anything about themes. Or this, apparently. I also got into Recovery and installed it twice, I don't really know what's going on.
So you're now fully set up with TWICS, or you're saying that it's still misbehaving?
Also, that theme should work - I had a CM7 theme that I was able to use with a CM9 rom's theme chooser. Wasn't 100%, but it generally worked.
I'm not sure WHAT is going on. The ROM seems to be working fine, I am reinstalling my apps from Titanium Backup and a "Low on space" popup is here, but that makes no sense since it's the same phone, it's a smaller ROM, and a 32gig SD Card. I also just got a text message that was "rejected due to low space".
What is going on??
It seems my phone always is unable to continue once Super Monkey Ball 2 tries to be backed up.
Look around in the cm7 thread for the dbdata full issue. I think there were some suggestions for how to deal with it in there.

Phone acting really weird (HTC m7)

Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.

Categories

Resources