Database Info

(Q) Odin 3 flashing kernel issue

What would start causing this to happen?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am very familiar with the process. Rooted, sideloading for apps is all done. I have flashed my device with JM2, JH2, and the 1.2 OC. Now when I try to flash it doesn't work. I tried last night with no luck. I decided to master clear the device since I was having issues and wanted to start back with a fresh device. Now after trying to flash the JH3 from JF6 with Unleash the beast it wont work.
I also tried flashing with one click root, and superrooter from a fresh Odin one click. Usb debugging is enabled, Odin opened and then get into download mode. So my process from when it would work is now not working haha? So beyond my confusion of what I might be forgetting can anyone think of something that might help? I didn't want to put this in the dev section since there is nothing specifically made up for odin 3, only odin one click restore.

Your drivers are messed up... grab the ones from the odin thread and reinstall with the phone plugged in and in download mode.

designgears said:
Your drivers are messed up... grab the ones from the odin thread and reinstall with the phone plugged in and in download mode.
Click to expand...
Click to collapse
Reloaded the drivers and still get the message. Any other suggestions would be helpful.

Try un-selecting the other options? (auto reboot/time)
I had a similar error message when the "repartition" was selected. Just an idea...

Gave that a shot but no luck
I am almost resigned to the fact I might be stuck with JF6 until Froyo gets pushed out OTA (if/when that happens). I just can't believe it has me this stumped.
Can busybox, the older superuser, anything like that cause this issue? When I wiped back to stock I loaded Unleash the beast because I prefer the older superuser (ninja guy). When I first got my phone I did the adb code for sideloading after doing one click root. That process isn't different from what the guys that made the UTB and Superrooter update.zip files is it?
Well tried running Odin as an administrator and that didn't work haha. Worth a shot.

I dont really know if that could be the cause or not. Im actually having trouble wiping all the data from my phone (I have my own thread, but it could be related). I used Odin 1 click, I used the regular Odin and did everything manually, tried master reset, and also did a factory data reset. Tons of data still on my phone, though. I was contributing it to titanium backup, but it may be things installed from super rooter

Anyone else have an idea that I might try?
Now even Odin one click comes up with this message??? I am really baffled with this situation.
Update: Got Odin one click to work again, I wiped my user data through clockwork. After this reloads I am going to try and do sideloading via the adb codes rather then using UTB or superrooter to see if that makes a difference for me. Still could use any suggestion on what else people have tried in this situation, if you have been in this before.
Sweet life

Still stumped by this issue if anyone has any help for me. Also could this be moved to the new Q&A section. Thanks.

flashman2002 said:
Still stumped by this issue if anyone has any help for me. Also could this be moved to the new Q&A section. Thanks.
Click to expand...
Click to collapse
Do you use the Kies program and if so has it ran an update lately, I had it on my Win7 laptop and when it ran the software update it totally hosed up my drivers and I could not connect to my phone anymore... I had to uninstall Kies and remove all my drivers and then reboot my laptop then I only reinstalled the Samsung drivers and now I can connect again. I won't be using Kies anymore..Anyways I thought I would share my experience in case it might help you..

jhernand1102 said:
Do you use the Kies program and if so has it ran an update lately, I had it on my Win7 laptop and when it ran the software update it totally hosed up my drivers and I could not connect to my phone anymore... I had to uninstall Kies and remove all my drivers and then reboot my laptop then I only reinstalled the Samsung drivers and now I can connect again. I won't be using Kies anymore..Anyways I thought I would share my experience in case it might help you..
Click to expand...
Click to collapse
I haven't used kies since I first got the phone to put contacts in. But I just tried again to give it a whirl and got it to load the kernel. Hell if I know why it worked today compared to before hahaha.

Samsung Infuse bricked

