Related
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
I tried flashing the ics source port but forgot to flash cm7 first... It flashed fine and I followed the procedure to flash. The phone would turn on but always go straight to recovery. I figured this was because I didn't go to cm7 first, so I went to flash it but I kept getting errors. I went to flash stock, it started going so I walked away. When I came back my phone was just a white screen and odin was stuck at sbl.bin. So now I can't boot up the phone, there's no bootloaders, just a black screen whenever I try to do anything. The thing is, I can get into download mode just fine through button combos which leads me to think it's not bricked. However, odin/heimdall will not recognize it... Anyone know what to do?
EDIT: View last post by me.
mikel.canovas said:
I tried flashing the ics source port but forgot to flash cm7 first... It flashed fine and I followed the procedure to flash. The phone would turn on but always go straight to recovery. I figured this was because I didn't go to cm7 first, so I went to flash it but I kept getting errors. I went to flash stock, it started going so I walked away. When I came back my phone was just a white screen and odin was stuck at sbl.bin. So now I can't boot up the phone, there's no bootloaders, just a black screen whenever I try to do anything. The thing is, I can get into download mode just fine through button combos which leads me to think it's not bricked. However, odin/heimdall will not recognize it... Anyone know what to do?
Click to expand...
Click to collapse
Try the things listed in the "connectivity issues" post attached to my signature. If none of those works to get Odin/Heimdall to see your phone, post back.
followed it. Didn't recognize for like a minute then it showed up. I started it but it's stuck at do not turn off the target
tried again and same thing
What is it showing on the computer side (i.e. what is Odin/Heimdall saying right now)?
I'm using odin right now. But heimdal would always just say not recognized or whatever it says. Odin, when I get it to finally recognize after waiting a minute using your method, it just gets to DO NOT TURN OFF TARGET! and stalls there.
I got it to work. No clue what made it finally work
mikel.canovas said:
I got it to work. No clue what made it finally work
Click to expand...
Click to collapse
Good to hear. I know the feeling - it's like the computer/phone are just messing with you.
Damn. A similar thing happened. I had to flash to stock since button combos weren't working, and all the sudden while odin was running my screen just went black. I waited to see if anything would happen, but everything just stalled there. I've been trying to use my homemade 100k ohm resistor jig, and button combos to get into download mode but nothing seems to be doing anything. Am I bricked?
If u have no signs of life at all (no battery charging screen when u plug into a wall charger or no kind of something happening if u try to power it on) then u r hard bricked.
But there is Jtag and the Unbrickable Mod.
4-2ndtwin said:
If u have no signs of life at all (no battery charging screen when u plug into a wall charger or no kind of something happening if u try to power it on) then u r hard bricked.
But there is Jtag and the Unbrickable Mod.
Click to expand...
Click to collapse
Thanks, not what I wanted to hear. But okay.
mikel.canovas said:
Thanks, not what I wanted to hear. But okay.
Click to expand...
Click to collapse
Its cheap and keeps your phone from ever being unrecoverable again, it is better than paying the $150 for a replacement.
Sent from my I897 using xda premium
Yeah and seeing as how I'm planning on doing a bunch of development on it once I get another phone, I'm probably going to need it.
I have it and it does come in handy
Sent from my I897 using xda premium
mikel.canovas said:
Yeah and seeing as how I'm planning on doing a bunch of development on it once I get another phone, I'm probably going to need it.
Click to expand...
Click to collapse
Sometimes, if you get a lucky brick, the UnBrickable resurrector will work without any mod. This is rare, but its a shot. If you need a mod and don't have the tools, pm me.
AdamOutler said:
Sometimes, if you get a lucky brick, the UnBrickable resurrector will work without any mod. This is rare, but its a shot. If you need a mod and don't have the tools, pm me.
Click to expand...
Click to collapse
Thanks, will try that next time. Luckily AT&T exchanged it for me
mikel.canovas said:
Thanks, will try that next time. Luckily AT&T exchanged it for me
Click to expand...
Click to collapse
I had something similar happen to me,when I was running A6 or A7. I even noticed that I was losing folders that were visible on CWM. I was going to try to re-flash the ROM, but those folders were gone. What fixed it for me, was I did a Factory Reset, and al of the lost folders came back, and I was able to Odin back to stock. I was one of the more weird things I'd seen with my Cap
Ok so if the answer to this question is already on this forum I searched for a hour and if you could drop me a link that would be great. Last night I flash v10k onto my LG thrill with no hiccups. The only problem is I want to go back to V20p because it changed to a O3D and all I can get is 2g edge service. So this morning I attempted to flash V20p and everything was kosher until it said there was a connection error. "Disconnect phone remove battery..." So i figured I needed to get the phone back into download mode in order to continue. The phone isnt bricked, however, I cant seem to get it back into Download mode to try again. Ive tried everything (that I can think of). Restarted my computer wipe all my phones data... My end goal is to have either v10e or the v20p. So I'm open to any routes to this end. I've read about doing a nandroid backup but all the links are dead. I've already decided I'm going to get the Galaxy Nexus and sell this phone if I can ever get it back to stock or semi stock. This is the second time I've had this connection error the first time it was during the update to GB and that time it bricked it. At the time I thought it was a faulty data cable, however, this time I was using a gold plated gigawire and it still did it... This coupled with the ghost call issue almost costing me my job(the reason for trying to go back to froyo) My experience has been buggy to say the least. Any help at all will be greatly appreciated.
PROlific666 said:
Ok so if the answer to this question is already on this forum I searched for a hour and if you could drop me a link that would be great. Last night I flash v10k onto my LG thrill with no hiccups. The only problem is I want to go back to V20p because it changed to a O3D and all I can get is 2g edge service. So this morning I attempted to flash V20p and everything was kosher until it said there was a connection error. "Disconnect phone remove battery..." So i figured I needed to get the phone back into download mode in order to continue. The phone isnt bricked, however, I cant seem to get it back into Download mode to try again. Ive tried everything (that I can think of). Restarted my computer wipe all my phones data... My end goal is to have either v10e or the v20p. So I'm open to any routes to this end. I've read about doing a nandroid backup but all the links are dead. I've already decided I'm going to get the Galaxy Nexus and sell this phone if I can ever get it back to stock or semi stock. This is the second time I've had this connection error the first time it was during the update to GB and that time it bricked it. At the time I thought it was a faulty data cable, however, this time I was using a gold plated gigawire and it still did it... This coupled with the ghost call issue almost costing me my job(the reason for trying to go back to froyo) My experience has been buggy to say the least. Any help at all will be greatly appreciated.
Click to expand...
Click to collapse
So you want V20P or V10E?
Sent from my Samsung Galaxy S II w/ DUAL BOOT: AOKP / MIUI
I really want V10e if its possible but If not then V20p will work.
I am having similar problems when I try as well. I have tried 5 or six times but tells me something about the b2c not loaded or a connection to the internet. Every time I hit "normal web upgrade test" it throws up a pop up and wont let me proceed any further. It has worked for me twice before, I got the no connection pop up and ignored it, but its not working this time. I set everything up the same from instructions on Acidhazzard rom web site. Please help...
I had to change the port back to 80 and put the orig host file back in the ect file just to download the bc2app then change it all back it worked the first time when i flashed v10k... idk i would delete the lg drivers and everything then start from scratch if i could boot into download mode.
Sent from my LG-P920 using Tapatalk 2
I have been starting...
From scratch. I download the LG flash package and go from there. It does it every time I try. The times I got it to work, I would just hit cancel or OK on the pop up and then hit the OK button I was wanting to hit real fast before the pop up could come back up. I thought it may be a Windows 7 issue (cause I have seen people talk about it) and tried win xp yesterday. Same things happened.
Im running Xp and Im having the same exact thing happen. I got it into download mode finally idk what was going on but now I just keep getting the communications error Ive tried the whole process (each one is like 5 errors) like 3 times now. If it keeps popping up before the update even starts then your probably need to change your small server port from 80 to 9002.
fixed
Somehow after getting the com error 100 times with the flash tool I noticed it had changed my model number back to P925 (I don't know how it did this) I then decided to chance it (after I changed the host file back and changed the port back to 80 and closed the small http server) I went through the LG support tool and clicked start update. After about 20 min of uncertainty during the update and another 5 minutes of self-loathing after getting a bootloop on the at&t screen... I did a hard reset and cleared all data and wah-la... I got it back to V20p. But the flash tool wouldn't flash the v20p for me.. So if I didnt somehow get rid of the P920 model number and back to the P925 model number I don't think it would have worked the way it did.
I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.