Database Develop

Some Roms just won't flash.

Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.

Maybe he dont follow the instructions correctly
Sent from my GT-N7000 using xda premium

meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
What method is he using to flash? If using pc Odin does the flash get stuck at factoryfs. Img?
Was he on ics stock and did he perform any factory resets on it?
If answers are yes, it's likely he's got traces of damage on his emmc chip, but we need to know where the flash is failing to understand further.
Sent from my GT-N7000 using xda premium

No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex

meminiau said:
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
Click to expand...
Click to collapse
Try flashing rom with pc odin instead of cwm.
Check out Dr ketan sticky thread in rom development for directions on how to use pc odin. It's simple.
Let us know how you progress.
Sent from my GT-N7000 using xda premium

meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
No problem at all.
Sent from my GT-N7000 using xda premium

What?????
Swiped on my Gnex

Sounds very odd - only though is he's not following instructions correctly..

Semi brick. Need help

Basically I've screwed over my phone.
It WILL boot. However I can't get it to go into USB mode.
I'm on Android 2.3.5 and I have this rom installed. http://forum.xda-developers.com/showthread.php?t=1779290
When I try to flash from a backup, it fails flashing system and renders my phone a brick until I reinstall the above ROM
I've also tried going into download mode so I can use the official LG updater to flash it back completely stock. However I can't seem to get that working.
Any help is appreciated. Thanks.

DracoAzule said:
Basically I've screwed over my phone.
It WILL boot. However I can't get it to go into USB mode.
I'm on Android 2.3.5 and I have this rom installed. http://forum.xda-developers.com/showthread.php?t=1779290
When I try to flash from a backup, it fails flashing system and renders my phone a brick until I reinstall the above ROM
I've also tried going into download mode so I can use the official LG updater to flash it back completely stock. However I can't seem to get that working.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
First you are posting in the wrong section.
Second, what baseband do you have installed. I am running on a Froyo baseband and can't run thrillseeker due to the baseband requiring the GB baseband. You can probably return to stock by using this guide http://forum.xda-developers.com/showthread.php?t=1491870
From what I am reading, the LG Updater sometimes will fail but you just have to continue using it.
Good luck with your issue. I am planning to do the same to my nephews phone later today. If i can figure something out I will post back.

I think its V20P which is Gingerbread. I know when I last updated it I used the official updating tool and grabbed it from their server. But again I'm on Android 2.3.5 Gingerbread. Will those update.zip files work?
Sent from my LG-P925 using xda app-developers app

DracoAzule said:
I think its V20P which is Gingerbread. I know when I last updated it I used the official updating tool and grabbed it from their server. But again I'm on Android 2.3.5 Gingerbread. Will those update.zip files work?
Sent from my LG-P925 using xda app-developers app
Click to expand...
Click to collapse
Everything works except USB ?.....does the phone charge through USB and just doesn't give you the option to connect SD cards?
Sent from my LG-P925 using xda premium

Bdadd34 said:
Everything works except USB ?.....does the phone charge through USB and just doesn't give you the option to connect SD cards?
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Yea it charges but that's it.
Luckily I have SwiFTP installed on my phone so I can still transfer things back and fourth between my phone and PC over my home network via FTP. Just much, MUCH slower.
EDIT: I just realized why this was in the wrong section. I TOTALLY thought I was posting in the general forum. Sorry. *derp*

Bump

First thing uninstall LG PC drivers then reboot PC and reinstall them. Or try to connect to a different PC to make sure it is not PC related. If that doesn't work then try wiping caches and instsall a different kernel. If that doesn't work I would then try full data wipe and reinstall rom of choice. You might try different rom as once its fixed you can always flash back...hope this helps you.
Sent from my LG-P925 using xda premium

Well I believe I've figured out what the problem was.
You see the other day while I was charging the phone I accidentally knocked it off. The USB cable got caught on my alarm clock and caught the phone, so the phone was hanging by the USB cable.
Well today I looked at the connector on it and I noticed it was bent a little. So I bent it back up and heard a small *click*
I was afraid I had broke it completely inside. However when I plugged it in my computer recognized my phone and USB mode showed up.

