hey guys, i have a big problem here.
I just tried applying a theme through metamorph, and it failed. Now my phone won't boot up, and is stuck at the splash screen. When I try to get into recovery, I can't because every time it wants to update the splash screen(which i changed), and then I get the choice of either updating the splash screen or not, and then to reboot, and this just repeats.
WhaT do to??????
yoseir2 said:
hey guys, i have a big problem here.
I just tried applying a theme through metamorph, and it failed. Now my phone won't boot up, and is stuck at the splash screen. When I try to get into recovery, I can't because every time it wants to update the splash screen(which i changed), and then I get the choice of either updating the splash screen or not, and then to reboot, and this just repeats.
WhaT do to??????
Click to expand...
Click to collapse
Easy. I did this before. Pull battery and SD card. Replace battery, boot to hboot, since there's nothing to scan scroll down to recovery, while its on the splash screen replace card, once in recovery restore a backup or flash a new ROM.
Trust me I freaked out too. Its easily fixed as long as you follow my directions.
Sent from my Mikrunny'd Superphone using my Ice Cream Sammich flavored Tapatalk
thanks for the reply. I didn't do this, but I got a microsd card to sd card adapter, pulled the sd card out, plugged it into my trusty macbook air, deleted the splash screen update, and metamorph's file, and then put it back in my inc2, restored from the backup that I made, and back to normalcy.
lesson learned: ALWAYS ALWAYS ALWAYS ALWAYS backup. You'll pay for it if you don't.
Or, you can find the ROM zip that you flashed recently before you messed it up, unzip it, and find the apk you messed with. Then, follow my guide in my sig to push it to system/app.
---------- Post added at 01:06 PM ---------- Previous post was at 01:06 PM ----------
Oh, the guide you would want is #5, ADB.
yoseir2 said:
thanks for the reply. I didn't do this, but I got a microsd card to sd card adapter, pulled the sd card out, plugged it into my trusty macbook air, deleted the splash screen update, and metamorph's file, and then put it back in my inc2, restored from the backup that I made, and back to normalcy.
lesson learned: ALWAYS ALWAYS ALWAYS ALWAYS backup. You'll pay for it if you don't.
Click to expand...
Click to collapse
Good. Yeah, always make sure you delete the update after its flashed found that out when I did it.
Sent from my Mikrunny'd Superphone
Related
Apologies in advance if this makes some of the vets here really angry.
My EVO is stuck at the bootloader after I tried flashing a ROM in which an error was received. I Nand restored, as I always back up prior to flashing, and I'm still stuck at the booaloader. Any chance I can download a ROM right onto my SD card and then flash? I can get into recovery.
Find the PC36IMG thread dl it and put it on the root of your sd card then get to bootloader. Should fix you up...
Thanks guy.
How can I mount the SD card though? My comp won't recognize the device at all.
It should let you reboot to your recovery from there. What does it do when you try to select it?
I can get into my recovery no problem but getting my SD card to mount is the issue now, even after toggling USB-MS.
GhettoOthello said:
I can get into my recovery no problem but getting my SD card to mount is the issue now, even after toggling USB-MS.
Click to expand...
Click to collapse
ohh, just give it a seconds after you turn USB-MS on. Sometimes it takes its time recognizing it.
10 mins? lol
Alright guys, my apologies. Looks like my terminology is off. I'm not stuck at the bootloader, but stuck at the HTC White screen.
GhettoOthello said:
Alright guys, my apologies. Looks like my terminology is off. I'm not stuck at the bootloader, but stuck at the HTC White screen.
Click to expand...
Click to collapse
Manually Boot into recovery restore the nandroid backup and continue where you left off
Sent from my PC36100 using XDA App
GhettoOthello said:
Alright guys, my apologies. Looks like my terminology is off. I'm not stuck at the bootloader, but stuck at the HTC White screen.
Click to expand...
Click to collapse
It probably doesn't like the kernel the ROM is using, try flashing one of Netarchy's universal kernels or the Stock #17.
I'm not sure about the usb-ms thing though, ten minutes is definitely too long. You may need to use ADB while in the recovery and push the files.
Manually going into recovery and then going nand restore = at least 5 times. Even the nand didn't work, which is making me a little uneasy. However, the USB-MS has worked (needed a new cable).
I'm downloading Virus's Airborne 4.6 onto my SD card, so lets see what this does.
GhettoOthello said:
Apologies in advance if this makes some of the vets here really angry.
My EVO is stuck at the bootloader after I tried flashing a ROM in which an error was received. I Nand restored, as I always back up prior to flashing, and I'm still stuck at the booaloader. Any chance I can download a ROM right onto my SD card and then flash? I can get into recovery.
Click to expand...
Click to collapse
Did you flash the new radio?
ALRIGHT after the weirdest experience with my EVO (mainly my fault), everything is back to normal. I downloaded a newer version of Virus's Airborne rom via USB MS (needed a new cable) then flashed. After that I went back into recovery and restored the Nand that wasn't working earlier. Weird, but im back.
Sent from my Evolution using XDA App
Early this morning, I rooted my Droid Incredible using the Unrevoked 3 method. After doing so, I completely forgot to create a nandroid backup and went ahead to install a custom ROM (Cyanogen Mod). Now here's the issue. I want to get back to the Stock 2.2 sense. I tried to unroot my droid, but nothing seems to be working. Can someone please help?
You need to flash a stock rom back before unrooting.
Where can I get a stock ROM. I think I just bricked it now because it won't even boot Cyanogen Mod. It's stuck at the HTC Incredible white screen.
Do you know what type of screen you're using? Slcd or amoled ? Each method has a different way of unrooting. Just in a Google search engine type in who to unroot Droid incredible, and then the what screen it is. You can potentially brick your phone if you use the amoled method on a slcd one.
With the amolcd screen it's as simple as finding the right file, hence doing the search engine. When you get the file, all you have to do is just place it in the root of your phone, and turn off your phone and press and hold the power button and the volume button at the same time.
With slcd you have to do it different way. Assuming you haven't messed with the radio, if you did, you have to flash a 07.28 radio. But assuming you didn't touch that, you have to flash something that puts s-on. Ans then after that you have to put a file into the root of your SD card and then flash appropriately.
Now I did this multiple times, rooting and unrooting, and for some reason there's always so
Something drawing me back into rooting and flashing a new rom. There's no greater satisfaction than knowing you can do anything with your phone. But it's entirely your choice.
Oh yeah, to figure out what screen you have go to settings then about phone then hardware information and 002 is amoled and 003 is slcd. Google is your best friend after you figure out what screen you have. Good luck!
Sent from my Incredible using XDA App
You haven't officially bricked it until you can't power it on at all. Try taking out the battery and then holding the power button and volume down. If you can access the white boot screen where it gives you a choice of accessing recovery there is still plenty of hope. Don't freak out you haven't bricked your phone
Sent from my Incredible using XDA App
I can't load anything. The farthest I can go is to ClockWord Recovery, and when I try to reboot the phone, it's stuck on HTC Incredible. That being said, I can't check what screen type I have. However, before it was bricked, I did flash a file to make S- on. And, when I tried degrading my firmware, nothing happened. :/
OK first off the name of the first that you flash should start with a "p" I don't exactly remember the exact file name. Make sure you have s-on, I'm sure you do. And then put that p something file into the root of your SD card. root as in, it isn't in any folder.
Now when you flash this, you don't do it in clockwork recovery, you do it through hboot I believe. Hboot is the white screen when you hold on the power button and volume down. It should automatically read the p something file. And it'll ask you if you want to update. Say yes and then just let it install
Sent from my Incredible using XDA App
PB31IMG, I attempted to Flash it in HBOOT, but it didn't work. Now, I can't even connect my Droid to my computer.
I'm screwed.
Sorry for the double post, but I just followed some whacked-out tutorial that told me to format everything via Clockworkmod Recovery...now when I boot my phone, it goes straight to HBOOT and won't do anything...
OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App
lazysleepyboi said:
OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Can't remember exactly how to tell but know you can tell by the model #under the battery on the phone.
Sent from my ADR6300 using Tapatalk
If you could get to clockwork u should be able to flash a rom if your sd wont mount use a card reader and plug directly into your comp
Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
HTC Incredible 2.3.1
Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader
lazysleepyboi said:
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader
Click to expand...
Click to collapse
That's the exact tutorial that I followed, but it didn't work.
Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
ok can you tell me how you flashed the included file? did you put it into the root of the SD card?
For now i would get a rom on your sd so your phone will boot up and do a nand backup so you at least have a working phone when i get home ill try and help you out
Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
HTC Incredible 2.3.1
Ok if you have a card reader for you SD card load it in and open you card on your PC. You need to make sure that the sd card is in FAT32 format otherwise when you try to load the PB31IMG file it wont read it. To check this go to my computer, find the removable drive for the SD card right click and go to properties, you should see what format its in. If it's FAT format copy everything from your sdcard to a folder on your PC, go back and right click on the removable drive and format the card to FAT32. Then of course copy everything back to your card. Then try the PB31IMG file again in hboot.
I would personally just go in recovery and wipe to factory, then choose the option to install zip from card and install the rom or which ever rom you want so the phone loads again. Good luck!
For now, I'm going to flash a new rom and hopefully I can fully boot my Droid again. Afterwards, I'll try to flash that file again. BUT, the first time I did it, I put it in the root of my SD card and booted HBOOT and nothing happened.
EDIT: This ROM is going to take close to 30 minute to download , so I guess I'll be back in 30 minutes; don't leave me please.
do you have a sd card reader? if you do, pop out your sd card and make sure it's format is FAT32, nothing will happen if it isnt FAT32
Just rooted my new DINC, got into the main screen. Went into Clockwork and flashed a nandroid from a different device. Now I cant even get back into CWM. If I hold down and power I get hboot, but anything after that gives me 5 vibrations and blinking green lights. wtf?>
I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?
DroidHam said:
I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?
Click to expand...
Click to collapse
not really that i know of
best bet is to ruu back to stock and start over
EDIT: first link i sent wont help you
http://d01.megashares.com/index.php?d01=CHoQD3B
put this on your sdcard, rename to PB31IMG.ZIP
boot into hboot, when it asks to apply the update, say yes
give that a shot
for future reference, nandroids from phones are not interchangeable
I dont know how to use ADB, and that tutorial assumes you can run zips via recovery, which I cant...
Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock
DroidHam said:
Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock
Click to expand...
Click to collapse
yea sorry, use the new link and destructions instructions i posted, should get ya running
damn, that link wont start the download
Do you have a micro sd card reader that you can put into your pc or laptop? You need to get that PB31IMG on the root of your card. Then get into hboot to flash.
Sent from my ADR6300 using XDA App
Yea, I put it onto the root, applied the PB31IMG and rebooted. Same fcking problem. WTF?!?!
DroidHam,
try pulling the battery, wait around 10 minutes, put the battery in and boot the phone. Yes, it is very important to wait for that long.
Post your results if it booted or not, i had the same issue.
Also let me know if this is a refurbished phone.
ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?
Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App
DroidHam said:
Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I noticed you mentioned that while powering on you say you are holding down...down is diagnostic mode, you should be holding up to get to recovery.
After applying the ruu. Try re rooting
Sent from my ADR6300 using XDA App
How do I root if i can't get past hboot??!
Sent from my LogicPD Zoom2 using XDA App
I attempted to root a new Incredible for a friend and had the same thing happen a few days ago. I was able to create a nandroid backup via CWM recovery, and then flashed CM 6.1. CM then bootlooped when trying to boot for the first time. After this point I was unable to get into recovery. The screen would just go blank and would vibrate multiple times. At one point I did manage to succesfully get into CWM recovery without the screen going blank, but then recovery would not recognize the SD card. I restarted and was never able to get back into recovery.
I then attempted to flash a PB31IMG.ZIP from HBOOT that was supposed to restore it to factory state. At this point the phone when blank in the middle of flashing and would not do anything other than vibrate when I would attempt to power it on.
I told them the phone just inexplicably died and they exchanged it at the Verizon store. Everything went perfect with the replacement phone. I figured what happened was a one time thing, but after reading this I would definately be hesitant to root anyone elses Incredible.
Do all phones have hboot?? I don't wanna get screwed. But this was sent was Asurion.... i really need to fix this. There must be a way please!!!
Sent from my LogicPD Zoom2 using XDA App
Just got off work... do the battery pull, wait 10 min, then the start phone see what happens.
I'm not sure at what point you are with the RUU image at this point so take out your sd card just to be safe.
You are getting into the Qualcomm diagnostic mode, which is basically 5 buzzes and then the green light keeps flashing green correct?
I will be on and off for the next few hours to see your results.
DroidHam said:
ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?
Click to expand...
Click to collapse
5 vibrate = defective usb plug/phone... time for nother refurb. theres a couple posts on it, happened to me.
I don't know much.. but I'm pretty sure this thread is in the wrong section. Mods should move this to Q&A or General...
I downloaded Cyanogen Mod through Rom Manager and it restarted my phone but now all it does is bring up the white splash screen for a little while, then restarts into a black screen with white bars. I can get into hboot but none of the commands do anything they just restart to the splash and then back to the black screen.
I have been able to adb into the phone when it is in the black screen and I tried following this tread: http://forum.xda-developers.com/archive/index.php/t-808065.html aka I tried pushing a PB31IMG.zip (from here: http://www.dougpiston.com/files/Recovery/) onto the sdcard, turning it off, taking out the battery and restarting to hboot. But hboot does not find the file, and when I restart it to the black screen the file is gone.
My guess is that when it goes to the black screen it wipes my sdcard, at least I hope it doesn't wipe it sooner because I'm not sure how to work with that. Maybe I am not pushing a good PB31IMG.zip file because I don't really know the difference between them. Maybe I am not renaming it correctly, or my sdcard is not FAT32, because am not actually sure how to check if it is FAT32 but I am assuming it is because that is the standard. I don't really have any other leads, does anyone have any experience with this problem? Is there another way to restore it to factory reset?
Please don't tell me I shouldn't have been doing this because I apparently don't know what I am doing. I am not disputing that, but it is a moot point now. I don't know how people go about learning these things a safer way. Apparently I just suck at it. I am starting to freak out a little because I have been without my phone for a day and half and my husband is a bit pissed because he doesn't want to buy me a new phone and doesn't understand why I would want to hack my phone anyway. I refuse to believe just yet that I have bricked my droid. Please help.
Okay, so, my sdcard wasn't in FAT32 but I fixed that by connecting my sdcard to the computer directly and then put my PB31IMG.zip on while I was there. Now my hboot recognizes that there is a new file and asks me to update and I click yes and then restart and I click yes again.
Unfortunately it still does the same thing, white splash followed by black screen with bars, so I have eliminated one of my possible problems and now either its the wrong PB31IMG.zip file, the file inside is named wrong, or something else that I don't even know about. Does the img file need to be something specific? I do have the android-info.txt file so that isn't the problem. I am running out of ideas...
Have you tried the RUU?
semmes said:
Okay, so, my sdcard wasn't in FAT32 but I fixed that by connecting my sdcard to the computer directly and then put my PB31IMG.zip on while I was there. Now my hboot recognizes that there is a new file and asks me to update and I click yes and then restart and I click yes again.
Unfortunately it still does the same thing, white splash followed by black screen with bars, so I have eliminated one of my possible problems and now either its the wrong PB31IMG.zip file, the file inside is named wrong, or something else that I don't even know about. Does the img file need to be something specific? I do have the android-info.txt file so that isn't the problem. I am running out of ideas...
Click to expand...
Click to collapse
Well... you can get into H-boot so there's still hope...
1) Check to make sure your PB31MG.zip isn't named PB31MG.zip.zip.... but since you said the system finally read it, my guess is that isn't your problem.
2) You said nothing about recovery, can you get into it at all? Well... nevermind... you said everything would just reboot your device.
... When you goto H-boot... can you read off the stats?
More specifically...
S-On or S-off?
Radio number...
H-boot?
I'm not 100% sure, but I'm guessing you WERE already rooted when you attempted to flash a ROM... but attempt a re-root with UnRevoked3... report back?
Thanks so much for replying. I have not had computer access so I am finally able to work on this some more.
I have now been able to get it into the recovery screen from the PB31IMG.zip file. I feel pretty stupid, the reason why it had not worked was that I took the other files off my sdcard when I put the flash PB31IMG.zip file on it. (face-palm) Anyway, now it gives me the option to wipe and factory reset but when I do that and restart I still get the same recovery screen. I tried a couple different PB31IMG.zip files but they are all giving me the same result. I do have adb access still and I tried rebooting it from there but it is the same. I feel like this is progress maybe (hopefully)...
As for the Stats:
S-off
h-boot-0.92.0000
radio-2.15.00.07.28
I know what s-off means, but do the other numbers mean anything to you?
I tried to send it through Unrevoked3 but it gives me the 'Device "/sbin/sh:getprop:not found" is not supported at this time.' error. I am going to see about RUU...
sounds kinda like a non slcd recovery on an slcd dinc.
I had the same problem rooting a friends phone.
Here's how I fixed it.
After trying to flash a Rom through ROM manager, it went to reboot into recovery to finish the job. The thing is, it didn't.
It wen't into a Black screen wioth two white bars. One on each side of the screen., So far, it hasn't looked like it had done anything. So I pulled battery and rebooted. Everything was fine. I went to ROM Manager and instead of installing through the app, I rebooted into recovery.
Black screen and white bars, AGAIN. So I figured I just needed to re-flash Clockwork.
I pulled his battery, and restarted. I flashed Clockwork, and booted into recovery.
IT WORKED!!! No problems since.
RUU worked! I have a fixed phone. I followed this:
www .droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible. html
in the hboot screen and it is back to factory reset and much happier. Thanks.
[They are not letting me post links so you will have to take out the spaces next to www and html.]
i have absolutely gone thru every post about this and couldnt find an answer
this is what happened
i was messing with "rom toolbox" app and installed a boot animation which kept going in a loop, i waited like an hour and got tired so i booted in hboot menu and and just started wiping every thing "format boot" wiped everything "data" "cache" then i read somewhere on xda to install PB31IMG.zip from sd card and i waited pressed reboot and now it wont turn on. other thread/posts talk about unrooting it but how can i do that when i cant get into the hboot/recovery menu. please point me in the right direction if this is fixed already
i have and htc incredible 2.2 rooted s-off led light turns on and and the buttons turn on, sometimes it vibrates 1 or 5 times
please help i just want my phone back, im tired of using my blackberry
http://forum.xda-developers.com/showthread.php?t=1110865
try that and get back to us
Though the 5 Vibrate never happened to me, I hope this can be of some assistance http://forum.xda-developers.com/showthread.php?t=1110865
actually ive already read it and well i cant seem to use it because it requires my phone to turn on. and on the link one of the process is to flash that PB31IMG.zip file which i have already done. Now im trying to do that again but by loading recovery using adb but im stuck there any help
Just to make sure, the battery has a charge right? Have you tried to do everything with the phone plugged in? Also, try pulling the battery just in case it needs a hard reset or something, put it back in, then hold down the volume - and the power button and see if you can get into hboot.
That's what I would do.
yeah when i connect to the wall charger the led light turns on and when i connect to the computer it shows the both removable disk (internal memory & sd card) but i cant access them cause i would still have to mount it as a disk drive
Just a thought, can you get another SD Card, load a PB31IMG.zip on it, make sure it's FAT32 (use a card reader or something) and reboot?
increibleADR619 said:
yeah when i connect to the wall charger the led light turns on and when i connect to the computer it shows the both removable disk (internal memory & sd card) but i cant access them cause i would still have to mount it as a disk drive
Click to expand...
Click to collapse
Wait, when you plug it into the computer - the computer shows it as a disk drive? Doesn't that mean that the phone is actually on?
Hold up...
First: The PB31IMG.zip file would have been used for a splash screen, not a boot animation. Correct? Second: That is just a generic file name so that the bootloader will read the file, did you know what was actually in that file? I ask because you could have had something like a radio trying to update under the PB31IMG.zip file, and as far as I understand it that's a pretty good way to brick a phone with the quickness
You are not bricked. You most likely installed an old stock image for 2.1 that does not contain drivers for your SLCD screen. Easiest way to fix this is to download the newest RUU and use that utility. Should have you back up and running in no time. If that doesn't work, you can do it through the PB31IMG method too, but it's a pain in the ass.
I'm curious to see if that worked, update when you can please
Sent from my ADR6300 using XDA App
Ok ill try that RUU thing but im doing more research on it so i dont mess it up even more so ill post it up if i fixed it or not. THANK YOU
That was it, its fixed aaaaaaaaaahhhhhhhhhhh finally i got my phone back but this all started by me using "rom toolbox" and installing a boot animation and then it went on a boot loop(hahaah sounds funny) how would i fixed that if it happened again, not that i would try it
Awesome dude! Glad it all got worked out for you.
Don't be scuurred...
increibleADR619 said:
That was it, its fixed aaaaaaaaaahhhhhhhhhhh finally i got my phone back but this all started by me using "rom toolbox" and installing a boot animation and then it went on a boot loop(hahaah sounds funny) how would i fixed that if it happened again, not that i would try it
Click to expand...
Click to collapse
Awesome, really glad to hear that you don't just have a very expensive paper-weight. And don't fear rom toolbox, I use it for everything that it does besides the rom manager part of it and it's an great all-in-one tool. If you learned anything it's that boot animations are placed in your system files and splash screens are changed by updating in hboot with the PB31IMG.zip file name, just check and double check before you do stuff like that. You learned the hard way, but now you know. Have fun with your new(old) phone
---------- Post added at 07:21 PM ---------- Previous post was at 07:11 PM ----------
What rom are you running anyway, depending on the rom you will have a different file path to get to where your bootanimation.zip should be placed. Sense roms are usually under data/local, and cyanogenmod is under system/media. Just look until you find the file name bootanimation.zip, change that file to bootanimation.bak and leave it in the folder where you found it. Then copy/move your new boot animation to the folder where you found the boot animation that you changed from .zip to .bak, reboot and you should be good to go. The reason for leaving the old boot animation in there is a just in case sort of thing, like if something goes weird with the new boot animation you can just change the extension from .bak back to .zip. Hope that helps (or at least makes sense, ha)
I think a sense Rom. A quick question why can't I root my phone, I'm using unrevoked3 and it says "firmware to new" but I chose the one that I've always used
Sent from my ADR6300 using XDA App
increibleADR619 said:
I think a sense Rom. A quick question why can't I root my phone, I'm using unrevoked3 and it says "firmware to new" but I chose the one that I've always used
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Reboot your phone and try again. Also try downloading the latest version from unrevoked.com
Sent from my ADR6300 using XDA App
Ive done that already and also when I open my browser and go on facebook its says that I should download the app for my "thunderbolt" and that would explain why I have a newer kernel
Sent from my ADR6300 using XDA App
That's the one thing I fear about messing with my phone.
increibleADR619 said:
Ive done that already and also when I open my browser and go on facebook its says that I should download the app for my "thunderbolt" and that would explain why I have a newer kernel
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
when you go into "about phone" what is your software version?
Your kernel has nothing to do with what phone your phone is detected as by Facebook.