Related
So I rooted with Odin using the "SPH-D710_Zedomax_Kernel.tar" and then unrooted with Odin using the "acs-eg30-stock-kernel-pulled.tar". Once I unrooted everytime I boot my phone up I get this error message:
'gaudi_bootimage.jpg' draw failed
and I boot into System Recovery (manual mode), and if my phone is plugged into laptop or wall charger when I power down I receive the following error message
'charging.jpg' draw failed
Even when I root back, it still always boots into recovery mode and boot up error message is replaced with the Galaxy S2 GT-I9100 splash screen, but I still get the 'charging.jpg' draw failed error.
On both occasions (root or unroot) I can still select reboot system now and the phone finally boots up fine, but I'm trying to eliminate the jpg boot and charge error messages and boot directly into he phone without having to select it in recovery. I have done a complete factory wipe with the same results as described above. Any suggestions?
try reflashing the stock pulled .tar file? and a nandroid backup/stock OS?
Looks like some files may be corrupt.
GH0 said:
try reflashing the stock pulled .tar file? and a nandroid backup/stock OS?
Looks like some files may be corrupt.
Click to expand...
Click to collapse
I have tried reflashing the stock pulled .tar file and resetting to factory defaults, neither of these worked. Are the files 'gaudi_bootimage.jpg' and 'charging.jpg' something I can place in a specific directory that will avoid this boot up into recovery problem? I'd like to overwrite those potential corrupt files with good ones.
They are in /mnt/.lfs
I'll see if I can pull them and post for you.
Oh wow!
There's a treasure trove of stuff in this directory. I think it's hidden but using Android Webkey I got to it. I'll post some other "boot" images from here. The initial "Samsung Galaxy S II" image isn't the only one. I like the Iron Droid one, though it doesn't seem complete.
Anyway, here's the .zip of all the images in that directory.
I saw you wiped fator reset. But dis you also wipe the cache and dalvik? Then do clean install with CWM 5.x.x.x ? I would recomend that id u haven't tried thus yet
eph5networks said:
So I rooted with Odin using the "SPH-D710_Zedomax_Kernel.tar" and then unrooted with Odin using the "acs-eg30-stock-kernel-pulled.tar". Once I unrooted everytime I boot my phone up I get this error message:
'gaudi_bootimage.jpg' draw failed
and I boot into System Recovery (manual mode), and if my phone is plugged into laptop or wall charger when I power down I receive the following error message
'charging.jpg' draw failed
Even when I root back, it still always boots into recovery mode and boot up error message is replaced with the Galaxy S2 GT-I9100 splash screen, but I still get the 'charging.jpg' draw failed error.
On both occasions (root or unroot) I can still select reboot system now and the phone finally boots up fine, but I'm trying to eliminate the jpg boot and charge error messages and boot directly into he phone without having to select it in recovery. I have done a complete factory wipe with the same results as described above. Any suggestions?
Click to expand...
Click to collapse
Hello, I got the same problem as you. I still don't know how to do it. please, Let me know if you know any way to fix it. Thanks
KCRic said:
They are in /mnt/.lfs
I'll see if I can pull them and post for you.
Oh wow!
There's a treasure trove of stuff in this directory. I think it's hidden but using Android Webkey I got to it. I'll post some other "boot" images from here. The initial "Samsung Galaxy S II" image isn't the only one. I like the Iron Droid one, though it doesn't seem complete.
Anyway, here's the .zip of all the images in that directory.
Click to expand...
Click to collapse
Alright a quick update (not positive):
I copied the files onto the /mnt folder, but unfortunately after I copy them they still don't appear in the directory. I reboot and I still receive the same 'gaudi_bootimage.jpg' draw failed & 'charging.jpg' draw failed. I do have root access by the way and I'm copying these to the directory using Root Explorer.
I also took the following steps:
Installed CWM 5.0.2.3
Performed a nanroid backup
formatted the system volume under 'mount and storage'
wiped data/factory reset
wiped cache partition
wiped dalvik cache
All that still with no success.
Another thing I'm noticing is when these error messages show (on boot & after power down while connected to charging source) it automatically boots into recovery. There has to be some way or place these files are being called for me to replace them to make this annoying issue go away. Any more suggestions?
So you have tried reinstalling CWM to see if it helps?
Seems (no expert here) that something is corrupted. Not sure exactly what but possibly part of the internal storage or the primary or secondary bootloader. I really hate to jump to something that extreme but i just don't see another reason it would be acting up like that.
I would download CWM one more time and check the MD5 before using ODIN to flash it. If it still does it - return to stock (remove the yellow triangle if you have it) and take it back to the store. Should be under warranty still.
Did you ever solve this problem as i have the same issue.
sscoleman said:
Did you ever solve this problem as i have the same issue.
Click to expand...
Click to collapse
Unfortunately none of these options resolved it. Still pending.
got d boot image running....
Hey i 1st got a stock samsung boot .zip file and den used sgs2 boot changer to apply d img it worked....!!!! Thank got for dat .... Still dont knw wat to do abt d charging. Jpg though... D app works for dis model too... Try it out....
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
Well... I installed Vicious V2 of the Jellybean ROM (toro), and things were running OK. I used titanium backup to try to restore my SMS data, and found that I could not boot back up. It just bootloops. Since then, I have tried mutliple things, but nothing ends it...
I've tried:
*Restoring a NANDroid, but /data will NOT restore, and phone will bootloop.
* factory Reset/reinstall old AOKP ROM. It will not boot.
*Reinstall Jellybean ROM. Still bootloops
*I'm working on trying to get ODIN to detect my phone, but my computer won't stop detecting it as "Samsung ADB Interface". I've verified there is no response from ADB while in ODIN mode on the phone.
I just... can't stop the bootloops. There is another thread of the same issue, but his resolved over time. Mine doens't seem to be... I really want my phone to boot. The interesting thing is that none of my Nandroids will restore "Data". It just says "Completed in 0 seconds"
Are you able to use fastboot?
Sent from my Captivate
Yes.
Speaking of fastboot, I can re-flash my recovery just fine. I've tried everything on both Clockwork, and TWRP. Results are the exact same.
Same thing
Mine did the exact same after installing the same ROM after a TiBu restore (no system apps, no sms just regular apps with data). I tried wiping/reflashing several ROMs I had on the SD to no avail, all my nandroids would fail to restore data. I finally ended up using the Odin method I found to flash it back to stock 4.0.2 unrooted, unlocked. I lost all of my data on the SD card in the process.
I loved JB and would like to install again if I could find out what I did wrong to avoid this mess, any input guys?
Just a note: In recovery you have access to ADB. You can backup your SDcard with the command "adb pull /data/media C:\SD_backup"
It will save to... C:\SD_backup
If you get a file not found then, "adb shell", then "mount data", then "Exit", then try the adb pull again.
I'll keep messing with drivers then to see if I can get ODIN to detect me.
I'm an idiot. ODIN was seeing my phone the whole time. I just forgot where it shows that the phone is connected. I'll try an ODIN in the morning. I'm backing up my SD right now. I need sleep.
Edit: Nevermind.. It doesn't see it while in Odin mode.. but does see it on and off while booting into recovery.
Edit 2: I found that it was indeed a driver error. Fixed. Now back to backing up my SD card that I accidentally interrupted. I'll report back my ODIN results after I wake up.
my phone is doing the exact same thing
I was able to bring my phone back to life with ODIN restoring a 4.0.2 factory image.
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
LordKyleOfEarth said:
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
Click to expand...
Click to collapse
LordKyleOfEarth said:
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
Click to expand...
Click to collapse
If it is your original TWRP backup (TWRP that Freegee installed) it might not restore, I had that problem a long time ago. Try installing an updated TWRP, that one is really old at this point.
If you have an updated TWRP you can mount MTP from recovery and transfer any files to your internal storage. I suggest starting out with the stock ZVC so you can have a fully working stock device and make sure everything works. From there you can copy zips to your device and flash away.
If you have issues copying a recovery to your device you can always use adb to flash. I believe it is
"fastboot flash recovery (name of recovery.img)" without quotes or parenthesis.
EDIT: On the CM 12 setup thing, @Shelnutt2 just posted in the CM12 thread that the bug is fixed and will be pushed to tonight's nightly.
Here is a newer recovery built by an international dev but this is the one I used when I had the OG.
http://dl.kevinjoa.me/recovery-geehrc/twrp/