I've spent about 3 days and worked closely with a few knowledgeable people outside of this forum. I'm desperate and a bit terrified to start this topic. I've read too many to know how frustrating it to answer the same questions over and over again.
In short:
a.) Was running CM9, flashed using CWM. (Did not have issues and have flashed in the past with other roms successfully)
b.) Went to flash another ROM (can't remember which one) and did not back up (big mistake, troll away)
c.) Cannot get phone to start, can flash roms all day long and only get to their boot/splash screens. It will sit there until my battery dies
d.) I've tried Galaxy Nexus Toolkit and Wugs
e.) I've installed TWRP and formatted drive
f.) I've read and followed 3 full days of different forums and still can't figure this out. I've tried so many things it would take forever to type.
I'm severely desperate.
Will someone help me start from scratch and walk me through a surefire process. At this point, I'm lost. Nothing seems to work.
Apologies in advance and I am willing to accept the bad vibe. I'm lost.
Phone is a Verizon Galaxy Nexus
Did you try fully wiping, formatting /system, flashing a ROM and wiping cache after that? Or flashing another kernel?
Wow finally something
Wow! I finally got something to load. I'm on 4.0.2. I need to get back to jelly bean.
Wow, I'm stuck in nearly the same rut as you are in right now.
Experienced flasher here too - I was using the Xylon v18 until now, and Paranoid Android 2.99 before this. Yesterday night my phone rebooted after some weird Contacts application opening issue. And kept rebooting. One backup restore said there was an I/O error in /data/data/com.android.contacts or something. The backup never booted.
I have TWRP 2.4.0.0.
I tried new ROMs, different ROM backups, a few kernels, formatting /data including internal memory, tried Adb sideloading (said Read Only file system), finally installed Xylon v18 through Usb-otg, but it refused to go beyond Google logo. Restored a backup through OTG, and the same continues.
Could someone tell me what could be going on here?
I swear I was about to put in a post similar to the OP.
Thanks for the headsup just_some_dude, I'll go try an ICS rom now.
---------- Post added at 01:59 PM ---------- Previous post was at 01:23 PM ----------
Edit1 : So it looks like my phone wanted to remind me what it feels like to actually jump with joy!
Installed the deodexed version of stock rom, and after a failed first boot, "Android is upgrading".
Edit2: Scratch that, couldn't get through phone setup. Changed to CWM 6.0.2.3. Flashed radio and RIL, PA2.99 again, and for now it seems to be working.
desktopfusion said:
Wow, I'm stuck in nearly the same rut as you are in right now.
Thanks for the headsup just_some_dude, I'll go try an ICS rom now.
---------- Post added at 01:59 PM ---------- Previous post was at 01:23 PM ----------
Click to expand...
Click to collapse
I was able to IMM76K, but phone wants to push newer version. I can't upgrade newer version without it getting stuck on that splash screen for the rom. I'm putting IMM76K back on.
So, weird. So much of this is not making sense to me.
Rebooting continuing for me despite different kernel and cache/dalvik wipes.
I'm sorry, absolutely not trying to hijack this thread. Only writing symptoms incase anyone notices something they have gone through too.
Baah, this is going to properly spoil my weekend.
Why not try to go back to stock by flashing the stock images first? At least you'd know if the phone works...
Thank you for the input.
I did, but in the zip, deodexed form. For me, all things are now pointing to Wifi causing the reboots, even when the Stock 4.2.1 was used I couldn't go past phone setup.
On PA2.99, after switching wifi off as soon as it booted, the phone is now stable for 10 minutes for the first time in 8 hours of trial-and-error.
Shouldn't XXLH1 flashing have fixed such things?
FIXED! It was a corrupted /data partition, which showed the /data/media or /sdcard was already 11 gb full after a full wipe with TWRP.
A /data and /data/media format with CWM did the trick!
desktopfusion said:
Thank you for the input.
I did, but in the zip, deodexed form. For me, all things are now pointing to Wifi causing the reboots, even when the Stock 4.2.1 was used I couldn't go past phone setup.
On PA2.99, after switching wifi off as soon as it booted, the phone is now stable for 10 minutes for the first time in 8 hours of trial-and-error.
Shouldn't XXLH1 flashing have fixed such things?
Click to expand...
Click to collapse
For reference, that's not going back to stock. Back to stock means flashing the Google factory image, which would have also formatted your data partition, so do that in future
EddyOS said:
For reference, that's not going back to stock. Back to stock means flashing the Google factory image, which would have also formatted your data partition, so do that in future
Click to expand...
Click to collapse
Ah, I did not know flashing the image wiped data partition as well, thanks!
I stopped looking for the image when I couldn't find JOP40G on the site. Classic case of beggars trying to be choosers. :cyclops:
I just tried to flash mmuzzy and gapps using wugs and am sitting at the Jelly Bean 'X' splash screen. I set it up so wugs would wipe data cache and Dalvik. Don't know what it is, but I cannot get Jelly Bean on this phone.
Tried flashing the Stock factory image? Not through recovery, but through fastboot. That is what I did ultimately.
Actually, my problem was deeper. My /userdata partition had some errors. On going through some posts here on /data partition corruption issues, these links helped me a lot, and made the phone ultimately much smoother than it ever was!
Definitely try the e2fsck command through adb shell while in recovery with /data partition unmounted. Try this before you flash a stock ROM image.
Here you go. I think these should help you too:
1. http://forum.xda-developers.com/showthread.php?t=1541379&page=4
2. http://forum.xda-developers.com/showthread.php?t=2025675
3. http://linux.101hacks.com/unix/e2fsck/ - e2fsck command options if you need help.
If adb asks you to 'check forced' because it finds problems, just use
Code:
adb shell "e2fsck -f /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata"
I'm guessing it was all a result of months of flashing huge amount of ROMs. :angel:
Related
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Moheemo said:
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Click to expand...
Click to collapse
2.6.3.0 seems to be giving many people issues. You need to install 2.6.1.0.
And is your radio up to date? Only 2 work...the new T-Mobile and Telus radios.
After those 2 things are taken care of, you should be fine. Tho lots of things can cause boot loops, and there's many.. many posts about it. If my suggestions don't help.....Search and read up. Try some various fixes.
Maybe try a different rom too.
Sent from my cellular telephone
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
Hope you did a nandroid backup in recovery? Restore it if so. If not, you may need to start from scratch and Odin flash stock rom, flash recovery and root again.
Sent from my cellular telephone
Moheemo said:
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Click to expand...
Click to collapse
flash stock rom zip via odin then you should be good to root and try to flash another custom rom again:good:
Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!
Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?
Format /system under Mounts and Storage in CWM and reflash ROM and GApps?
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
Soft bricked G3 with a lost IMEI number
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
mrchuajason said:
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
Click to expand...
Click to collapse
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
I don't quite know how to do it though but I've been thinking about unbricking my phone and restoring to factory state and start all over again. Do you mind posting a link for the instruction on how to do all this? Thanks
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
mimivg said:
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
Click to expand...
Click to collapse
This was the ROM I initially wanted to flash. I think something went at flashing the Modem causing my phone to have this unmount /system problem.
I have followed the instructions from Max at galaxynote4root http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/5/. I got all the way through to the final step which is go into TWRP recovery, install the Oscar kernel and SuperSU zip files. I did not extract these files. Once I did that I got into a boot loop. I get by the Verizon logo to the UI and then it starts rebooting. Since there is not much discussion activity at Max's site, I thought if anyone here could help me.
After the UI comes up and before it goes in the boot loop, I get messages saying "Unfortunately xxxx has stopped." It varies about sometimes it is Knox. S Pen, Google Play, etc.
Try a factory reset by going into recovery and wiping delvik, cache, and data
MonstaSaleens said:
Try a factory reset by going into recovery and wiping delvik, cache, and data
Click to expand...
Click to collapse
That improved the situation. It is no longer in a constant boot loop, but it will still reboot when I manually start it or reboot it. When it starts it says "unfortunately KNOX has stopped running." It was doing that before, too.
I have confirmed I have root and and unlocked bootloader.
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.
codydixon said:
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Click to expand...
Click to collapse
Just followed your instructions. Everything was fine until I installed the kernel and supersu. I hate to be stuck when I'm so close.
ssj4gogeta2003 said:
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.[/QUOTE
OK, tried that, and it worked--once. When I reboot with the SD card out, it either won't start or goes back into a boot loop.
Click to expand...
Click to collapse
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
MrNetwork said:
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
Click to expand...
Click to collapse
You'll need to connect the micro sd card itself to the computer and format it there. I have used Rufus (https://rufus.akeo.ie/) in the past to do this, but you may use any formatting program that you are familiar with. I recommend FAT32 as your format unless you move files over 4 GB to and from the card.
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
MrNetwork said:
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
Click to expand...
Click to collapse
It will depend on what version of firmware you are currently running. Most 6.0 ROMs require that you are using N910VVRU2CPD1 or N910VVRU2CPF3 for proper use. Please go into About Phone in Settings and check the Baseband Version field to make sure that you have one of those two in there. Flashing a 6.0 ROM with 5.1.1 firmware will cause issues with mobile signal and can make it impossible to use wifi.
If you find that you are running 5.1.1 firmware, then you have two choices: Flash a 5.1.1 ROM and call it a day or go through the process of unlocking the bootloader for 6.0.1 firmware. It's important to note that this will be a different process than the one you just went through. Be sure to research it thoroughly before attempting it. Hsbadr is a great developer and I believe he has a process for that, but it's been a while since I did it myself.
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
MrNetwork said:
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
Click to expand...
Click to collapse
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
ssj4gogeta2003 said:
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
Click to expand...
Click to collapse
Thank you. I finally figured it out. The problem was with oscar_kernel_v0.2. Instead I am using Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P. I'm going to stay with 5.1.1. The only trouble I am having now is with My Tracks not showing the map. I know it's been deprecated by Google, but it still is working on my LG G4. However, I'm not trying to hijack this thread. I'll start a new thread for this issue.
This is now the fastest phone I've used after deleting bloatware and running Nova Launcher.
Good to hear. Enjoy the phone.