Related
I've been lurking for quite some time and haven't been able to find a solution for my issue. Here's what happened:
I cracked the screen on my Galaxy Nexus and got an insurance replacement. I then used ClockworkMod Recovery to copy over from my old device to my new device. All was good for about 12 hours when the new device started boot looping with the flashy color animation screen. I figured that might have been something I did, so I tried doing a factory reset and the like with ClockworkMod Recovery and managed to totally mess the phone. After trying to do a factory reset, the phone wouldn't boot up at all anymore -- I just get the dreaded red triangle with exclamation point. I tried formatting all the partitions with ClockworkMod (which was a bad idea). Ever since then, I've been stuck. I've spent several days so far trying to get this thing working. I have to note that Odin and fastboot modes work perfectly fine.
Among things I've tried unsuccessfully:
Flash to stock using Odin
--Odin says everything is fine, when I flash with a stock ROM that I downloaded. Upon reboot, nothing is any better and I still get the red triangle/exclamation point.
--When I try to use the tar files that ClockworkMod generated, Odin crashes immediately.
Push custom ROMs to /sdcard/ using adb while booted into ClockworkMod in hopes of getting the system to boot.
--This never works successfully. Sometimes I get no error but can't find the zip file. Other times I'll get an I/O error, or even a read-only error. The original backup is giving me checksum errors.
Flash factory ROMs using fastboot.
--I always get the red triangle/exclamation point.
Restore and flash with WUG's toolkit.
--Same thing as when I try to use fastboot. It seems that flashing the device goes fine, but the device will still not boot.
After every time I've flashed the device, whether using Odin or fastboot, I've tried doing a factory reset by pressing power+vol up+vol down and then selecting factory reset. This hasn't made any difference.
I'm about to give up on it and send the device back to the nameless insurance company, but I would like to lock the bootloader first. I can't even seem to lock the bootloader! In fastboot, I type the usual 'fastboot oem lock', and the device reports that it is locked, but after rebooting, the device always reverts back to having an unlocked bootloader.
Have I missed anything? Any thoughts? I'm lost.
Fyi, the red exclamation point is the stock recovery screen.
Try following the instructions in the "flash" link in my sig.
Sent from my Galaxy Nexus using Tapatalk 2
As well, issue the following commands when in fastboot:
Fastboot erase system
Fastboot erase userdata <- this will wipe by the way, including/sdcard
Fastboot erase boot
Fastboot erase recovery
Fastboot erase cache
And then flash the images in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
enginerrd said:
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
Click to expand...
Click to collapse
If you've flashed the system, userdata and boot images using fastboot, and you are still not able to boot into Android, I can only suspect that you have either a corrupt bootloader or a hardware issue.
And if odin does not work, then unfortunately I would suspect that there is a hardware issue.
This sounds like what happened to my phone as well. Someone else had it happen too. That's 3 nexus's in a week. Mine didn't even last 2 months.
I have a thread about mine and another user posted another thread a day or 2 ago. Mine boots into the system but is not erasable, not writable. Can't lock my boot loader. I've tried odin, adb, everything possible. I wish we could start a lawsuit because Samsung won't help me. I'm in the US and it's a gsm nexus that was purchased before the play store sold it. USA wont accept an international phone and UK Samsung won't take a phone from overseas. Basically they said I'm sh*t outta luck.
Thanks again for the help. I'm going to bite the bullet and just call the insurance company and try to send it back as a defective device. Hopefully they don't rake me over the coals.
I'll post back with an update as to how that goes.
You guys need to learn how to use fastboot and adb commands correctly to restore google's stock images.
Stop realying on toolkits thinking it will help you.
Also learning that the Red Exclamation Android is stock recovery!
Press the Power and Vol Up button will get you the stock recovery menu options to come up!
Not to be mean, BUT I hope the insurance company denies you, you totally screwed up the phone yourself.
I did not screw my phone up myself. My phone was never even rooted. I know very well how to issue adb commands and install images. Learn what you are talking about before you jump onto people or come across as a total di*khead
Alright, replacement phone is on the way. Thanks again for the help. I tend to think it is a hardware issue because of how the issue originally presented itself, but I'm still pretty new to the Android platform. It seemed to me that a watchdog timer was timing out or something similar.
Perhaps this will be the push I needed to start developing Android hardware/software... I'm all about embedded systems and would like to move beyond basic ucontrollers.
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
gjtoth said:
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
Click to expand...
Click to collapse
Surprisingly, there was nothing wrong with the phone nor the software nor the PC. After screwing around with this for a couple of days, I had a thought to try a different USB cable. So, I popped it on and, lo & behold, I'm able to flash to stock! Lesson learned: Don't use cheap cables and try changing cables when you're have weird problems like this. :good:
I'm trying to prevent having to use the warranty if I don't have to as this was just a mistake on my part.
I've tried going completely back to stock removing TWRP and everything and I'm in the stock recovery right now with the error that says:
"Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Which I've done twice now (since going back to stock bootloader) and nothing happens.
These are the steps I took-
downloaded factory ota image.
flashed flash-all.bat
moved boot.img to adb directory and flashed boot image on both a & b slots
ran flash-all.bat again (just in case)
start up & get the loading G screen that either never stops loading or refreshes to this screen with the error above.
I tried locking the bootloader and that just caused a "no os" error. So I unlocked it, re-ran flash-all.bat and now I'm back with this error. I mean at least I can get into the bootloader & recovery?
I'm going to try pressing the 'try again' about 20 times in a row. I saw something online that said pressing try again that many times it randomly worked. I'm still searching and trying to figure this out but that is going to be my next step while I search.
I posted this on reddit about an hour ago but still no responses so I wanted to reach out here as well.
Just for more information: I am able to get into stock recovery & bootloader just fine. It is just the OS that doesn't want to load. I have factory reset this thing more times than I can count. I've tried flashing the images google has up. I did the very first one and the 8.1.0.
Neither are working & I don't understand why. The ones that are listed here.
Just for kicks here is a screenshot of the whole window and what happens during the flashing in the flash-all.bat. Here they are.
HELP?
While I was doing those screenshots I fixed it! I downloaded 8.1.0 (OPM1.171019.011, Dec 2017) just for the heck of it since the others weren't working. Figured it wouldn't hurt anything, would just cause the same error to appear and it took longer to install, which I figured was good, AND NOW I WAS ABLE TO GET INTO THE STARTUP SCREEN! WOO!
DudeThatsErin said:
I'm trying to prevent having to use the warranty if I don't have to as this was just a mistake on my part.
I've tried going completely back to stock removing TWRP and everything and I'm in the stock recovery right now with the error that says:
"Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Which I've done twice now (since going back to stock bootloader) and nothing happens.
These are the steps I took-
downloaded factory ota image.
flashed flash-all.bat
moved boot.img to adb directory and flashed boot image on both a & b slots
ran flash-all.bat again (just in case)
start up & get the loading G screen that either never stops loading or refreshes to this screen with the error above.
I tried locking the bootloader and that just caused a "no os" error. So I unlocked it, re-ran flash-all.bat and now I'm back with this error. I mean at least I can get into the bootloader & recovery?
I'm going to try pressing the 'try again' about 20 times in a row. I saw something online that said pressing try again that many times it randomly worked. I'm still searching and trying to figure this out but that is going to be my next step while I search.
I posted this on reddit about an hour ago but still no responses so I wanted to reach out here as well.
Just for more information: I am able to get into stock recovery & bootloader just fine. It is just the OS that doesn't want to load. I have factory reset this thing more times than I can count. I've tried flashing the images google has up. I did the very first one and the 8.1.0.
Neither are working & I don't understand why. The ones that are listed here.
Just for kicks here is a screenshot of the whole window and what happens during the flashing in the flash-all.bat. Here they are.
HELP?
While I was doing those screenshots I fixed it! I downloaded 8.1.0 (OPM1.171019.011, Dec 2017) just for the heck of it since the others weren't working. Figured it wouldn't hurt anything, would just cause the same error to appear and it took longer to install, which I figured was good, AND NOW I WAS ABLE TO GET INTO THE STARTUP SCREEN! WOO!
Click to expand...
Click to collapse
You tried fastbooting the "factory OTA image" Well, that mistake number one. Just use the stock factory image, not the OTA.
Never mind.?
Congrats on fixing it.
For future reference, and if you ever reset your phone again, you should perform: fastboot flashing unlock_critical <--this will wipe your phone!
As you can see in your screenshots, that failed, each time. This was the cause of your failure(s): FAILED (remote: Flashing is not allowed for Critical Partitions)
The last one worked because it flashed the proper bootloader (TMZ12a). Had you not used that image, it still would have failed.
What was your fix?
@DudeThatsErin -As mentioned by uicnren, you still need to unlock_critical or your phone will not upgrade properly, and you won't be able to flash full factory images. When you unlocked your bootloader, there were two steps but you only completed the first one. See the sticky by Nathan for step-by-step instructions. Unlocking critical will wipe the phone again, but then you will be set.
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
threehappypenguins said:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
Click to expand...
Click to collapse
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
sdembiske said:
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
Click to expand...
Click to collapse
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
threehappypenguins said:
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
Click to expand...
Click to collapse
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
sdembiske said:
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Here's what I've done now at this point. I tried creating and flashing a 2 core boot image via fastboot, and then flashing the 2 core TWRP. Still bootloop.
I flashed the v29a N modem and UsU kernel for my device (H812), then went to TWRP and flashed stock N ROM again. Still bootloop.
I flashed N stock modem again, then baseband package for my model. Still bootloop.
I'm about to extract my MM modem and flash that.
Beyond that, I don't know what to do. I had zero issues with the UsU method originally and everything went fine and has been fine for the last couple of months since I did it.
Well, roadblock again. I attempted to extract modem from the kdz with SALT in FWUL, and after a while, I get a popup window that says: "This KDZ has an ARB of: arb-detect-error" and then it says "Select partition(s) to EXTRACT:"
Except there are no partitions to select. And my only options are "Deselect All" "Extract" and "Abort." If I try "Extract," I get the error, "No partition selected or abortioned by user."
I did make sure I had the latest version of SALT.
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Code:
fastboot flash modem modem_32768.img
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
threehappypenguins said:
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
Click to expand...
Click to collapse
Read about the ilapo it can't be fixed by software it may just help to enlenghten life.
Sent from my OnePlus 6T using XDA Labs