[Q] Samsung splash sound but no display. HELP!

Hi everyone, as you can see I am a n00b and am in need of help.
Basically I upgraded my n7000 after running a German version of ICS (4.0.4 I believe) to the latest UK Jellybean. All worked well except that JB is pretty slow and totally drained my battery. After becoming frustrated I decided to try to flash my phone back to ICS and found a uk/Ireland version (4.0.3). I popped the phone into download mode and ran Odin successfully. Jobs a good one.....until I tried to restart my phone. It appeared to boot up as I could hea the Samsung splash tune, however the LCD didn't light up, nor any of the touch buttons. In a panic I tried to revert the phone back to JB which appeared to work except I still have the LCD/ touch button problem.
So, can anyone help at all? I can put it into download mode and connect it to Odin however KIES doesn't appear to see the phone when it's on and plugged in. Should I send it for a JTAG repair, or can this be fixed via the PC?
Thanks in advance!
Kev

Kevrobot said:
Hi everyone, as you can see I am a n00b and am in need of help.
Basically I upgraded my n7000 after running a German version of ICS (4.0.4 I believe) to the latest UK Jellybean. All worked well except that JB is pretty slow and totally drained my battery. After becoming frustrated I decided to try to flash my phone back to ICS and found a uk/Ireland version (4.0.3). I popped the phone into download mode and ran Odin successfully. Jobs a good one.....until I tried to restart my phone. It appeared to boot up as I could hea the Samsung splash tune, however the LCD didn't light up, nor any of the touch buttons. In a panic I tried to revert the phone back to JB which appeared to work except I still have the LCD/ touch button problem.
So, can anyone help at all? I can put it into download mode and connect it to Odin however KIES doesn't appear to see the phone when it's on and plugged in. Should I send it for a JTAG repair, or can this be fixed via the PC?
Thanks in advance!
Kev
Click to expand...
Click to collapse
Thats an odd one really, but I would try flashing stock GB with pc odin, there are many fewer flash problems with gb and it's a good place to start.
Forget connection to kies, so long as you can connect to odin.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Thats an odd one really, but I would try flashing stock GB with pc odin, there are many fewer flash problems with gb and it's a good place to start.
Forget connection to kies, so long as you can connect to odin.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for the prompt reply SpyderTracks, I will give that a whirl. Any reccomendation of where to get a decent stock GB as I tried from Sanmobile and they only seem to have later ICS and JB. I did try to download a copy from an old thread on here but I couldn't unzip the file with win zip or winrar both said "unknown compression type" when I tried to extract even though I could see the tar file inside. :S
Kev

Kevrobot said:
Thanks for the prompt reply SpyderTracks, I will give that a whirl. Any reccomendation of where to get a decent stock GB as I tried from Sanmobile and they only seem to have later ICS and JB. I did try to download a copy from an old thread on here but I couldn't unzip the file with win zip or winrar both said "unknown compression type" when I tried to extract even though I could see the tar file inside. :S
Kev
Click to expand...
Click to collapse
Try the unzip with 7zip, winzip won't handle it and winrar is a bit old school.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Try the unzip with 7zip, winzip won't handle it and winrar is a bit old school.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
POW! The phone lives!!! Thanks for your help mate. Just stuck on the android system recovery now, so will have a read up on that.
Kev

Great stuff, should be easy sailing now. Best of luck.
Sent from my GT-N7000 using XDA Premium 4 mobile app

Mine did that when I put the DBT release 4.1.2 on my phone, then put a custom kernel. Reflashed it several times with
no luck, then, tried a kernel from a different developer and it worked just fine. Downloaded the original kernel I was using
(speedmod) and flashed it again, and sound but no lights. Put Philz kernel back on it and it worked. Not sure what the
deal was, but with my device, the DBT LT5 rom and speedmod, I couldn't get any video.

