Need help! - Thunderbolt Q&A, Help & Troubleshooting

I have an thunderbolt that I was running bamf 3.0 (I think), I havent used it for a while so I gave it to a buddy. He took it and started playing with the bamf toolkit changing the font, ever since then it gets stuck at the HTC screen. I can still boot into recovery and everything even still flash roms through CWM, but no matter what it sticks at the white HTC screen, can the excellent XDA peeps help me through this?

Even after you wipe the system, cache, and dalvik you still get stuck? Try updating your clockwork, or switch to twrp 2.0 and see what you can accomplish. http://teamw.in/project/twrp2

Did u try clearing data/cache each 3 times then restore a nandroid back up?
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
If that does not help you need to do this http://forum.xda-developers.com/showthread.php?t=1310014

Related

Stuck on boot.

Hi all. My Droid x2 is stuck on the boot screen with the Motorola logo and won't go past that. I attempted to flash Speedy v6, and this caused this. I also tried fastbooting by going into Android Recovery and wiping cache/format data, and it still does not work. Please help me with this situation. Thanks
Try sbf if you can't get back into bootstrap recovery.
Sent from my DROID X2 using Tapatalk
itskevin94 said:
Hi all. My Droid x2 is stuck on the boot screen with the Motorola logo and won't go past that. I attempted to flash Speedy v6, and this caused this. I also tried fastbooting by going into Android Recovery and wiping cache/format data, and it still does not work. Please help me with this situation. Thanks
Click to expand...
Click to collapse
If you made a nandroid backup before you broke it, turn phone off and plug it in, hope it boots into bootstrap recovery, then restore backup. If no backup or doesn't boot into bootstrap, you will have to sbf
Sent from my DROID X2 using XDA App
Ihad the same problem but turned phone back on with power and down volume button on at same time until you get into the point where you can get into your android recovery. Remember to hit both volume buttons at same time when you get to the android and triangle. Wipe data factory reset and re boot and it worked for me. If not then you will have to sbf again. I was ready to sbf but this worked instead and saved some time.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
EvilTim said:
If you made a nandroid backup before you broke it, turn phone off and plug it in, hope it boots into bootstrap recovery, then restore backup. If no backup or doesn't boot into bootstrap, you will have to sbf
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
If you have a backup you can get to it with the stock recovery.
Travisdroidx2 said:
Ihad the same problem but turned phone back on with power and down volume button on at same time until you get into the point where you can get into your android recovery. Remember to hit both volume buttons at same time when you get to the android and triangle. Wipe data factory reset and re boot and it worked for me. If not then you will have to sbf again. I was ready to sbf but this worked instead and saved some time.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
If you have a backup you can get to it with the stock recovery.
Click to expand...
Click to collapse
How do u get to a backup using stock recovery?
Travisdroidx2 said:
If you have a backup you can get to it with the stock recovery.
Click to expand...
Click to collapse
Really now?
That would be nice.
Sorry must be a noob mistake. I thought while I was in there to clear data/factory thought I also seen a spot to load zip from SD. Guess I was wrong you all know more than I do I have only been at it now for a couple of months
Pretty sure there is an option to apply update zip but my backups aren't named update and they aren't zips so that poses a problem __
I see I never tried I just figure that yo ucould get to it like you do with recovery app. I did get bootloop when flashing to 2.3.4 and thought I was going to have to sbf again. However starting up in backup recovery and clearing data and factory reset again fixed the issue. Eclipse went smooth and is looking good! Just concerned on my battery life as I need a strong battery for work.
Yes u will have to clear data/cache from stock almost every time u sbf. I know I have.
i sbf back to 2.3.3 and reflashed the script and worked perfectly. thanks for all your help!

[Solved] Vibrant flashing problem

