looking for some assistance here...
in regards to upgrading to chingy's 1.4 perfect storm ROM....
i flashed the new radio and had no issue, booted up fine and everything was ok.
i put the new 1.4 on the root of the sd and rebooted into recovery, performed factory reset, cleared cache's etc. and installed the rom from the zip. everything seemed like it was going perfectly smooth.
phone rebooted the first time, got the energy star screen and boot up sequence... Thunderbolt logo screen came on and it took a very, very long time before it just rebooted itself (probably 10 mins +).
now, it just boots up to the posting screens, energy start logo etc. goes to
Initialization finished........
Activating root access SUCCESS!
Beginning Andriod 2.2 boot sequence.........
Enjoy your HTC Thunderbolt
and just sits there....... been 10 minutes now --- any advice on what I can do?
I tried battery pull and reboot, stops at same place...
Thanks so much!!
background, i was on 1.1 prior to this update.
could of been a bad download. did you check the md5 of the file. I would download again and reflash.
You can try reflashing with the current download you have, if it dont work, redownload and flash again..
how can i get to a menu to flash again?
it just boots to the "Enjoy your HTC Thunderbolt" and sits there... I tried connecting through adb but the computer doesn't recognize the device since it hasn't booted up far enough.
power off the phone then hold power and volume down and it will boot into the phones white recovery, then in the menu select recovery to get back to clockwork recovery
(if power & volume down dont work then try power & volume up)
It is volume down. Once in recovery, go to mounts and partitions and mount USB storage. Plug into a pc, download the ROM, move it onto your card and then unmount, wipe, and flash.
Sent from my ADR6400L using Tapatalk
ok, thanks for the quick replies so far, you've got me able to flash again... i restored to a backup and tried flashing the required radio for chingy's 1.4
1.13.605.7 CDMA-LTE radio combo
However, after successfully flashing and booting back up, going into software information, the Baseband version still says 1.16.00.0402w_1
and my software number is 1.12.605.6
is this the radio flashed correctly? i was thinking the baseband version should be different...
any thoughts?
i don't want to try and flash 1.4 again until i know the radio is updated correctly....
you have the right radio and
the update software itself is 1.13.605.7 but the info was changed to protect the leaker of the update. The software will come up with the stock info,
well it appears it was a problem with chingy's 1.4 apparently. i tried it 3x and the same thing happened each time. MD5 was confirmed on all 3 attempts.
i flashed dasbamf 1.5 and it worked perfectly...
guess i'll be using this one for now
thanks for the help!
It's not the Rom I just flashed to my bolt and works fine so far
-Abuse- said:
well it appears it was a problem with chingy's 1.4 apparently. i tried it 3x and the same thing happened each time. MD5 was confirmed on all 3 attempts.
i flashed dasbamf 1.5 and it worked perfectly...
guess i'll be using this one for now
thanks for the help!
Click to expand...
Click to collapse
There is no problem with that rom or the file. Don't make claims like this unless you have proof to back them up.
Try flashing a different kernel... He is using a very undervolted kernel and it sounds like it doesn't play well with your phone... Try one of adryns kernels and it should work for you... I use ps mainly cause of the 4x5 but bamf is good also
Sent from my ADR6400L using Tapatalk
I've had this problem before as well...try doing another factory reset after flashing the Rom, it might get you up and running.
Sent from my ADR6400L using XDA App
Related
Need help!
I am rooted running BAMF 1.6.3. I haven't updated this in at least 2 weeks.
Something very random just happened. I noticed my phone was on 1x (I live in 4G area) so I decided to reboot it to see if that fixed it. When I rebooted it, it loaded up and came back to lock screen. I then hit the power button to turn off the screen. When I tried to wake it back up nothing would happen. I then pulled the battery and when it started back up it hangs on the white HTC screen. It will stay on there for about 1 minute and then the screen will turn off. 3 seconds later, the screen will turn back on with the same white HTC screen. It appears this loop will happen over and over. I pulled battery again and same thing. I tried to hold the power button and volumn down and then go to recovery. There I get error messages stating:
E; cant mount /cache/recovery/command
... cache/recovery/log
etc.
when i go to restore, I get the same messages. The phone then goes back to the white HTC screen and loops over and over.
I haven't tried factory reset yet.
Any ideas? This is random that this happened during daily use and not while flashing or mucking with it.
Please help!
R u running gingerbread radio
Sent from my ADR6400L using XDA Premium App
mschwartz26 said:
Need help!
I am rooted running BAMF 1.6.3. I haven't updated this in at least 2 weeks.
Something very random just happened. I noticed my phone was on 1x (I live in 4G area) so I decided to reboot it to see if that fixed it. When I rebooted it, it loaded up and came back to lock screen. I then hit the power button to turn off the screen. When I tried to wake it back up nothing would happen. I then pulled the battery and when it started back up it hangs on the white HTC screen. It will stay on there for about 1 minute and then the screen will turn off. 3 seconds later, the screen will turn back on with the same white HTC screen. It appears this loop will happen over and over. I pulled battery again and same thing. I tried to hold the power button and volumn down and then go to recovery. There I get error messages stating:
E; cant mount /cache/recovery/command
... cache/recovery/log
etc.
when i go to restore, I get the same messages. The phone then goes back to the white HTC screen and loops over and over.
I haven't tried factory reset yet.
Any ideas? This is random that this happened during daily use and not while flashing or mucking with it.
Please help!
Click to expand...
Click to collapse
so you are able to go into recovery then to restore.. correct? Are you running the MR2 Radio?
No, running the suggested radio for BAMF 1.6.3 which I think was the leaked froyo radio...and I haven't messed with this in over 2 weeks and have been fine since I last flashed. adrynalyne talkes about it in his first post here: http://forum.xda-developers.com/showthread.php?t=1057933
...and yes, I can get into recovery and restore, but can't get past the can't mount errors I see in recovery.
I am not sure if the radio suggested for BAMF 1.6.3 is the MR2 radio of if that is something else?
Download the full downgrade rename itand flash then see ifthat helps ?
Sent from my ADR6400L using XDA Premium App
Maybe a voltage issue. Is your battery all charged up?
mschwartz26 said:
...and yes, I can get into recovery and restore, but can't get past the can't mount errors I see in recovery.
I am not sure if the radio suggested for BAMF 1.6.3 is the MR2 radio of if that is something else?
Click to expand...
Click to collapse
Download the MR2 radio from here
http://www.multiupload.com/3U3QC9V1UL
Rename it to PG05IMG.ZIP.
Next go into your recovery.. mounts.. and mount usb storage.
Plop that zip file into the root of SD card..
Then do a battery pull and go into bootloader (power + vol down).. (or if you are on adb.. do adb reboot bootloader).
Install the MR2 radio after the prompt and then reboot your device..
see if that fixes it.. if not.. report back.
Ok, I will have to try all of this when I get home from work. I don't have the drivers or ADB installed on my work computer. I just went to mounts/mount SD storage and got this error:e: unable to write to ums lunfile (no such file or directory).
Is this b/c I am not connected to the computer with the drivers installed or a different issue?
Ah tryunplugging it or go to a different port or reinstapl drivers
Sent from my ADR6400L using XDA Premium App
I have been doing some research on the MR2 radio and through my quick research, I have seen people saying not to install it if you are running on Froyo not to install it, but only if you are running a GB ROM. Is this safe for me to try?
mschwartz26 said:
I have been doing some research on the MR2 radio and through my quick research, I have seen people saying not to install it if you are running on Froyo not to install it, but only if you are running a GB ROM. Is this safe for me to try?
Click to expand...
Click to collapse
MR2 radio actually comes with a Froyo RUU.. I don't know who is telling you not to have MR2 radio over Froyo.. because they are wrong. The RUU does have an updated software version (1.66 I believe).. instead of the 1.37 that you have.
Maybe I am reading this wrong then. I see you have posted in the xda thread below, so i assume I am just not reading this correctly (I am relatively new to all of this!). Thanks for the help so far.
http://www.droid-life.com/2011/06/08...reboot-issues/
http://forum.xda-developers.com/show....php?t=1115714
mschwartz26 said:
Maybe I am reading this wrong then. I see you have posted in the xda thread below, so i assume I am just not reading this correctly (I am relatively new to all of this!). Thanks for the help so far.
http://www.droid-life.com/2011/06/08...reboot-issues/
http://forum.xda-developers.com/show....php?t=1115714
Click to expand...
Click to collapse
"page not found" for both links.
Let's try that again...
http://www.droid-life.com/2011/06/0...io-updated-released-should-fix-reboot-issues/
http://forum.xda-developers.com/showthread.php?t=1115714
I just installed the drivers on my computer and still get this error when trying to mount the SD storage:
unable to write to ums lunfile (no such file or directory).
Any ideas on other things to try?
As far as I know MR2 only works with GB Roms, I don't believe it will work with Bamf 1.6.3
mschwartz26 said:
I just installed the drivers on my computer and still get this error when trying to mount the SD storage:
unable to write to ums lunfile (no such file or directory).
Any ideas on other things to try?
Click to expand...
Click to collapse
Have you tried pulling out your sd card and then putting it back in? I'm wondering if you maybe dislodged it when you pulled your battery the first time?
You're not the first person to have this problem. I remember seeing it - try a search. I did a little work and got -
http://forum.xda-developers.com/showthread.php?t=1096426&highlight=mount+cache+recovery
As I recall there is at least one more similar to this, don't know which Tbolt forum - Q&A or General.
mschwartz26 said:
Let's try that again...
http://www.droid-life.com/2011/06/0...io-updated-released-should-fix-reboot-issues/
http://forum.xda-developers.com/showthread.php?t=1115714
Click to expand...
Click to collapse
It does work on Froyo.. but only on Froyo 1.66 .. and NOT on the earlier version of Froyo.. which was 1.13
the reason why Chingy and Droid Life said it won't work on Froyo was because at that time.. only this radio was released.. and not the full RUU... and so they didn't want people flashing this radio over the older Froyo.
the RUU was released a few days later.. and it was the MR2 radio with Froyo.
However, I stand corrected... since you are the earlier version of Froyo.. MR2 radio WILL NOT work for you.
I was running Das BAMF 3.0 and then switched to anothe rom. I restored das BAMF and now I keep getting the message Sorry! Process system is not rssponding. I cant get past this screen.
If I reboot into recovery the I get an update message it wants to update:
[1] MDM9K
[2] Radio_V2
If I say yes to update then after the update I reboot and back to "Sorry Process...
If I say no then it reboots and same thing!
Help!
Wipe and reflash. It's what I had to do when mine did the same thing.
Sent from my ADR6400L using XDA Premium App
How?
Thanks for the response! How do I wipe... I cant get to any screens.
Donloric1 said:
Thanks for the response! How do I wipe... I cant get to any screens.
Click to expand...
Click to collapse
I had the same question when I started out. I'll make it easy on you.
Go into recovery, use the volume buttons to toggle up and down. Go to wipe data / factory reset. Select it and then confirm it. Then go to wipe cache partition and do the same. Then go to advanced and select wipe davlik. THAT IS HOW TO WIPE. This is recommended to do before flashing a new ROM.
Can't get past the update
I cant get past the update in recovery
Donloric1 said:
I cant get past the update in recovery
Click to expand...
Click to collapse
That's easy to get past. Just load a PGIMG05.zip file onto the ROOT of your SD card. ROOT means without being in any folders. If you're on BAMF 3.0 then you're on Gingerbread. So find the RUU file for unsigned Gingerbread RUU and place it on the ROOT. Then do an Hboot. Which is Power down and volume up at the same time when the phone is off. Make sure you don't have any PGIMG05 files on the ROOT. You probably do because you rooted your phone. If you don't you could end up with S back on.
**You did flash the correct Gingerbread radio...right?
**I have no clue where the Gingerbread RUU is. If you find it, please post it. It will be a fairly large file. Probably around 300mb+
EDIT:
I'm sorry but the RUU for Gingerbread isn't out yet. Try Hbooting the MR1 then Hboot the MR2 Radio RUU which is 2.3.4 base.
Link to Jcase radio thread: http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
I'm pretty sure, you'll need to flash the "PG05IMG_Mecha_VERIZON_WWE_1.13.605.7_Radio_1.16.00.0402w_NV_8k_1.41_9k_1.64_release_182727_signed.zip" on that page which should be the last link.
Take your SD Card out, put in a reader or another Android phone and delete the radio file from it.
Sent from my ADR6400L using XDA App
I've had this problem too and I've wiped and reflashed from scratch to fix it.
But this happens to all my backups, making nandroid backups virtually useless to me now. Anybody know why this happens? I've never had a problem like this before and it started after trying to restore from the new CM7 back to bamf 2.1....
A common solution would be to backup the SD Card and reformat it in Clockwork or with SDFormatter.. NOT IN WINDOWS.
When the house gets dirty, you have to clean it.
Sent from my ADR6400L using XDA App
I have tried to format/system and every other piece of advice i can find I still cant get any nandroids to restore... Any ideas?
I have search every possible thread regarding restoring a nandroid and have tried every possible fix... my only solution, which DID WORK, was to format/system, do a full wipe of all three, and then flash the original zip, I cant use any nandroids at all!!! if any one know why please tell me how to restore a nandroid for future use. thanks
format did not work for me either.
restores worked for me at when i came off of Synergy's ROM back to bamf3.0, but coming outta CM7 to bamf 3.0 busted it again...very strange.
str1der_D said:
format did not work for me either.
restores worked for me at when i came off of Synergy's ROM back to bamf3.0, but coming outta CM7 to bamf 3.0 busted it again...very strange.
Click to expand...
Click to collapse
I am using th3orys inj3ct rom and just wanted to see what Synergy was all about, when I wasn't impressed i tried to restore my nandroid (which i made right before i flashed synergy) and that is when all the trouble started... i tried everything that I know of and just had to reflash the original ROM and start from scratch, sux but at least my phone is back on.
I had this issue over the weekend. However I did do a restore prior to getting the error... I was texting my gf, and all of a sudden my screen wouldn't turn on... Pulled the battery and when i booted up I kept getting the error.
I had a PG05IMG.zip on my SD card so if I tried to boot to recovery from boot menu it wouldn't let me.
I took my SD card and plugged it into a PC using an adapter. Deleted the PG05IMG.zip and then booted to recovery. Restored my latest backup (3 days old) and everything worked.
Sent from my ADR6400L using XDA App
What the hell.. this same thing happened to me last night - never had this happen before.
Happened after restoring a backup of Das Bamf 3.0 RC 3
Guess I have to wait for my wife to come home with her old droid so I can plug my sdcard in to her phone and get rid of the pgimg zip
I was running A05PTH3ORY V1.4X and wanted to put on a new kernel to see if I could get better batter life. I flashed Tiamat's kernel and everything seemed to work fine for a little while while it was sitting on my desk. About 30 minutes later I reached over to unlock it and nothing, it had shut off.
I go to turn it on and I get a boot loop on the white HTC screen. I get into recovery to restore a backup and it get a minute into the restore and automatically reboots. So I try again but wipe data/cache first, same thing. So I try to just install a new ROM, same thing, reboots.
Don't know where to go from here....any help?
Can I rename a ROM to PG05IMG.zip and flash it through the bootloader????
schmaltzy said:
Can I rename a ROM to PG05IMG.zip and flash it through the bootloader????
Click to expand...
Click to collapse
No
tbolt ^_^_^
Same thing happened to me. You have to find the correct RUU to flash in bootloader. I flashed the stock RUU. Although I lost root, phone was fine again.
schmaltzy said:
I was running A05PTH3ORY V1.4X and wanted to put on a new kernel to see if I could get better batter life. I flashed Tiamat's kernel and everything seemed to work fine for a little while while it was sitting on my desk. About 30 minutes later I reached over to unlock it and nothing, it had shut off.
I go to turn it on and I get a boot loop on the white HTC screen. I get into recovery to restore a backup and it get a minute into the restore and automatically reboots. So I try again but wipe data/cache first, same thing. So I try to just install a new ROM, same thing, reboots.
Don't know where to go from here....any help?
Click to expand...
Click to collapse
Another member had the same problem as you and what eventually fixed it was a factory RUU run from the computer. You would then need to root the phone again. The other fix to try first is a different Micro SD card. Apparently if the Micro SD is bad or corrupted, when the phone is trying to restore the backup it encounters an error and reboots. If you don't have another Micro SD card then you can try formatting the current one. Formatting the Micro SD card will erase everything, I'm sure you know that. If you want to run a factory RUU from your computer this site has a couple different RUU's to choose from http://dougpiston.com/ThunderBolt/RUU/ Download one of the .exe RUU's not the .zip RUU's. Once you download it to your computer run it from your computer with the phone plugged in and turned on. Running the RUU is a last resort because you'll have to root your phone again, but if you've exhausted all your other options then go for it.
EEdaesung said:
No
tbolt ^_^_^
Click to expand...
Click to collapse
Tbolt! Thanks for the help on the IRC! It worked!
I flashed the MR1 RUU and it got me in. So all is well!
Question though....why? I can understand a boot loop because of my phone not meshing well with the kernel, but why wouldn't it let CWR work correctly?
schmaltzy said:
Tbolt! Thanks for the help on the IRC! It worked!
I flashed the MR1 RUU and it got me in. So all is well!
Question though....why? I can understand a boot loop because of my phone not meshing well with the kernel, but why wouldn't it let CWR work correctly?
Click to expand...
Click to collapse
Had the same problem and cure. I suspected a fubar clockwork only because I was running an older version.
courtesy of my rooted bolt
ILMF said:
Had the same problem and cure. I suspected a fubar clockwork only because I was running an older version.
courtesy of my rooted bolt
Click to expand...
Click to collapse
HMMM.....I was running the most up to date CWR.
Ok, I'll try to be short about this.
I did the RegawMOD method and was able to install Liquid Smooth on the phone. (1.45)
When I was going to install an update for that things when odd. (I always back up, reset and wipe before hand)
The update didn't take however I was able to the home screen. As it was weird I went back to restore and the Trwp did not back up correctly. The file was bad.
I was able to get back to the home screen and then setup my phone. I decided to wait for a while until the roms grew up a bit.
Now I was going to install Mean 1.4 today so I downloaded as the post said and installed the radio. Downloaded the rom. When into recovery backup, reset and wiped. When I tried to flash the rom TWRP just started rebooting.
I have tried it several times and also tried to recover and TWRP keeps rebooting. Now I am stuck on the HTC screen.
What do I do now? I feel the recovery is bad.
Any help greatly appreciated.
Maybe a bad recovery flash or corupt download.. Try reflashing recovery through fastboot, download the ROM again, do a FULL wipe and reflash the ROM.
Sent from my ELTE using Tapatalk 2
Thankfully I was able to install an earlier backup so at least I am running now. I have tried using Goo Manger to reinstall twrp 2.2. Just stays stuck at the download.
I haven't used the fastboot method before so I'll have to look that up. I want to get to mean 1.4 as included the OTA fixes because I have the wifi issue. Guess I'll have to wait until I have more time.
Thanks for the help.
Ok so I got goo manager to reflash the recovery.
Now I am on mean 1.4 and very happy. No more WiFi issues either!
Finally as useable as my OG EVO and dandy like this phone was ment to be.
Thanks for the help and thanks developers.
Very cool.
Sent from my EVO using xda app-developers app
I could really use some help here guys. Last night I flashed a new ROM - ThunderShed-v1.6_CM7.2-tbolt using Rom Manager/ClockworkMod (had been using CM7.1 without issue). I also updated the kernal to imoseyon_leanKernel_v6.2.1AOSP (didn't change ANY kernal settings) after reboot and install gapps. Everything seemed fine, however after powering off and back on again. I am now stuck in a boot loop. HTC screen phone vibrates, black screen, then HTC screen. I then attempted to boot into HBoot screen which I was able to do. Clicked on recovery and attempted to get into clockwork mod and restore the backup I'd created. Phone just reboots don't get to recovery and continuous HTC Screen black HTC Screen. This isn't my first rodeo with flashing roms (no expert by any stretch, but I'm pretty familiar with the process). Somehow I've screwed something up badly. I did attempt factory reset. I've also tried to downgrade to an older RUU although the RUU is loaded in HBOOT and seems to install (other than Bootloader is bypassed, due I believe because of Revolutionary ERROR - Can not roll back hboot version). Everything else Boot, recovery, system, splash1, userdata, etc all appear to update and show oK. After rebooting I'm back in the boot loop. I've tried installing stock roms rooted and unrooted without resolving the problem. ADB doesn't help either just never returns the device serial number. Loopfix just sits there waiting for device.
I'm am S-OFF (via Revolutionary)
-Revolutionary-
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-1.16.00.0402w_1
eMMC-boot
Feb 23 2011,20:42:55
There is no PG05IMG.zip file on my SD card. (apparently can cause boot looping)
I googled to my hearts content, browsed every forum and blog I could to find a solution. Found similar issues but was not able to use any of the know fixes out there. Part of the problem is ADB doesn't see my phone. I've looked at 'loop fix' and 'thunderbolt all in one tool' these don't work for me. Any suggestions would be welcome. I'd prefer not to have to throw money at the problem to fix it.
I know I screwed the pooch on this one, maybe someone has the skills to help me unscrew it.
Thanks much in advance!
Rem
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot as PG05IMG. See if that works and you can get into recovery.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
Windows 7 does signal that it sees a USB device but it shows unknown device. I've tried the HTC Drivers and the android USB drivers from google. Nothing doing. I am currently trying to install CWM via hboot (PG05IMG.zip). Got into CWM once tried to restore back to my backup but after the restore process same thing.
Thank you for your suggestions!
Rem
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
UPDATE: Unable to get CWR through HBOOT.
Rem
I have the same problem.
I have a brand new(refurbished) thunderbolt. I recently installed
*07-25-2012* JELLYBLUR *V1.3* CM7.2 - SPJESTER Production
I completely wiped and cleared the device. All was running fine, until I unplugged it from the charger then poof, boot loop. I can also access hboot but nothing seems to work. I have flashed a few roms, but I'm out of my depth here.
I will try putting and image on the sd card, since it does try to flash a radio when it boots.
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
I have successfully flashed both recovery, and the latest mr4 radio from hboot.
Without the sd card, I was able to get it booted once after each flash. Unplugging it forced it right back into boot loop(whether card was in or not).
The only options that work are hboot, and fast boot. Neither connects to adb, or the all in one tool.
Can I flash a regular rom from hboot? I have previous version of thundershed, and various stock roms on the SD card?
dizzyman1180 said:
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I've tried RUU both .9 and .19 both seem to flash fine. But after reboot same boot loop. After trying a few more times flashing various RUU I flashed .19 again. After rebooting the phone I was able to get into the phone, everything setup fine, google account, wireless, etc. But after rebooting again. Back in same boot loop. I've also tried using 2 different SD card to rule out a bad SD. Unfortunately same thing. Starting to think this is hardware not a bad rom or firmware.
Rem
Ok I tried a factory wipe, no go either....
Tried installing regular rom renamed as "pg....." that didn't work.
So I've been told as long as you have hboot you can fix anything...Not sure whats next? At this point I'd be happy to start over.
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
dizzyman1180 said:
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Dizzyman any help is appreciated. Thanks for taking an interest and trying to help!
Rem
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
Click to expand...
Click to collapse
Attempted the above on my device but no luck. Just same reboot loop. Just FYI. Thanks for the tip.
Rem
Even the different sim, eventually led to the same issue. I finally just convinced assurian that my replacement phone is defective (which is may be).
The only thing I can think of is that the jelly rom, combined with the all in one root tool somehow made a bad situation or the phone is simply defective.
Now my task is to see if I can flash something to make this stock...lol...I really don't want to send back a phone to assurion with clockwork and revolution on it if I can help it.
I suspect its going to be tricky as ADB doesn't work..
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
tonyagee said:
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
Click to expand...
Click to collapse
Tonyagee that's for the step by step. Tried on my Tbolt. Still boot looping. I appreciate you documenting what you did THANK YOU!
Your welcome...I definitely was on the edge of my skill set for sure....
So my thunderbolt is is in the same boat. The main cause for the boot looping seems to come from unplugging the usb from charging.
Mine will randomly stop the infinite boot looping and boot up. Sometimes it's quick. Sometimes it will take hours.
Most of the time when I manage to get it to run it is very difficult to get back into a custom recovery. It has to reboot the phone to get into recovery which most of the time just puts it into the infinite boot loop again.
If I plug mine into a computer it will charge but will not recognize the phone.
I've tried every fix known to man. No luck. I've come to deal with it as I've had this problem for two or three months now.
Sent from my ADR6400L using Tapatalk 2
---------- Post added at 08:09 PM ---------- Previous post was at 07:37 PM ----------
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
The mystery deepens...
Click to expand...
Click to collapse
Mine has done the same thing. I read that one of the failsafe ways to boot up clock work mod recovery is that it will automatically boot up after a battery pull and turn the phone back on with it plugged in.
If I plug the phone in while it is completely shut down it automatically powers it on and 9 times out of 10 it randomly reboots but sometimes it will boot up into recovery.
Sent from my ADR6400L using Tapatalk 2