Thanks SpyderTracks all working now, battery is a bit iffy but I think that is hardware more than anything else, I've changed the charge port and it's the same. Both batteries are fine in my girlfriends phone though. Hey, at least it is alive!
P51D - yeah I got totally worried, it's really odd, plus I couldn't really find anyone else who had this problem when I was searching. Thought I may have had to go for the JTAG route.

In my 40 + years of fixing electronic circuits, I've always found that troubleshooting ALIVE, although not working properly, is a hell of
a lot easier, than troubleshooting DEAD
Kevrobot said:
Hey, at least it is alive!
.
Click to expand...
Click to collapse

Has anyone else gotten this while rooting?

Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers

Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.

Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops

That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?

That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..

Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.

I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.

Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers

[q] help help help

So I tried rooting my Samsung Galaxy Note 3 SM-N900A with Odin but it went wrong somewhere along the way and now the phone won't start up. When I try to start up, the screen says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" But when I tried to recover in Kies, it always gets to the end and then says that the PC can't recognize my mobile device. I can still access download mode but that's about it. I have tried looking EVERYWHERE and there is no solution! someone please help! D:
Also, I found something online that says that I can recover through Odin and I went through the whole process but when I start flashing, it says FAIL so that didn't work for me either

Did you use RDLV on MJ5 to root? If so, that's probably what bricked you.
Sent from my SM-N9005 using Xparent Red Tapatalk 2

U will prolly need to flash from scratch using the pit file
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

antiguangenius said:
U will prolly need to flash from scratch using the pit file
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Click to expand...
Click to collapse
What's the pit file?

becky0251 said:
What's the pit file?
Click to expand...
Click to collapse
That just showed off why your phone got bricked. Rooting a phone got some responsibility. Let this be a lesson for you and read before you root. You will need to download the stock firmware and flash this through Odin. I guess you still can enter Download mode?

Wi-Fi Issues
I also need some help here... I did successfully root my note 3, however whenever I install a custom rom such as knoxraid or azure, my wi-fi will not work at all.
The wi-fi will be on from a clean flash, but once I try to connect to any network (I've only tried those with passwords), the wi-fi grays out and I can no longer turn it on or off. I haven't encountered anyone else with the same problem, and I have tried deleting the rom partitions and recreating them.
Disclaimer: I don't have enough posts to post in the dev forums, so that's why I'm posting here. Sorry about that.

Dearest Becky, im so sorry girl..
butchya may be fuct for a lil while let me tell ya why..
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Sister!!
Please let us know how it goes. I think there are many brothers and sisters desperate as F and in ypur same predicament.

This is your best bet.
If you can get into download mode or should work
http://forum.xda-developers.com/showthread.php?p=48243768
Sent from my SAMSUNG-SM-N900A using xda app-developers app

mrkhigh said:
This is your best bet.
If you can get into download mode or should work
http://forum.xda-developers.com/showthread.php?p=48243768
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
THANK YOU SO MUCH! this worked :good:

all i did is using kingo, it work perfect.
来自我的 SM-N9005 上的 Tapatalk

Glad it worked
For anyone Reading this thread for similar issues
What probably happened is she attempted to root de LA Vega method while she was on firmware mj5 rdlv method is based on mi9 and die to this it will soft brick your device.
Unfortunately att diff not release an Odin file for mj5 or even put it on kies.
One of or members figured out how to fiddle with the files we have access to to flash a hybrid of mi9 and mj5
Making it possible to more or less recover from an mj5 brick.
Follow his steps completely and you will wind up with a stock rooted os.
But since this is such an odd way to recover I chose to use kingo to root.
Xda doesn't support kingo dir to hour closed they are in their methods and the fact it is not apparent how they are funding themselves. so you'll have to Google it. It was one of the easiest root methods I've done on a device it installs chainfires su. It is completely removable and I personally believe it is the lest chance of a brick method.
Sent from my GT-P3110 using xda app-developers app