Related
Hi smart people!
Just to throw it out there, I am not very tech savvy so excuse me if I misuse terms and such.
I believe I completely bricked my phone (I hope I'm wrong). After I downloaded Cyanogen through ROM Manager, my finger stumbled on the "continue" or "next" button or whatever WITHOUT checking the boxes to clear data, etc. I believe this is where I went wrong as I think I followed all other steps correctly (fyi I used the one click recovery flasher and made a back up).
Now when I turn on my phone, it goes from the stock LG loading screen to a modified LG loading screen (Cyanogen's I'm assuming) but it gets stuck there.
I've been searching on the different threads for quite a while and pressing the different combinations of volume up/volume down/power don't seem to do anything. I cannot get to the recovery screen.
Please help! I will forever be indebted to all of you. I am stupid and shouldn't have tried to do this on my own. Thanks in advance
What you will need to do is flash CWM via NVflash then boot into CWm and install your ROM.
If you flash CWM via ROM Manager it causes problems like what you're describing, I know from my own experience of following a friends instructions and doing that then having that exact issue. After getting my phone working again I then started to frequent the boards here.
As soon as I read the first couple lines I saw rom manager and saw the problem, you to search something that you have typed out all within this thread... I'm not near a computer but you should just search through these threads and you find your solution in detailed description. You need to get recovery from nvflasher just search that
Sent from my LG-P999 using xda premium
thanks for your replies
thank you to both of you for your prompt replies. i will try doing this within the next couple hours and post any results. this is the thread i found with the information you guys gave: http://forum.xda-developers.com/showthread.php?t=1058649
thanks again
No, that's not for G2x. Go here: http://forum.xda-developers.com/showthread.php?t=1056847
Ya it needs to be the one that gunnman wrote out for people.
Sent from my LG-P999 using xda premium
Hey guys...on step #10, it says to "select 'have disk'" but i do not see that option in the list.
Thanks
okay now i realize i should have been doing the cwm recovery. sorry guys and thanks again
reboot error
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
justintheshark30 said:
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
Click to expand...
Click to collapse
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
P.S. for future reference, you did not brick your phone, you got stuck in a boot loop, you know your phone is bricked when you don't see anything on the screen when you turn it on, usually it's just a software issue, but sometimes it could be hardware, for example I burned the motherboard on my previous android phone trying to customize it lol
jj_z1 said:
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
Click to expand...
Click to collapse
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Волк said:
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Click to expand...
Click to collapse
I really hate posting anything that doesn't have to do with anything phone related but I just couldn't stop myself from replying to your post!
1) I actually read all posts in the thread!
2) I did not in any way suggest that he didn't flash CWM the right way, I merely asked if he had done a full wipe before restoring his backup!!
3) Your reply was submitted while I was typing mine, so I'm sorry I didn't check the thread again before submitting my reply!!!
4) I'm well aware of what he tried to do already, but thanks for repeating it!!!!
5) If YOU read all previous posts you'll notice that my post does not exactly replicate any other, there's some new information in there that the OP might find useful!!!!!
6) From what I can tell, you need to work on your english and comprehension skills!!!!!!
To the OP, sorry for trolling your thread with this post, but I just couldn't help it, and to Bonk I hope you'll be the mature one and not reply to this post.
Is that to say you're immature? If one were to judge by the number of exclamation marks you have I'd say yes.
The only "new" thing was asking if he wiped before the restore, which, at this point, would be useless to ask as I already told him to make sure to wipe.
To the OP: How goes everything thus far?
thank you
that's what i ended up doing and it worked. thank you so much for all your help!
Волк said:
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
Click to expand...
Click to collapse
And dalvik cache for good measure, even though it is stored on the cache partition and will probably get wiped when you wipe cache. Sometimes it's good to overdo thing's.
Unable to do anything!
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Start over. Do what it states here: http://forum.xda-developers.com/showthread.php?t=1248644
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Did you battery pull and start over?
Sent from my LG-P999 using xda premium
UNROOT help
Hello again smart people,
I was hoping we would never meet again (for the better) but unfortunately i must unroot my phone to receive work emails. I have tried unrooting my LG G2x multiple times but to no avail thus far.
Here is the process I have tried:
1) boot into recovery - wipe cache/data factory reset, wipe cache partition, wipe dalvik cache
2) restore - using stock rom i found online
3) flash stock recovery image using nvflash
4) (attempt to) unroot using superoneclick - AFTER GOING THROUGH MULTIPLE STEPS, IT SAYS "TRUE" UNDER "CHECKING IF ROOTED". (also, i know it is rooted because it says the phone already appears to be rooted when i try to root again).
Do you guys have any idea what the issue could be?
Thank you in advance...
Had just flashed the latest CM9 nightly (clean install, fresh wipe) yesterday and everything was running fine.
This morning, woke up, my phone was turned off. When powering it on it hung on the google screen. Fastboot still working, booted into recovery only to find that I would get error messages when trying to load my backs "E:unable to mount /sdcard". Apparently it also couldn't mount /data. So I was unable to flash any images or restore or boot up.
Seeing that fastboot was still working I assume I'm not bricked yet. I tried flashing a new boot and cwm recovery via fastboot - no dice. Same errors.
I don't have a recent backup of anything in sdcard, but at this point I'm willing to sacrifice it.
Found this thread http://forum.xda-developers.com/showthread.php?t=1078213
and I'm trying to follow the steps to flash back to stock GB. using the GRJ22 images
It flashed the boot and recovery without issue but seems to hang while flashing the system.img. I know it's a big file, but it was up to ~2hrs with it still transferring. I pulled the plug on it and tried again, lost patience after an hour.
Now I had the idea of maybe locking and unlocking the boot loader would help things.....not sure why I thought this. Anyway, now it seems to hang on the unlock bootloader screen.
So my question now - am I screwed?
- anything else to try?
- is it really "hanging" or do I need to give it more time?
- have I screwed myself even more by now locking my bootloader and flashing the stock recovery?
Any help would be very much appreciated....
Some new additions and new insights from the reddit android community:
- this probably has nothing to do with CM9. My phone has been wonky for about two weeks - random reboots, sometimes rebooting into recovery. That's why I thought I'd throw on the latest nightly and do a fresh wipe yesterday.
- There's definitely something up with /data. Anytime I tried wiping all/factory reset in cwm recovery I got errors about not being able to mount /data or being able to find files in /data
- basically anything I do involving /data partition causes the phone to lock-up -- flashing the boot.img and recovery img worked, but not system. Also, I think the reason I can't re-unlock the bootloader is because during the unlock process it tries to do a factory reset/data wipe
Basically I think there are two things I need to know if I can do - 1) unlock the bootloader again, via some way that won't try to reset the /data partition and thus won't freeze the phone. 2) try repartitioning /data
I really hope I didn't screw myself by locking the bootloader. I'd actually feel a lot better if it was something in my phone that just failed hardware-wise rather than something I could've fixed if I wasn't too quick to try poorly thought out ideas.....
Any help at all would be appreciated!
Possibly (and likely) a corrupted nand flash. Fairly common problem sadly. I'd say it's a good thing your bootloaders locked, no dramas sending it back to samsung. It might've been possible to reset the partitions and flash fastboot images but i don't think i've seen anyone who has done this to sort any similar problem. Hopefully your phones still under warranty
Well thank God that it turns out that I'm still on warranty.....sending the phone back to Samsung tomorrow.
Like you said, it's actually a good thing the bootloader is now locked and the stock boot img and recovery img are now back on! Hopefully this makes it more likely that they weren't turn away my phone.
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Harbb said:
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Click to expand...
Click to collapse
I bricked my nexus s 4 days before Christmas last year... and i was using a custom rom obviously with an unlocked bootloader and custom recovery image, and i handed it to vodafone, and guess what? they repaired without asking any questions, and the day before Christmas! sooo happy maybe because i was thirteen then, they didn't suspect a thing
I was running CM10, downloaded the nightly released on 1/13.
Installed it, it rebooted, then got stuck looping again. I couldn't get it to do anything. Eventually my boot screen would go away, it would go to a blank black screen. I could see backlight, but I had absolutely nothing.
I managed to get into my bootloader, could get into recovery as well. I'm using TWRP.
I couldn't get it to do anything at all.
I eventually wiped my SD card, reformatted it, downloaded AOKP, flashed the ROM. It's started, got to the AOKP Loading screen, which it is now looping. I can't get it to do anything. I'm lost and frustrated as can be.
Any fresh ideas from anyone?
If the screen is on, its not bricked. Not knowing what to do is not a brick.
Did you factory reset, wipe data and wipe cache (all from TWRP, do not factory reset from hboot, whatever you do) before flashing?
If on hboot 1.14 or higher, did you flash boot.img via fastboot?
I restarted the entire process. I actually ended up having to do it a few times. No change in the process.
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
On another attempt it worked just fine. No change in the way I did things. I'm unsure of what the difference was or why, but its working, for now. I may end up getting a different phone instead of my Onex to see if things run smoother on my process. I have an old captivate I may try to use as a trial/error experiment.
Sent from my One X using xda app-developers app
i factory reset from hboot is there anything i can do? had the same issue with cm10
mfc1288 said:
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
Click to expand...
Click to collapse
Why do people keep wiping their SD card when flashing? I understand there are some people that do it deliberately because they like to make a "fresh" start. But it seems that the majority of people doing it are n00bs that for some reason think its "required" when flashing a new ROM, which it is not. Factory reset, wipe Dalvik, wipe cache. Nothing else "needs" to be wiped when flashing.
Remember on most devices the SD is removable, and doesn't really have much of anything to do with the flashing process, aside from the fact that you put the new ROM zip file on there (and backups go there). Its like saying you "have to" format your external hard drive every time you want to change or upgrade your PC operating system.
mfc1288 said:
I have an old captivate I may try to use as a trial/error experiment.
Click to expand...
Click to collapse
Completely different hardware, so I'm not sure what you would trying to accomplish with that experiment. I think you just had some bad luck, and bad flashes just happen occasionally. I've flashed many different ROMs on the One X, and have never had issues booting up.
CM10 seems to be giving more headaches than other ROMs, so that may have something to do with it. Not to insult that ROM or its devs. But when things change nightly, there can be glitches. And it just seems there are a lot more complaints about not being able to boot after flashing CM10 than other ROMs (despite having correctly flashed boot.img and wiped). Or maybe the number of people posting this issue is just a testament to how popular CM10 is?
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
sinzish said:
i factory reset from hboot is there anything i can do?
Click to expand...
Click to collapse
This has been discussed on many threads already. Plug the phone to a PC, and it should show up as new hardware. Select it, and choose the option to format FAT32. After that, you should be able to mount as a USB drive.
So here is the situation.
Regardless what Rom I flash, the phone works fantastic up until the first time you try to reboot it. At that point it gets past the samsung flash screen and gets stuck on the flash screen of whatever rom I'm running. I've even left it on like that for an hour and it never changed. The only way I'm able to get out of this is to reboot into recovery with a battery pull and do a data/internal storage wipe.
I've even tried odin'ing to stock and when it goes to reboot the phone to reset it gets stuck at that screen.
From recovery if i wipe everything and install the rom fresh it works great. Any ideas what is messed up or corrupted? Gets kinda old having to reset everything just because phone needs to reboot lol.
xRelapse13 said:
So here is the situation.
Regardless what Rom I flash, the phone works fantastic up until the first time you try to reboot it. At that point it gets past the samsung flash screen and gets stuck on the flash screen of whatever rom I'm running.
Click to expand...
Click to collapse
I have pretty much the same issue with any ROM other than the stock Verizon. I can restore that and everything is fine. I can flash a ROM, flash GApps (if needed) and everything is fine...but restart and yep..hangs at splash screen. If I try a standard wipe data, it fails. I have to do a format of internal memory and then I can proceed to restore or reflash. Kind of a pain in the ass because I really want to run something other than stock. Whoever can solve this problem will be a hero!
Maybe this will help you
Might be a bad partition, a rare problem to all. Maybe this will help you, do this at your own risk. Read first the thread before making a move.
[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have responsibility to your phone, it is your choice.
skyss07 said:
Might be a bad partition, a rare problem to all. Maybe this will help you, do this at your own risk. Read first the thread before making a move.
[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have responsibility to your phone, it is your choice.
Click to expand...
Click to collapse
Gonna go ahead and read through that and try it, not much to lose at this point. I'll keep you guys updated if it works or not
xRelapse13 said:
Gonna go ahead and read through that and try it, not much to lose at this point. I'll keep you guys updated if it works or not
Click to expand...
Click to collapse
Please do...I am interested to see what happens but not ready to try it yet as I am going on vacation and need my phone at the moment instead of bricking it...LOL
I actually had this problem when I just did the regular wipe in TWRP (the one that maintains the internal SD card). When I did an advanced wipe and did everything, excluding the recovery and external SD, things went back to normal.
Used the Unbrick thread and it fixed the problem. Thanks!
Just wanted to post this update for anyone else who had the problem.
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL