Related
Friend of mine flashed wrong rom. Now phone won't turn on at all. Any solutions?
sent from your moms house
A little more details then that.
GINGERVOLTED!
nap286 said:
Friend of mine flashed wrong rom. Now phone won't turn on at all. Any solutions?
sent from your moms house
Click to expand...
Click to collapse
A few questions first:
What ROM did he try to flash?
Did he try to flash it through Clockwork Recovery or ROM Manager?
When you try to turn the phone on, does the backlight come on the screen or anything? Or does it just sit there without even making an attempt to turn on?
Flashing the wrong ROM would not hard brick your phone. The install of the ROM would simply fail. If anything, it sounds like your friend tried to flash a ROM and the battery either died or was taken out during flashing. Please post back so we can all try to help.
He is talking about me
I flashed it through CWM and went to restart and now the phone is dead
No lights nothing no vibrate it simply will not turn on
flashed it with
O2X FLAIR GB v4 REVOLUTION FINAL (based on LG v20L)
for optimus
From what I am thinking The power button is no longer assigned?
I am guessing
JVT said:
He is talking about me
I flashed it through CWM and went to restart and now the phone is dead
No lights nothing no vibrate it simply will not turn on
flashed it with
O2X FLAIR GB v4 REVOLUTION FINAL (based on LG v20L)
for optimus
Click to expand...
Click to collapse
Could you give me a link?
Sent from my Transformer Prime TF201 using xda premium
JVT said:
He is talking about me
I flashed it through CWM and went to restart and now the phone is dead
No lights nothing no vibrate it simply will not turn on
flashed it with
O2X FLAIR GB v4 REVOLUTION FINAL (based on LG v20L)
for optimus
Click to expand...
Click to collapse
So the ROM flashed but when you went to reboot, that's when the phone froze up?
Are you 100% sure there was enough battery life when you flashed it? You really might have hard-bricked it. I figured the ROM would just simply fail installing because that's usually what happens.
spc_hicks09 said:
So the ROM flashed but when you went to reboot, that's when the phone froze up?
Are you 100% sure there was enough battery life when you flashed it? You really might have hard-bricked it. I figured the ROM would just simply fail installing because that's usually what happens.
Click to expand...
Click to collapse
I think it might be something with the splash screen.
Sent from my Transformer Prime TF201 using xda premium
The battery was low, but it went to reboot after the install and never restarted
JVT said:
The battery was low, but it went to reboot after the install and never restarted
Click to expand...
Click to collapse
The phone shouldn't automatically reboot after an install...
Sent from my Transformer Prime TF201 using xda premium
JVT said:
The battery was low, but it went to reboot after the install and never restarted
Click to expand...
Click to collapse
Were you doing this through ROM Manager or just flashing through Recovery?
Sent from my GingerFusion Revo using Tapatalk.
http://forum.xda-developers.com/showthread.php?p=20747850&posted=1#post20747850
I have to wait 5 mins between posts
I selected the reboot phone option.
I had successfully flashed gingervolt but thought this was another option.
---------- Post added at 09:14 PM ---------- Previous post was at 09:05 PM ----------
through recovery, Did the necessasary data wipes and then flashed from zip
JVT said:
http://forum.xda-developers.com/showthread.php?p=20747850&posted=1#post20747850
I have to wait 5 mins between posts
I selected the reboot phone option.
I had successfully flashed gingervolt but thought this was another option.
Click to expand...
Click to collapse
I honestly don't know what to say. If the phone is completely unresponsive then it very well could be a hard-brick. The only thing you can do then is call Verizon, tell them that you had a software update for your Revolution and the phone shut off in the middle of the update and now will not come on at all. They'll probably send you a free one (hopefully). That's really about the only thing I can think of. Have you tried just plugging it in to see if it charges at all? Plug it in and see if either the screen will come on or you at least get the LED light to come on. If not then do what I said a second ago and call Verizon.
Yeah I get nothing, they are going to send me a new one. Thanks anyway.
JVT said:
Yeah I get nothing, they are going to send me a new one. Thanks anyway.
Click to expand...
Click to collapse
Ok cool, sorry I couldn't help more man!
I was more curious why it happened more than anything, Being phoneless for 2 days sucks too though. I feel naked
JVT said:
I was more curious why it happened more than anything, Being phoneless for 2 days sucks too though. I feel naked
Click to expand...
Click to collapse
Yeah I've been there, it sucks really bad. The reason why it happened other than the fact that the ROM is for a different phone, is because the ROM has a boot.img that is not compatible with the Revolution. So once you changed the boot.img the phone was no longer able to boot up. At least that's what I think about it.
Sent from my GingerFusion Revo using Tapatalk.
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.
So i have installed android 4.2.2 slimrom
Baseband version N7000XXLPT
Kernel version 3.0.31-CM-ga034655
Slim version Slim-4.2.2.build.6-OFFICIAL
Build number JDQ39E
The problem is from what i can see, my computer is not finding my phone, but after a few apks i saw that my phone doesn't recognise my computer too, strange thing, anyway i have another problem, this android is charging with like 3%/hour, i do not have any backups from an stock rom, so because of the connection error i am unable to flash a stock with odin.
P.S If somebody have a stock backup made for his/her phone with a stock (4.0.3/4.0.4/4.1.2) and want to make a good thing and share, i would be greatfull, just upload it somewhere and i will download it, after i will install the update i will do a factory reset so no aware about
http://forum.xda-developers.com/showthread.php?t=1424997
joey_oggie said:
http://forum.xda-developers.com/showthread.php?t=1424997
Click to expand...
Click to collapse
Thank you man but this is not helping me cause I have to use Odin to flash them
Update! Tried to downgrade to 4.2.1 using CWM no results same problems,
Try to flash android 4.1.2 using CWM, no results same problem, what i still can do?
Sorry, I might have missed the part about Odin not recognising it.. Anyway, are you sure you installed the correct Samsung drivers? Try another PC and install the drivers and give Odin another shot. Also, try using another USB cable, it might help.
Sent from my GT-N7000 using xda app-developers app
joey_oggie said:
Sorry, I might have missed the part about Odin not recognising it.. Anyway, are you sure you installed the correct Samsung drivers? Try another PC and install the drivers and give Odin another shot. Also, try using another USB cable, it might help.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Man I tried on 2 computers with Samsung drivers installed + kies , 3 different cables , no result even in download mode.
Well, I can't think of anything but a defective USB port.. I assume you tried cleaning it as well?
Sent from my GT-N7000 using xda app-developers app
joey_oggie said:
Well, I can't think of anything but a defective USB port.. I assume you tried cleaning it as well?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
3 times, IFK what else to do,really, but I am concern because it may be a problem with the hardware cause I have a problem too with charging and I can't send it to warrant cause it has a costume rom
oliviancool said:
3 times, IFK what else to do,really, but I am concern because it may be a problem with the hardware cause I have a problem too with charging and I can't send it to warrant cause it has a costume rom
Click to expand...
Click to collapse
try charging battery outside of phone (like external charger). use mobile odin to flash stock rom.
edit: or just borrow if someone you know has same phone.
Used to have problem of odin not recognizing my phone. Then I switched to xp from windows 7 with same driver installed, no issue.
So could be driver issue if you're using windows 7.
oliviancool said:
3 times, IFK what else to do,really, but I am concern because it may be a problem with the hardware cause I have a problem too with charging and I can't send it to warrant cause it has a costume rom
Click to expand...
Click to collapse
treacherous_hawk said:
try charging battery outside of phone (like external charger). use mobile odin to flash stock rom.
edit: or just borrow if someone you know has same phone.
Click to expand...
Click to collapse
^that. Since you're already rooted, get Mobile Odin from the Play Store and try and flash the stock ROM with it.
OK everything went smooth I was able to flash a new and a stock ROM but my battery problem is still there in 4 hours turned off I have 32% battery, idk what to say about this
oliviancool said:
OK everything went smooth I was able to flash a new and a stock ROM but my battery problem is still there in 4 hours turned off I have 32% battery, idk what to say about this
Click to expand...
Click to collapse
Well, since you have a stock ROM now, I guess you could try and take the phone to the retailer (or service center) and have them check the USB port.. It could be a battery problem too. My phone was doing weird stuff when I was using an unbranded battery (it didn't want to recharge and it kept making connected/disconnected sound even though I was nowhere near the charger).
Sent from my GT-N7000 using xda app-developers app
Slim-n7000-4.3.build.1 battery charging problems
oliviancool said:
So i have installed android 4.2.2 slimrom
Baseband version N7000XXLPT
Kernel version 3.0.31-CM-ga034655
Slim version Slim-4.2.2.build.6-OFFICIAL
Build number JDQ39E
The problem is from what i can see, my computer is not finding my phone, but after a few apks i saw that my phone doesn't recognise my computer too, strange thing, anyway i have another problem, this android is charging with like 3%/hour, i do not have any backups from an stock rom, so because of the connection error i am unable to flash a stock with odin.
P.S If somebody have a stock backup made for his/her phone with a stock (4.0.3/4.0.4/4.1.2) and want to make a good thing and share, i would be greatfull, just upload it somewhere and i will download it, after i will install the update i will do a factory reset so no aware about
Click to expand...
Click to collapse
I had problems installing the Slim-n7000-4.3.build.1-OFFICIAL-874.
Installed from the 4.1.2 stock.
Once connected, the N7000 did not carry the battery.
Tested various cables and chargers, even doing full wipe again the problem continued.
Had tested the Slim-n7000-4.3.beta.4-WEEKLY-424 and this problem did not occur.
The only solution was charging the N7000 with it off and go back to stock rom.
I had no problems with the Slim-n7000-4.2.2.build.7-OFFICIAL, Slim-n7000-4.2.2.build.8-OFFICIAL.
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
I have been experiencing this for a while: after rebooting my phone, the exact momment it finishes booting up, it starts shutting down, no matter what custom ROM I have flashed, so it makes me believe it's not ROM related, but related to the bootloader or something like that. after banging my head against the wall for so long I couldn't find any solution, so I'd like to know what's your opinion about it.
Edit: forgot to mention I've tried all the routine methods, cleaning dalvik/cache, wiping system, data and even internal storage without any success, that's why I believe it is bootloader related, but I'm no expert so... If this issue has been addressed here please show me where as I've become empty handed
Sent from my LG-P880 using XDA Premium HD app
tristaoeast said:
I have been experiencing this for a while: after rebooting my phone, the exact momment it finishes booting up, it starts shutting down, no matter what custom ROM I have flashed, so it makes me believe it's not ROM related, but related to the bootloader or something like that. after banging my head against the wall for so long I couldn't find any solution, so I'd like to know what's your opinion about it.
Edit: forgot to mention I've tried all the routine methods, cleaning dalvik/cache, wiping system, data and even internal storage without any success, that's why I believe it is bootloader related, but I'm no expert so... If this issue has been addressed here please show me where as I've become empty handed
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
i have seen this happening only when the custom kernel is not compatible with the rom installed. the bootloader has nothing to do. we just unlock it to install a different recovery image that help us install any kernel and any rom
I'm using the CM10.1.3 right now with its stock kernel and it still happens... It annoys me so freaking much
Sent from my LG-P880 using XDA Premium HD app
tristaoeast said:
I'm using the CM10.1.3 right now with its stock kernel and it still happens... It annoys me so freaking much
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
Maybe you should reflash the .kdz file to be completely stock. If this problem still occurs, it's definitely nor ROM related.
Dexxon said:
Maybe you should reflash the .kdz file to be completely stock. If this problem still occurs, it's definitely nor ROM related.
Click to expand...
Click to collapse
....... the .kdz is used to flash stock LG's rom. when he sais stock kernel with cm 10.1.3 , he means , the cyanogenmod 10.1.3 as it is.
kessaras said:
....... the .kdz is used to flash stock LG's rom. when he sais stock kernel with cm 10.1.3 , he means , the cyanogenmod 10.1.3 as it is.
Click to expand...
Click to collapse
exactly.. It is annoying me for real not being able to find what's causing this... Not being able to properly reboot is a real pain in the a**