Here is what happened. Flashed voodoo lag fix, Didnt notice any difference after 3-4 days. Then tried to flash back to stock(eclare). Here is where im stuck at, it wouldnt boot up using the stock eclare, So I tried one of the tuts here that said to use eugene rom. I used the pit 52 file+ eugene rom. Flashed those using oden, phone boots up fine, but I now have the not enough space problem when attempting to dl apps from the app store. When I reboot my phone after I have tried to use the market, the market app disappears. Ive tried using other roms and nothing works.
Every time I flash a rom I get "data failed to whipe" on first reboot.
Find a ROM you want and in recovery wipe cache, dalvik cache, wipe data, format system in mounts and storage then flash the ROM and see if that clears things up.
sent from the depths of helly bean
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
BTW, what ROM were you running before?
sent from the depths of helly bean
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
Just saw this in another thread, it might help you.
Google eugenes froyo that does not brick, read the op carefully, because after you odin the tar file, you will have an error message, thats ok, odin eclair and you should pass.
Read it 10 times, you'll reboot in cwm with an error message, ok, reboot, download, eclair.
sent from the depths of helly bean
samsgun357 said:
Find a ROM you want and in recovery wipe cache, dalvik cache, wipe data, format system in mounts and storage then flash the ROM and see if that clears things up.
sent from the depths of helly bean
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
BTW, what ROM were you running before?
sent from the depths of helly bean
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
Just saw this in another thread, it might help you.
The only rom that will boot up is
Google eugenes froyo that does not brick, read the op carefully, because after you odin the tar file, you will have an error message, thats ok, odin eclair and you should pass.
Read it 10 times, you'll reboot in cwm with an error message, ok, reboot, download, eclair.
sent from the depths of helly bean
Click to expand...
Click to collapse
The only rom that will boot is "eugenes froyo that does not brick". All others boot to the vibrant/samsung screen then to black screen where only the bottom 4 buttons light up, but nothing happens.
I was on the stock eclare rom.
Its also saying there isnt a partition for app2SD. Any way to fix this?
Have you tried this tar? I use it instead of flashing to eclair as most of eugenes roms repartition...XDA search for a link to this... Eugene_2E_JK2_froyo.tar.
Sugartibbs said:
Have you tried this tar? I use it instead of flashing to eclair as most of eugenes roms repartition...XDA search for a link to this... Eugene_2E_JK2_froyo.tar.
Click to expand...
Click to collapse
Thats the one Ive been using, if there is a tut to fix the vibrant on here, Ive already tried it.
I dont think thats the one, the eugene I use is Eugene373_samsungS_froyo_pda.zip, and it wont reboot, it will take you to recovery with an error message. you pull the battery, enter download, then odin eclair. Ive used it for corrupted flashes that result in failed odin rewrites to stock. Search that pda and it will take to a 4share download.
Sugartibbs said:
I dont think thats the one, the eugene I use is Eugene373_samsungS_froyo_pda.zip, and it wont reboot, it will take you to recovery with an error message. you pull the battery, enter download, then odin eclair. Ive used it for corrupted flashes that result in failed odin rewrites to stock. Search that pda and it will take to a 4share download.
Click to expand...
Click to collapse
That worked perfectly. Thx

[Q] Stock Rom wont stick. Why?

Just a simple question reallly but the answer may not be because it really dont make sense to me.
Why wont the stock rom for electrify boot up on my phone? it just sits there on the red moto logo and kills the battery.
I have 4 of these devices. 2 unlocked and 2 locked. I have flashed many roms. Like many! I have not had problem flashing these custom roms
but i have tried to flash on an unlocked bootloader a couple of the diferent deodexed versions via both recovery and fastboot and they dont boot.
I have redownloaded all of the files several times. Wiped this phone with every option i can find so far. Tried different recoveries on the phone. I feel like i have tried all i have in my knockledge base but this seems just odd to me. Could be im trying to hard and need to just walk away but i really wont to get this to take. I DONT want to sbf back and lock the bootloader. I can flash th3bills cm10 and it works great. Wipe the phone and flash either of these 1FF-sunfire-user-2%2e3%2e5-4%2e5%2e1A_SUN_USC_19%2e0-19-release-keys-signed-USC-US.zip
1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.zip
and it just hangs.
So heres another question....can i not go back to stock gingerbread after going to jellybean?
Just kinda baffled right now and would like a second opinion here about what i must be missing or am doing wrong.
thanks in advanced for any help
After you flash did you do a factory reset in recovery before rebooting? Only thing I can think of.
Sent from my Photon 4G using Tapatalk 2
I have several times. Seriously dont think that these files can be corrupt after ruling that out by downloading them 3 times. I wait for the transfer to complete in ever way i transfer the files. Im seriously stumped.
New question.....in there a certain way to format for stock gingerbread or does it matter....re ext3 ext4 or whatever is out there.
When flashing back to stock, it's system data and cache. If after that it's not working, it's probably a bad download. The kernel would be the culprit if your flashing between android versions if I'm not mistaken. Also which stock ROM did you download? Some have had problems
Sent from my MB855 using xda premium
---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------
A good full wipe would rule out the formatting I think
Sent from my MB855 using xda premium

