Related
First and foremost any help will be appreciated.
Just got my sprint Sph-D710 galaxy, used the one click Odin EL29 stock kernel to root, everything is fine phone is rooted, tested rom manager and it asks for permission, but when i go into recovery it stops a quarter of the way and it goes into the triangle, the phone lets me hit the home button and it goes into some type of recovery but all the options it gives are reboot, wipe and partition, install from sdcard shows nothing in the directory??? any ideas on what i did wrong? Thanks again.
ROM manager is pretty dodgy on this phone...
I'd do some more reading... get to where you have a kernel with cwm recovery built in on your phone (sfhubs auto-roots should be able to get you there, from there I personally recommend the rogue kernels if you want to venture a little farther from stock), manually booting into recovery yourself, and maybe even a rom that gives you the option to boot into recovery from the power menu. (Calk's ROM is a VERY good, stable, close to stock ROM).
Final word of warning -- be very skeptical of the CWM touch recovery (and the "hitman" rogue kernel that includes it); I've read more stories of bricked phones related to the touch recovery than anything else I've seen on the e4gt. It's hella cool to have touch interface in recovery; I ran it myself for a while, but... caveat emptor.
Did you flash recovery while you were in ROM Manager?
---------- Post added at 06:31 AM ---------- Previous post was at 06:27 AM ----------
And what ROM/kernel did you put on?
Yes i did flash recovery from rom manager
Stock EL29
Jt_hatch so its safe to just flash a different kernel even though they all advise a nandroid backup?
After using one-click Odin did you use the Auto Root Package to put CWM on? But ya I agree with Hatch Calks got the best stable ROM for our phone. I absolutely love it. Here's his directions:
http://forum.xda-developers.com/showthread.php?t=1332837
Don't forget to use his Format All zip file first.
Crap, i really wanted an Ics themed rom, there's a couple that use the format all zip from Calks but im terrified that once i place them on the sd card or flash with Odin they won't show up in my recovery, ah forget it i guess ill do the rom first and then worry about recovery, thanks a bunch guys
..... actually i need a custom recovery to flash that rom
back in the same hole
cast466 said:
Jt_hatch so its safe to just flash a different kernel even though they all advise a nandroid backup?
Click to expand...
Click to collapse
If you don't have a custom recovery (i.e cwm/rogue) then you aren't going to be able to make a nandroid...
my memory of what I did was sfhub's autoroot, then adding cwm recovery (again via the autoroot), then I went to calk's ROM, then I was off to the races (rogue stock repacked kernel w/ recovery, then gunslinger w/ rogue recovery...) That was before the EL29 OTA but I'm pretty sure sfhub's process is updated since then.
Why do you want just an ICS theme when Calkulin has ICS? lol It's still a little buggy but it's pretty solid in the end and he's only going to keep working on getting it better.
http://forum.xda-developers.com/showthread.php?t=1505979
---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------
To put recovery on just skip down and follow the directions for Option C
http://forum.xda-developers.com/showthread.php?t=1342728
cast466 said:
Crap, i really wanted an Ics themed rom, there's a couple that use the format all zip from Calks but im terrified that once i place them on the sd card or flash with Odin they won't show up in my recovery, ah forget it i guess ill do the rom first and then worry about recovery, thanks a bunch guys
..... actually i need a custom recovery to flash that rom
back in the same hole
Click to expand...
Click to collapse
I'd give the ICS roms a little bit more time to ripen... only those who thirst for the bleeding edge can really call them daily driver's (and I've got nuthin but respect for them). "Reasonably" stable leaks (far from releases) of ICS for this phone are just a few days old; devs and bad-ass testers are all over them, and the ROMs, kernels, and themes for the rest of us are starting to come out. My (admittedly granny-ish ) advice -- flash up to calk's 2.8.1 EL29 ROM (now 2.9, tho I haven't tried it yet ) and add overstews or shiftr182s (or others) ICS theme and wait until the real ICS roms settle down just a *wee* bit more.
And don't forget to follow the prerequisite checklist on the top of the page beforehand! Don't worry too much about a backup in this case.
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
jt_hatch said:
I'd give the ICS roms a little bit more time to ripen... only those who thirst for the bleeding edge can really call them daily driver's (and I've got nuthin but respect for them). "Reasonably" stable leaks (far from releases) of ICS for this phone are just a few days old; devs and bad-ass testers are all over them, and the ROMs, kernels, and themes for the rest of us are starting to come out. My (admittedly granny-ish ) advice -- flash up to calk's 2.8.1 EL29 ROM (now 2.9, tho I haven't tried it yet ) and add overstews or shiftr182s (or others) ICS theme and wait until the real ICS roms settle down just a *wee* bit more.
Click to expand...
Click to collapse
I would advise this too, lol. ICS is really tempting but the safer and more stable route is the best. Shouldn't be too long of a wait for a more stable ICS anyways. I probably shouldn't of mentioned it.
yep, im trying the autoroot right now but its not recognizing the phone, debugging enabled and storage turned off, re-installing drivers right now to make sure that's not the issue
Try starting all over again with the one-click Odin again and do the autoroot right away.
http://forum.xda-developers.com/showthread.php?t=1505979
One nice thing about using the one-click and autoroot is how fast it is to redo.
MeWarning said:
And don't forget to follow the prerequisite checklist on the top of the page beforehand! Don't worry too much about a backup in this case.
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
I would advise this too, lol. ICS is really tempting but the safer and more stable route is the best. Shouldn't be too long of a wait for a more stable ICS anyways. I probably shouldn't of mentioned it.
Click to expand...
Click to collapse
believe me, I am TWITCHING to flash up to real ICS; I'm just a bit of a nervous nancy. Of course, I have yet to brick a phone... take that for what it is For now, I'm staying pat on GB; I'm willing to bet 2 weeks from now I'll be on ICS and w/o a trip to the sprint store, hat in hand, swearing up and down my phone is dead but most definitely NOT because I rooted (but a couple of weeks behind many ppl who jumped on ICS without a hint of a problem). Me, I'll pass on the walk on THAT much of the wild side; instead I'll wear out the "thanks" button for those brave souls who will...
Also don't worry about losing a ROM on your sdcard, Calk's format all won't touch it. Nothing really will unless you delete it yourself or specifically format the sdcard again. I've actually have 3 different roms on my card right now.
You might want to try this: Flash sfhub's Full EL29 restore here http://forum.xda-developers.com/showthread.php?t=1433101 then add CWM here http://forum.xda-developers.com/showthread.php?t=1342728 use option C and select the option L - EL29+CWM+Rogue. [sfhub's work is a life saver here - many an assumed 'bricked' phone has been saved via his work.] QBKing77 got's some freakign great vids here is how to get it on there http://youtu.be/jZRnH-_XZmM
That will give you a stock rooted EL29 with a very good CWM version (Rogue Kernal). You can use that as a starting point if you're not familiar with what you are doing. As some have said ROM Manager can be dodgy, Better off manually booting to recovery after getting RogueCWM installed. Make a nandroid image after you've got all your apps and settings working. (copy it to your PC too!) Do a LOT of reading to really understand what you are doing and what you really want! Then do some more searching for other ROMs and or themes, read what people say and through all the posts. Remember stock is Odex and most themes are DeOdexed - search and learn what that means if you don't.
I have used many ROMs and most here are great; it really comes down to your taste. You can't go wrong with anything based on Calkulin's work - PhantomHacker, StrongSteve, VeNuM and Team-Nocturnal. I've been using BlazerROM now for a while and absolutely loving the sh$t out of it, it's an ICS theme too. But just a friendly reminder to spend some time here reading and learning. Asking questions that have been answered will not go over well. Some posts have HUNDREDS of pages and they should ALL be read.
I'd also wait to go to a full/real ICS version till these awesome devs had more time to really work it out.
yep I already tried doing the autoroot with Option C and then Option L, but now it doesn't want to install drivers, it installs it while usb is connected but once i turn on debugging it goes away and the autoroot does not pick up the phone, sooooo frustrated right now but i hate giving up
I did everything exact to the video and it just doesn't pick up the phone
So if you turn on debugging and then plug the phone into the computer there isn't any chiming sound saying it's connected nor the phone recognizing it just got plugged into the comp?
And you have tried just powering off the phone and then holding the Volume Up and power button to go into recovery mode right?
cast466 said:
First and foremost any help will be appreciated.
Just got my sprint Sph-D710 galaxy, used the one click Odin EL29 stock kernel to root, everything is fine phone is rooted, tested rom manager and it asks for permission, but when i go into recovery it stops a quarter of the way and it goes into the triangle, the phone lets me hit the home button and it goes into some type of recovery but all the options it gives are reboot, wipe and partition, install from sdcard shows nothing in the directory??? any ideas on what i did wrong? Thanks again.
Click to expand...
Click to collapse
The recovery you are describing appears to be stock.
The triangle sounds like it is trying to install some leftover OTA.
---------- Post added at 11:21 AM ---------- Previous post was at 11:14 AM ----------
cast466 said:
yep I already tried doing the autoroot with Option C and then Option L, but now it doesn't want to install drivers, it installs it while usb is connected but once i turn on debugging it goes away and the autoroot does not pick up the phone, sooooo frustrated right now but i hate giving up
I did everything exact to the video and it just doesn't pick up the phone
Click to expand...
Click to collapse
If it is stuck waiting for phone to be connected, that means adb isn't able to see your phone.
Have you tried going over FAQ #E3 for troubleshooting:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Thanks for helping sfhub, I'm starting to run out of ideas for him!
Hi,
I'm not a very well versed with this rooting thing so I hope you guys can help me out here with some guidance. I have rooted a Desire HD for my friend quite some time ago. I follow step by step tutorial and managed to get it up and working with a custom ROM despite not knowing what half the steps are about.
Now, I tried to flash ICS 8.0 for him and it seems that it wasnt flashed properly as it is on a reboot loop over and over again. I did a factory restore before flashing and flashed using clockworkmod.
The main problem lies within I only remember parts and pieces of how I manage to root his phone the last time. How can I get it back working again without wiping off the root and s-off etc. Or is this just a small problem where I can reflash the rom without having to do all those again?
Let me know if you need any information about the phone. Thanks
If you are still able to get into recovery, make sure you do a FULL WIPE. Afterwards re-flash the rom and reboot your phone, should be fine.
---------- Post added at 10:07 AM ---------- Previous post was at 10:04 AM ----------
And something more:
if you're not sure what is the correct wipe you must do before installing a new rom, download this Super Wipe script (it's actually from ARHD but works with any rom ofcourse as it's just a full wipe), then you are 100% sure the problem will not lay with the wiping.
I tried to hold on to volume up key while powering on and all I get is 3 short vibrates and the yellow led on top blinking. The screen is blank, not even lit. Any idea what this means?
turn the phone off, pull the battery out and turn the phone on while holding the volume down button.
Now get into recovery and to a full wipe
so clear the cache partitions etc.
than flash again
btw ICS 8.0 does not excist
i gues you mean the 8.0 build from lord C ?
hi!
I've managed to get it to boot up in recovery mode! It was my stupidity to boot it up while pressing volume up when actually you had to press volume down. Got ICS up and running. Sorry for the confusion. Yep I was referring to the version 8 of the IceColdSandwich
I'll be sure to lurk around for more updates!!
orenzai said:
hi!
I've managed to get it to boot up in recovery mode! It was my stupidity to boot it up while pressing volume up when actually you had to press volume down. Got ICS up and running. Sorry for the confusion. Yep I was referring to the version 8 of the IceColdSandwich
I'll be sure to lurk around for more updates!!
Click to expand...
Click to collapse
No problem youre welcome
no questions anymore?
maybe about ics?
haha some bugs so far. the camera stopped working after 1 day. it focuses and snaps but the photo isnt saved. it worked when i first flashed it yesterday
Happend to me too. Use an alternative camera app for the issues with the cam
Sent from my Desire HD using xda premium
This is what happens when you dont read. These roms are always in the beta considered beta nad not really meant for people that dont know what they are doing or not willing to spend the time to read about it. Custom roms are not meant to be flashed to be part of the cool crowd. They are meant to help people learn how to do develop things on their own and how to trouble shoot issues.
zelendel said:
This is what happens when you dont read. These roms are always in the beta considered beta nad not really meant for people that dont know what they are doing or not willing to spend the time to read about it. Custom roms are not meant to be flashed to be part of the cool crowd. They are meant to help people learn how to do develop things on their own and how to trouble shoot issues.
Click to expand...
Click to collapse
I was expecting bugs. I'm on that likes to try out the newest things. But never mind, it's my friends phone and he couldnt bear with the bugs. It rebooted a few times randomly last night. Told me to flash it back to gingerbread for him. I'll keep an eye for the thread for more updates. Thank you all so much for the help guys!:laugh:
Q&A for [ROM/KERNEL][4.4.4] Quantum 5.2 & QuantumKernel 10/6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Simple question, from a simple user
singhz905 said:
Yep, Thanks. I just re downloaded the Kernel and it flashed perfectly.
Click to expand...
Click to collapse
First, want to say a big thank you to Pwn for the great ROM you created and the support you've given in the threads.
I've been keeping up with updates for about a year now, but wanted to ask the simple question about "flashing" a new ROM version or Kernel.
I use CW Mod recovery as well as titanium root to back up data and apps etc. When needing to flash a new kernel, what steps are required to ensure it is done correctly? I follow your directions on the home page, wiping everything a few times and installing fresh. From what I gather, that is only needed for flashing new rom's, is that the same process I must follow for Kernel's? Each time I return from the bootloader I install titanium backup from the play store and run my restore of apps etc, not sure that's the best practice, but I am looking for simple answers. I'm a father and work a lot of hours here in Bosnia and Herzegovina, and don't have a lot of time to dedicate to spending hours tweaking the device. I use your rom for it's simplicity and battery life. Any guidance is much appreciated.
Thanks,
Andrew
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
mrrocketdog said:
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse
Great information as well as confirmation. I will take your advice and create the zip file. That will make things a lot easier for sure. And thank you for the quick response!
Quantum Kernel 10/11
I take it that bluetooth is working again on Quantum Kernel 10/11?
Thanks!
Hey pwn! Thanks for Quantum/ Quantum kernel! I used to always use CM10/11 and it was never that stable for me and the GPS wouldn't work most of the time. I installed Quantum kernel 9/8 and the rom and it was pretty stable I did get some restarts in apps once in a while. However, once you released the new 10/11 kernel everything has been running super smooth! Thank you so much for all your work. I only had one issue with the new kernel, when my battery was completely drained and then shut off, I then plugged in my phone to the AC adapter and it would stay at the boot logo with samsung and pwncakes at the bottom. However, once I let my phone charge for a couple minutes I was able to start it up without any problems. Thanks again!
---------- Post added at 06:29 AM ---------- Previous post was at 06:16 AM ----------
trent2 said:
I take it that bluetooth is working again on Quantum Kernel 10/11?
Click to expand...
Click to collapse
Yep, it's working for me. I'm using a pioneer head unit in my truck and stream audio and phone calls.
Quantum Kernel
Thanks, I'll have to try out the latest.
Hey all. I'm using latest philz touch recovery. For some reason I can't flash the 10/11 kernel with it. Status 7. Assert error. Any ideas?
Sent from my SGH-I747M using Xparent Cyan Tapatalk 2
REPORT: 3hrs post clean flash. att sghi747UCUFNE4.
twrp 2.6.3.1. superSU v2.0.
carbon nightly 10-16 with QK 10-11.
wifi , sound , gps all good. (never have used bluetooth, so dont know. srry).
NO : f/c , random reboots.
no calendar icon (?). & would like to request , if able and not too much trouble , the APN settings menu.(!?). unless i totally overlooked it , which i don't think i did. (please). thanks once again pwn for helping to keep our 'ol s3's up-to-date.
err on the side of kindness
:GOOD:
err on the side of kindness
That looks familiar
Sent from my SAMSUNG-SGH-I747 using Tapatalk
manfromgta said:
Hey all. I'm using latest philz touch recovery. For some reason I can't flash the 10/11 kernel with it. Status 7. Assert error. Any ideas?
Sent from my SGH-I747M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
My guess is you have an unsupported version of recovery installed like d2can instead of d2att. Follow these steps to find the problem: http://forum.xda-developers.com/showthread.php?t=2302599
Update to my fellow Quantum members. Have flashed properly and wiped properly, reloaded Q5.2, QK10-11 and restored my apps/data from TIBU. Since this upgrade, my phone is discharging it's battery within minutes. I can't boot it properly when it is plugged into a charger and at times the screen is locking then unlocking itself then crashing. I have tried full wipes and factory reset's and then flash everything from scratch, but to no avail the battery life is still crashing. Any advice? I researched this problem in the threads and only saw a solution to go back to the nandroid or something like that, but did not see instructions, therefore I am lost like a proper noob.
Thanks,
A
mrrocketdog said:
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse
Texan806 said:
Update to my fellow Quantum members. Have flashed properly and wiped properly, reloaded Q5.2, QK10-11 and restored my apps/data from TIBU. Since this upgrade, my phone is discharging it's battery within minutes. I can't boot it properly when it is plugged into a charger and at times the screen is locking then unlocking itself then crashing. I have tried full wipes and factory reset's and then flash everything from scratch, but to no avail the battery life is still crashing. Any advice? I researched this problem in the threads and only saw a solution to go back to the nandroid or something like that, but did not see instructions, therefore I am lost like a proper noob.
Thanks,
A
Click to expand...
Click to collapse
Some battery stats screen shots or a BetterBatteryStats log could help to diagnose your problem assuming it's a wakelock causing it. Try leaving your phone idle after unplugging or rebooting for a couple hours to get better stats.
Edit: This thread might help you out if it is a wakelock: http://forum.xda-developers.com/showthread.php?t=1179809
luckie10 said:
Some battery stats screen shots or a BetterBatteryStats log could help to diagnose your problem assuming it's a wakelock causing it. Try leaving your phone idle after unplugging or rebooting for a couple hours to get better stats.
Edit: This thread might help you out if it is a wakelock: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Thanks for your reply. There in lies part of the problem, I can't get it to stay on for longer than 20 seconds or so to take screen shots, download the battery stats log etc. It is constantly unlocking and relocking the screen over and over and then shuts down and doesn't reboot properly. Also, with the battery out or just on AC power it will not power on.
Quantum 5.2 is running very smooth on my phone. Quick question though, my bootloader is I747UCALG1 and modem is I747UCLG1. What bootloader and modem should I upgrade to in cwm, I've been hearing about this NE4. Or should I just go for the jellybean ones? Thanks!
Texan806 said:
Thanks for your reply. There in lies part of the problem, I can't get it to stay on for longer than 20 seconds or so to take screen shots, download the battery stats log etc. It is constantly unlocking and relocking the screen over and over and then shuts down and doesn't reboot properly. Also, with the battery out or just on AC power it will not power on.
Click to expand...
Click to collapse
Gents, it has been a few days now and I have no solution for even booting up the phone. Now when holding the power button down to restart it will begin to reboot, but then just shut off. I rarely can get it to the recovery screen, but then it crashes quickly. This limits anything I can try to do in recovery, so I'm open to any suggestions at this point.
Thanks!
have you put this on the general s3 Q & A thread ? more would see it there. just an idea.
err on the side of kindness
Update. So I finally had some time to scour the forums for a possible solution and troubleshoot further. Turns out the power button was shorted, had to watch a tutorial and removed it. After getting to recovery I was able to flash 5.2 and latest kernel etc. So far so good, it needs a full charge and hopefully that will go smooth. As this problem started it was discharging the battery so incredibly fast I couldn't keep it charged. Thanks for your help everyone, crossing my fingers it stays up!
Texan806 said:
Gents, it has been a few days now and I have no solution for even booting up the phone. Now when holding the power button down to restart it will begin to reboot, but then just shut off. I rarely can get it to the recovery screen, but then it crashes quickly. This limits anything I can try to do in recovery, so I'm open to any suggestions at this point.
Thanks!
Click to expand...
Click to collapse
Sounds like it is hardware related I'm guessing faulty power switch. I've had two go bad on me and that's exactly the symptoms you describe. $20 fix unless you do it yourself
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
aircooledbusses said:
Sounds like it is hardware related I'm guessing faulty power switch. I've had two go bad on me and that's exactly the symptoms you describe. $20 fix unless you do it yourself
Click to expand...
Click to collapse
Well glad you got it sorted out any way
I had an unfortunate defect in my previous phone where it no longer saw the SIM card, so I had to have it exchanged through T-Mobile. The refurb I got in exchange had the NH7 complete stock ROM installed already, so I was stuck with Knox.
I flashed the 02/23 release of Danvdh's GPE ROM, but lost sound. After reflashing it several times, I thought maybe it was a compatibility issue. I decided if I was going to be stuck with a TW stock ROM for now and already had Knox, might as well use the latest, so I Odined the stock NK2 ROM posted by ShinySide. Sound issue persisted, and on further inspection I found the bootloader had failed to update with the rest of the ROM, so thought the mismatch with the modem was a problem.
After fighting to get it to update, I finally succeeded and have a complete match of bootloader, modem, and ROM for the same (NK2) release, but the sound problem persists. In addition to the sound problem, and probably related to it, various apps are unstable and sometimes FC for no apparent reason, and the camera fails to load at all.
Anyone have any insight to this one?
Don't know why everyone is so anal about Knox, if your warranty is up it doesn't make a difference.
By flashing lollipop you got all the bugs that Samsung and T-mobile are weeding out before releasing the update, try clearing data in recovery or in apps not working.
Reflashing twice with a battery pull in between without rebooting after first flash may help.
Uninstalling and reinstalling apps f/c'ing may work.
Pp.
---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------
I run stock / debloated with all Knox removed with no issues what so ever, and everything works the way it's supposed to.
Pp.
My warranty wasn't up yet, so I had hopes for avoiding it. The apps with problems are mostly the ones that use sound and I still have the problem on a fresh install of the mentioned stock KK ROM.
As for back-to-back flashes, I forgot to mention I've been using that method after reading about it so often, just to be sure.
What recovery are you using?
CWM
Twerp
Philz
Pp.
TWRP.
The stock ROM I'm Odining overwrites that with stock.
Did you do a full factory reset?
It's needed in your case with the lollipop rom going back to kitkat.
Don't see it mentioned in your op.
Pp.
I did, and my apologies for leaving out so many vital bits of info. Having read so many threads, I really ought to know better.
Wow, this is getting complicated.
I'm running out of ideas, you may have to start going through lollipop threads and maybe you'll come across something that may give you a lead on how to proceed.
It may come down to picking a dev's brain on what to try next.
Sorry about my long response times, snow day today for nyc schools and been busy all day with my daughter, she's disabled with cerebral palsy and a handful.
Check the 5.0 threads maybe someone has been through this before you, and you'll be able to find an answer. I'll try Google and let you know.
Pp.
---------- Post added at 10:21 PM ---------- Previous post was at 09:54 PM ----------
Did you do a factory reset right after flashing stock kitkat?
You do this before first boot up so that conflict from previous rom doesn't stick to new rom flash.
Reset will delete all data pertaining to apps, if you had any lollipop incompatible apps before 5.0 and thy get borked, they will mess with new rom install.
Try a reflash of kitkat and right after flashing completion pull battery, startup in recovery and do the factory data wipe (reset) . Now let phone boot up and see.
Pp.
I did in fact do just that as one of my most recent attempts at this, and I'll probably do it again tonight for giggles. Maybe I'll get lucky.
I appreciate you taking the time to help out. I spent 2 days searching through any thread I could find regarding no sound issues before posting.
If I can make contact with one of the more knowledgeable devs here and get this resolved, I'll most certainly be posting the solution here.
-EDIT-
Got it working!
I recalled this post in which someone mentioned having removed the back speaker and reattached it so solve a no sound issue on their S 4. I had thought to try that at the time, but didn't have a tiny phillips screwdriver handy. When I got one and tried it, I was quite shocked as I hadn't had much hope for it to work for me.
Thanks again for your help, Pancho. You rock.
Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*
Interesting story bro
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Let's see if I can reply today when I'm home
Hnk1 said:
Interesting story bro
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Let's see if I can reply today when I'm home
Click to expand...
Click to collapse
2000ftt said:
Click to expand...
Click to collapse
Hi
well, I have had used different variants of LG G3s and I found that some ROMS had certain bugs. Like in Fulmics and Cloudy, if you turn off your device on AT&T variant, you can not turn it on again unless you replace the battery again. Even that used to occur on a reboot so it depends really which bugs you might face.
It could be your battery but I will suggest you few things you can do. Firstly, charge your battery to 100% and wait half an half more before you unplug your charger. Next thing, You calibrate your battery as well, maybe there might be an issue. You can find battery calibration tool by Nema in the playstore.
Next thing I would suggest you to move back to STOCK Lollipop / Marshmallow which you can flash via TWRP or KDZ or TOT method. See if that works for you or not. When I faced the issue of my device not booting after a restart or power off unless i reinsert the battery, this helped!
Last, clear dalvik cache / etc and see that helps too. (Would be done if you flash the KDZ)
Also, if you are flashing roms, for example lollipop stock before you flash a new custom rom, make sure you restart in betwee. i.e
flash lollipop stock via twrp. Restart and then install custom rom of your choice. Flashing over sometimes does not work well.
Good Luck and I hope you have a better story for me where everyone lives happily ever after!