I've been lurking here for a long time, and had all kinds of fun flashing my HTC Fuze, Tilt 2, and Samsung Captivate. I now have an Infuse. I've had it for a while, and it's been rooted for a long time, but due to slow support here on the forums for it, and the fact that AT&T it taking forever with Gingerbread, I decided to wait a while to try to flash Gingerbread.
So, I finally decided by looking at the Gingerbread roms coming out that it was time to try to flash. I spent quite a few hours reading threads here on the forums, downloading gtg's unbrick, the Heimdall one click, and other files. I also finally got CWM installed on my phone. (Blue version).
So, I chose to use the Heimdall one-click to flash my phone to gingerbread and get the gingerbread bootloaders. I fired up Heimdall, installed the driver, clicked flash, and watched it go. Unfortunately it DIDN'T go. It stopped pretty much instantly. I figured no problem, there was no way it had had time to alter any files yet. WRONG. All I get when I turn the phone on now is a solid white screen. It did give me a multi-colored pixel arrangement at first, but now it's solid white. Odin will still recognize the phone, but it stalls as soon as it gets to factoryfs.
Any suggestions? Or am I fully bricked?

If u can get to download mode use Odin...much better in my opinion
Sent from my SGH-I997 using xda premium

Odin recognizes the phone. It tries to flash but stops once it gets to factoryfs. (Using GTG's Ultimate Unbrick). Also, even tho I'm pretty sure the phone is getting into download mode because Odin recognizes it, the screen stays completely white.

Try a different USB cable, a different USB port or a different computer. My rig got to the point that it would fail just like you are describing 90 percent of the time
I finally gave up and used heimdall to flash a kernel only, then I used cwm to flash a ROM from a zip. You don't have to use ultimate unbrick, just unbrick manually by flashing only a custom kernel. Any kernel will do, just not stock
I reinstalled windows a few Weeks later and it has flashed perfectly with heimdall and Odin ever since.

Tried all of those so far except a different cable. Gonna try the cable from my old captivate.

The problem with hemidall is that if your not experienced using it you can do more damage than harm..you can ask dani897 if he knows how to fix it since hemidall caused it
Sent from my SGH-I997 using xda premium

Well seems like the cable was the issue. I noticed the old cable from my captivate feels thicker and heavier. Dunno why. Gonna try working with it a bit more. My screen is working again tho.

Well, I have to say thanks to Demonspork! Using my other usb cable did the trick. I'm gonna save that cable just for flashing. It took a couple flashes with GTG's Ultimate Unbrick to finally get it to the point of fully booting up but I'm good to go now.

I'm assuming you're running ubuntu like I am since you used heimdall. Often times you will get rainbows when running heimdall... Not sure why though.
you can either run gtg's unbrick through wine on ubuntu, or use a windows machine to revert to stock.
The infuse is impossible to brick... Trust me, I've had more than, my share of issues.

Trouble! Got a brick
I have 2 Samsung Infuse phones. I updated my phone easily. I tried my wife's phone with the anti-brick program and this is what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cant get anything other than this. Is there anything i can do about this? My wife is ready to kill me.
Thanks

That is still download mode. Try to Odin/heimdall a compatible package. Not real sure what you are doing. Gingerbread leaks?
Sent from my SGH-I897 using Tapatalk

odin3 v1.7 should work with your device... I have bee doing my infuse again and again... now i have 2.3.6 but it is too slow and catch lots of heat while charging.. so i don't give damn i am downgrading to frayo.. just put in download mod and odin should recognize your device...

Yeah, the !--->(PC) screen just means, "OK, you borked up my system, but I'm in download mode and ready for you to install a new one!"
IF you were using HEIMDALL, try downloading your ROM to the phone again. If it doesn't work, you may have to select the option to install a kernel as well. I bad to do this a couple times. However, always FIRST try without install a new kernel.
(Please correct me if the above is wrong...I mean if whatever the OP is talking about needs a new kernel...)
Also, what difference would a different USB cable make? Just curious. Is it just that the first one the OP tried was faulty?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Ok. I used Odin3 v1.70.
First time around I used PIT, PDA and Phone. That is when I got the first screen. This time around I used PDA. Thats when I got this screen. Its just stuck there now for the last hour.
I'm going to try another program.

Ok. I used Odin3 v1.70.
First time around I used PIT, PDA and Phone. That is when I got the first screen. This time around I used PDA. Thats when I got this screen. Its just stuck there now for the last hour.
I'm going to try another program.
Click to expand...
Click to collapse
Odin 1.81 has worked well for me. I just check off PDA and point it to the tar.md5 file that comes with it.

Where do I get Odin 1.8?
Just reflashed with the original file and all is back to normal. Back to 2.2.1

fastvan67 said:
Where do I get Odin 1.8?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1092021

[Q] My atrix 2 is on the edge of dying. please help.

I'm really sorry if this doesn't belong here.
My atrix 2 (MB865 from Singapore) updated by OTA to ICS then rooted successfully and I installed custom roms (scv7 and swifty etc) and even mods (xLoud and Beats) but in CWM (Bootstrap + cwm-on-boot script) it would usually say ''installation aborted'' whenever I tried to flash a custom rom, which is pretty weird since I was using the correct roms for my device.
One day I decided to go back to stock ICS by flashing a ics fzw in RSD Lite 6.0 (I tried flashing 6.7.2_EDEM-18-SEARET_cfc.xml and 6.7.2_EDEM-18-ASIAOPS_cfc.xml) but every time it would stop at step 14/20 ''writing system.img'' but the progress arrows would still keep moving. So after an hour of waiting, I disconnected the phone from the usb cable and I got the black screen with Flashmode (Flash Failure) with ''cannot program'' and ''battery low''. Now the battery died and it won't even charge when I connect it to the wall adapter, it would only boot into the flashmode (flash failure) screen and when I turn it off and try to to it on again it won't. I don't think it's hardbricked because when the battery was still on, I could turn it off and boot back up into fastboot with options like normal boot or go to the stock android recovery.
What do I do now?

Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.

lkrasner said:
Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.
Click to expand...
Click to collapse
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance

aligex said:
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance
Click to expand...
Click to collapse
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Yes all of these things matter. You will need to do the McGyver method to charge your battery (lkrasner mentioned it as the diy method). It is in this forum, just Search for it.
After you get us the information I asked for above we will be able to better help you.
Also one last thing to check is to see if the MD5sum matches. If not you prolly have a corrupt download and that is why it may not be working as well.

With respect to our developers this will allow you to flash without a battery. It does nothing else useful but does get around the low battery issue
http://forum.xda-developers.com/showthread.php?t=1910027
There are other forms however being in Singapore may limit your options. Remember Google is your friend.

jimbridgman said:
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Click to expand...
Click to collapse
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.

matthew5025 said:
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.
Click to expand...
Click to collapse
That is great information! Thanks!

Really confusing softbrick (small reward offered for fix)

TLDR: LGUP will just straight up not recognize my G5 no matter what. I'll give you five bucks on Paypal for a solution, if that means anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi guys, I try to avoid posting, but I've searched high and low for an answer and I really can't find it.
I've got a T-Mobile LG G5 H830, that I have recently rooted and installed TWRP on it. Last night, I decided to try changing a value in build.prop, stupidly without making a backup first and after I changed the value and rebooted, stuck at T-Mobile bootscreen, go figure. All I did was change a value from false to true for adoptable storage..
Anyway-- I tried factory resetting, I tried flashing that FLUENCE rom I found somewhere here on XDA, I've tried just about every thing I could, before I gave up and decided it would be easier to just revert back to stock and unroot. I wasn't really utilizing root for more than Titanium Backup anyway.
To the point; I've got the LG UP program installed, I've got the DLL for it installed and inserted, and the appropriate .tot file to flash it back to factory default. No matter what I do, no matter how many different COM ports I try, different drivers I've tried etc, I cannot get it to read my phone in download mode. ADB mode works in TWRP still, but this is driving me insane. The only other phone I have is a busted up BlackBerry Priv, and I want this phone working again asap.
If someone can shed some light on whatever the hell I'm doing wrong, it would mean the world to me.
Please.
P.S: yes I've tried just about every USB port on my computer, and I've tried restarting Windows many times.

you have tried jiggling it?

You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.

speedanderson said:
You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.
Click to expand...
Click to collapse
Use the twrp restore file in the development thread it will revert your build prop back, and from there your phone will work again. Editing build prop is not advised on the H830 has been discussed on numerous threads even before root was established. At least it's only a soft brick .

Have you tried jiggling it perhaps?

so did @wolfu11 get the 5 bucks? his solution should have fixed it.

autoprime said:
so did @wolfu11 get the 5 bucks? his solution should have fixed it.
Click to expand...
Click to collapse
I don't know if he's been back on since his initial post.

wolfu11 said:
I don't know if he's been back on since his initial post.
Click to expand...
Click to collapse
Last Activity: Today 12:52 AM
good luck :fingers-crossed:

autoprime said:
Last Activity: Today 12:52 AM
good luck :fingers-crossed:
Click to expand...
Click to collapse
Not holding my breath lol. That's why I declined any of the root bounty.

Try manually pointing to either the lg drivers, or adb drivers had that same problem when trying to root H830.
Sent from my LG-H830 using XDA-Developers mobile app

IDK if u fixed it or not, but i have a simular issue where LGUP does not recognize my phone. i'm guessing it could be the buildprop could have broken it. i have factory reset my phone, but upon turning on wifi, the phone crashes and i need to factory reset. i am rooted and retain root. My guess is that changing the buildprop causes the phone to be unrecognized. I did backup my buildprop but its stuck in an encrypted backup. Thanks alot gooogle...

Same problem here
I am having the same problem but I never touched my build prop. I rooted and decided to install cm14. When i flashed, none of my partitions are mounting and phone would not boot. I put stock back on and flashed tot and tried mounting partitions and nothing. Now computer doesn't recognize it as well as it will not boot into recovery or android.

I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.

Barsky said:
I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.
Click to expand...
Click to collapse
ill give it a shot, thanks

Setting phone back to defaults for dummies

It doesn't appear anybody knows what to do with this http://forum.xda-developers.com/general/xda-assist/incoming-calls-answered-vener-make-to-t3500914 and I now have to go back to full factory stuff with no custom recovery and stock os to find out if this is a hardware issue. I did a TWRP restore from several months ago when the phone worked fine and it still has the incoming call issue from the link above. Did a factory wipe in Teamwin, same thing.
Rooted Sprint Galaxy S6 on Lollipop 5.1.1 with Teamwin recovery
http://tiribulus.net/pix/Phone/1.png
http://tiribulus.net/pix/Phone/2.png
Please pretend than I am a not particularly precocious ten year old who needs to make this phone as if I just took it outta the box. I have searched here and around the web. All I find elsewhere are paid download sites or 3 hour downloads and here I can't make heads nor tails out of the volumes of impressive information in these forums.
I do have PC skills, and this is my first smart phone and getting it rooted and the recovery installed and all that wasn't too tough back when I got it 15 months ago. It appears restoring it back to stock is quite a bit tougher.
I have to see if incoming calls still don't work when the machine is totally stock. Is there a way to do this without a 3 hour download and a masters in computer science? I sure would be most grateful for any help with this.
Thank you.

You can simply do "Rescue firmware" via Smart Switch.

forumber2 said:
You can simply do "Rescue firmware" via Smart Switch.
Click to expand...
Click to collapse
Thank you sir! I will have a look at this a bit later tonight when possible.

This won't work with Teamwin recovery right?

I have none of the boot options in this video. Not that I don't appreciate it.

I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.

http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448

brenner650 said:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Click to expand...
Click to collapse
I appreciate that sir, but like I say, I never get step 4. It doesn't exist for me. As soon as I click the device initialization tab I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I proceed, I get this:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix. That's what started this whole thing:
http://forum.xda-developers.com/spr...er-make-to-t3500914/post69641921#post69641921

Tiribulus said:
I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.
Click to expand...
Click to collapse
You won't do anything on TeamWin.
1. Open Smart Switch on PC.
2. Turn Off the phone. Press Volume down (not up) & Home button & power button. When you see the warning screen, just press volume up once. If you see "Downloading" screen, plug into PC
3. Do "Rescue Firmware" via Smart Switch.
Thats it.

Tiribulus said:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix.
Click to expand...
Click to collapse
Well they had to write that, because if something happens during flashing it is not their fault, and you have been warned.
You can also uninstal supersu, and download that same fw Smart Switch would install from another internet source, and it will probably be a painfully slow download, but that is up to you.
I cannot guaratee you that Smart Switch emergency initialization would solve your phone issues, but it is the way to unroot and for the phone to become officially stock, offcourse knox will stay tripped if it was tripped during rooting (and probably is, unless you are on 5.0.2. and were using ping pong root).
I used Smart Switch emergency a lot, and it was always succesfull, just follow instructions, connect your phone in dowload mode when it asks for it, and there should be no problems getting to stock.
...I saw just now, in your other topic that you have fixed it /thumbs up!