Stuck on "Samsung Galaxy S4" Screen, Kinda

OK, I think it is "sort of fixed" but, here goes...
I booted into recovery to do a fresh wipe/install of CleanRom 1.3 (odexed version).
Wife got me side tracked and after wiping dalvik and then system, I accidently rebooted before flashing the ROM.
Phone was stuck at the "Samsung Galaxy S4" screen.
Tried booting into Recovery (twrp 2.5.0.2) but, apparently I wasn't holding the Volume Up button long enough and the phone would just reboot to the normal "Samsung Galaxy S4" screen again and hang.
So I went into Download mode, and tried re-rooting the phone using the instructions here, Odin said "PASS" but, after waiting about 10 minutes, the phone still hung at the same screen.
I was then able to successfully boot into recovery, reflashed the Scotts Cleanrom 1.3 odexed (found here) and everything seems to be fine.
Question is, I never was able to flash, using Odin, the stock kernel again but, in the "about phone" menu, it shoes me as being on the 3.4.0-562219 kernel version.
Is this OK?
How would I do a fresh wipe (I'm talking EVERY MO****IN THING) and start again from stock, everything stock except SD card?
http://www.sxtpdevelopers.com/showthread.php?t=237
but you might wanna try http://forum.xda-developers.com/showthread.php?t=2301259&highlight=factory+reset first if you have any data you want
---------- Post added at 08:21 PM ---------- Previous post was at 08:17 PM ----------
tgumina said:
http://www.sxtpdevelopers.com/showthread.php?t=237
but you might wanna try http://forum.xda-developers.com/showthread.php?t=2301259&highlight=factory+reset first if you have any data you want
Click to expand...
Click to collapse
edit: http://forum.xda-developers.com/showthread.php?t=2289325&highlight=one+click might be better or easier. for full wipe
Thank you, the weird thing is, I am not bricked at all, once I was able to boot into recovery and reflash the rom mentioned in OP, phone is acting like normal, tried several normal reboots and all is well.
Should I do an unroot flash and start from scratch or is this one of those "if it ain't broke, don't fix it" sort of situations?

[Q] TWRP issue

Hello, I am having issues with TWRP recovery. I have been running mean rom since I got the phone when it was new. I have been thinking of trying a new rom and wanted to update TWRP. I mad a nandroid back up with TWRP, also backed up my apps with Titanium, no issues with either. Now the fun begins, I used goomanager to updated TWRP to 2.6.1 and now when i boot into recovery nothing happens, the phone gets the splash screen with the white bar on the upper right then instead of opening recovery it reboots to the phone.
I cannot get into recovery, I have tried battery disconnect, rebooting multiple times using bootloader to reset to fasctory and nothing happened. It didnt even reset factory defaults. The phone works, everything works jut cant get into recovery. any ideas?
thanks
You're saying you can boot into Android but not to recovery, right? Have you tried pushing the recovery to the phone via fastboot? If that doesn't work, sounds like you need to RUU and re-root.
Sent from my HTC EVO 4G LTE
recovery
I dont trust the goomanager app for recovery images.
http://teamw.in/project/twrp2/98
read the instructions and flash that one instead. there are instructions for multiple situations.
---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------
jimbo4822 said:
I have tried battery disconnect
That is no easy task on an evo lte
Click to expand...
Click to collapse

Categories

Resources