Related
ok the phone is not bricked an i know there is only one way to brick a hero blah blah blah. but i have psfmod recovery flashed to my phone and i was trying to do the firats mtd partition thing. so i did everything it said and when it came time to do adb shell,reboot recovery it wouldnt work. so after about 5 minutes i realized that the computer wasnt recognizing my phone. i guess cause of the psfmod recovery. and i had already wiped everything. so i wiped everything again and flash zenaraia rom back on. but after rebooting it just stays at the white HTC screen. waited for an hour. i tried wiping and reflashing like 20 times. and i cant mount the sdcard to put another rom on there since the computer wont recognize my phone. anybody following me? lol any suggestions?
It seems like you might need to RUU... have you tried doing that?
cp0020 said:
ok the phone is not bricked an i know there is only one way to brick a hero blah blah blah.
Click to expand...
Click to collapse
Haha I came here just to possibly rip on the OP when I read the title but saw you already mentioned it :/ So you put it in your thread title anyway?
As the guy said before, try running the RUU - should be able to be done in the bootloader.
OR if you can boot up into a rom (wasn't too sure judging by what I read) just get a Dropbox, throw a rom.zip on it, get the app for the phone, sync and bam. New rom.zip on your phone to try.
If neither one can be done, you need to find another phone, camera, sdmount...something so you can add files to it. Even if its just a HERCIMG.zip to update via the bootloader (look up s-off if you don't know what that's about)
Good luck
thanks for your help guys. i'll try the RUU but i dont think it will work since my computer wont recognize my phone while in bootloader. im pretty sure it's just the psfmod recovery that f'd everything up. and yeah i cant boot into a rom. im hoping that somehow my rom.zip just got messed up somehow.
ok yeah RUU didnt work. my only other option is to find a laptop or something
Try getting a live Fedora or Ubuntu linux cd (or any flavor for that matter) and booting it up.
what would that do? i went back to the psfreedom thread and i saw that adb and usb mass storage does not work with that recovery. i should have read better lol
Same thing happenned to my evo..i kept tryna flash the wrong kernel wit nym rom..all i did wuss flashed the rom without da kernel and walla...it started workin again..thnx god..idk if dis would help but it worked for me..
Sent from my PC36100 using XDA App
ok i got it to work. i was talking to nfinitfx45 on google talk and he said to boot up in fastboot and then plug the phone into the computer and then i can run the RUU and it worked like a charm now i just gotta re root :/
cp0020 said:
ok i got it to work. i was talking to nfinitfx45 on google talk and he said to boot up in fastboot and then plug the phone into the computer and then i can run the RUU and it worked like a charm now i just gotta re root :/
Click to expand...
Click to collapse
yay !!! im just quoting this because this bears repeating...
1 - if recovery is not working, go into fastboot to get pc to recognize phone...
2 - if roms (recovery or whatnot) are not working, reflash to RUU to start fresh...
(and adding)
3 - once youve started fresh, then flash a working-recovery and go back to your latest [nandroid] backup...
(you always have a good backup to use, right ?) h.
I think all you had to do was flash a different recovery from terminal if you were able to boot up the reason y I didn't use that mod was the fact you can't use adb wen u flash that recovery in that post I think the op posted the link to the old recovery that allowed you to use adb good luck
Root-Hack-Mod-Always™
that was the problem. i couldnt boot to a rom cause i had erased all data and my rom.zip had got corrupted somehow. and with that recovery you couldnt do adb or usb mass storage. so i started freaking out lol. thanks again nfinite
So I'm having a similar problem. I can use ADB to reboot my phone, so I know the computer is talking to the phone but it wont get past the HTC screen. I was trying the firerat mod and made it to the reboot as well but it never came back up. If I reboot to recovery its a white screen with the android on the skate board but the only option is to clear user data and then reboot again which goes back to the HTC screen. I tried the RUU but it wont install because it says my phone doesnt have enough battery (it's been charging on and off for the better part of 24 hours now.) Any assistance or advice would be greatly appreciated.
first, can you use usb mass storage? if so the you need to put a rom on your sdcard and flash it and see if that fixed it. and if you want to RUU. then pull the battery and put it back. then hold volume up and power at the same time. then hit the button it says to to go into fastboot. you should already be in fastboot though. and then while in fastboot plug the phone into the pc and you may have to install drivers. and then you can run the RUU.
I'm not exactly sure what happened but i got it working. I ran "adb reboot-bootloader" from the menu that brought up i was able to get back to the clockwork recovery, restore my nandroid and finish the mod. all appears to have worked beautifully except that last night my battery went completely dead over night (for the first time) although i'm doubting that that has anything to do with any of this
So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.
same question here
Did anyone figure out how to restore Verizon tab?
mkay o i'm kind of new to android and tonight i wet my pants cause i thoughy i bricked the optimus. I wanted to install CM7 but something went horribly wrong.
After I rooted and installed ROM manager I copied CM7 to my SD and installed. After it was done the CM7 boot screen kept looping. No way the phone was doing anything more than that.
The only other thing it would do was to sho a 'waiting for update' screen. After a lot of searching I mangaged to get stock ROM back by using smartflash, praise be...
Now that I know I can rescue the phone I'd like to know what whent wrong..any clues? Did I use the wrong build of CM7? I just used the latest of the 4th of july.
I want to try again but maybe some insight would be helpful, thanks...
Did you remember to tick the wipe data box in ROM Manager?
Well it would not install from rom
Manager (installation canceled by itself and ennded up with fresh install of LG rom...) so after that i did it from recovery. cant remember if i got the option to wjpe in there...
So when i installed from ROM manager i did xheck the wipe boxes. Then started installing from SD. The installation stopped, i have seen some sort of warning exclamation but i could not read what was wrong the message disappeared too fast. I think the 'wipe' was sucssesful though because all my apps and settings for stock LG firmaware were back to factory.
Ah ha.
ROM Manager and the stock ROM don't get on too well. Boot to recovery, wipe and install from there.
Assume you are using CWM recovery? It has the option to wipe on there if you look carefully so you can wipe it manually before flashing.
I tried again and it seems GB is now running cause I can see the battery icon on a different angle but it keeps givin me LG installation error messages after boot which i may ' forrxe close' but basicly nothing happens. Did i forget to wipe somerhing or forget to do smth else?
What recovery are you using? If it's 4.0.0.5, you might want to update to the newest 4.0.0.5, as the original one I built had some problems formatting.
The error messagel all seem to refer to LG apps or services. Device wont go beyond these messages.
I know, if it's what I'm thinking, they will have been left behind during the CM install, which shouldn't happen.
Ok so what do you think i should do? thanks for the snappy replies rusty.
Fyi, behind the error messages i can see a black background. The top bar with battery indicator is present, it charging. Signal indicator is there but has no signal.
Change recovery and flash again, either to 3.2.0.0 or the newest 4.0.0.5
this is what it looks like now. When i switch off and do volume down+ power its says waiting for S/W upgrade.
First i need to re-install syock again i guess? Wont do much else..
If you're getting software upgrade, you're letting go of power to early, keep em both held.
Edit: Or use 'adb reboot recovery'
hmkay im in recovery now thanks for that. It says 3.0.2.8
Signarure check enabled
Signature check disabled
Script asserts eneabled
Im not quite sure what you want me to do now. Thanks for your patience
Oh, 3.0.2.8 shouldn't have had any problems then, annoying.
Still, pik the wipe data/cache option, then install CM7
Im there thanks so much Rusty.
Hello guys!
I'm having some problem with my OB. This happened after one reboot while using TeslaLED's torch. My phone rebooted then the LG logo showed up. Then to my surprise, the nova8's boot animation didn't showed up. At first I thought it got bricked, but I waited for it to finish boot up. Then when I touched the screen, I felt a haptic feedback, meaning the phone ain't bricked.
Then I tried pulling battery and rebooting again. Same black screen with flashing buttons. Then after 5 tries of pulling battery and rebooting, it continued to boot to bootanimation and screen didn't turn black. But everything was wiped out. So, downloaded all my apps again.
And everytime I reboot my phone I get this black screen.
After a month of pulling and rebooting, I decided to go back to stock, to see if it was a problem with Nova8 ROM. And I hoped the issue will be gone after flashing back to stock.
But now, I'm on stock ROM. LG logo shows up, then black screen, then I waited and heard LG's stock bootanimation. Meaning it ain't bricked.
Can you help me? Is there a way for me to fix this? Any form of help will be much appreciated. Could it be hardware problem?
hi, I have the same problem that you've tried everything and I can not make my optimus black out the screen of lg. I've watched several people with the same problem.
Well, I can't say that it's good that you have the same problem. But now I'm sure that it has to be some problem with Nova8. And that it did something terrible with our phones.
I've tried flashing Cm7 rom and this problem doesn't occur. It could be a problem with Froyo Roms?
We need help (
factory reset !
how to factory reset the phone's screen is just lg?
http://forum.xda-developers.com/showthread.php?t=1275315
If you havent tried this yet, try this here: http://forum.xda-developers.com/showthread.php?t=1396091
should always work. If not, either your phone is bricked and needs to be returned, or your PC doesnt work properly, or you missed anything in the thread, so follow it CAREFULLY, or you simply need more knowledge about your phone... so keep on reading
OR try this one, since it really is a step by step guide
http://forum.xda-developers.com/showthread.php?t=1396091 I do not understand, I'm Brazilian.
it is not bricked. I'm using my phone as I speak. It's just that its very hard to boot normally if I reboot. Because There's an 90% chance of getting into black screen than to continue boot up to bootanimation
yes my Ob also did not able to restart it if it was on the screen of LG, but now he does not care anymore.
Did you have CWM installed before? If yes get SuperoneClick and a custom .zip rom (e.g. redy's). And put .zip Rom to ur sd card.
1. Extract Superoneclick to C:
2. rename the folder to SO
3. then open Command Prompt by typing cmd into search/run or push windows + r and type it there
4. when command prompt is open type "cd so" without " "
5. type "cd adb"
6. type "adb reboot recovery"
7. wipe data, cache, in advanced wipe dalvic
8. go back
9. choose install zip from sd card and install the zip you just downloaded and everything should be fine, but ALL your data will be lost!
should I do the command prompt while the phone is connected?
Yes, otherwise, how should the phone get what the PC wants it to do? and also enable debugging mode if possible.
Solved it!
It seems that my phone has issues with Froyo based firmwares. When I flashed Zeus1 and CM7 my phone didn't showed the same problems I had.
What I did:
1.Used KDZ updater to flash V10A.(I came from Nova8)
2.When it's finally up and running, install Gingerbreak to attain root.
3.Download CWM recovery from ROM Manager.
4.Download any Gingerbread based ROM.(CM7,Redy's repackaged, Zeus1)
5.Put it in SD card.
6.Reboot to recovery
7.Wipe data/Factory Reset
8.Wipe cache partition
9.In Advance, wipe Dalvik Cache
10. Go back, Install zip from SD card.(Look for your ROM)
11.Wait for it to finish
12.Reboot.
13.Enjoy!!!
Why V10a? Because root can be attained using Gingerbreak. I tried Superoneclick , but got no luck.
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom