Related
i looked around the forum and couldnt find the issue fix for my problem but here it is.
I just have a simple question about this how do you flash the gapps to your Droid Eris original rom. i was dumb enough to delete gtalk i luckly had root explorer and fixed it then well i had some issues and had to do a factory restore but when i restored gtalk was gone and i cant get any file managers to put gapps back on my phone. without it i cant do anything worth while with my phone but talk. i would appreciate all the help i can get on the issue. ive tried to download a file manager from the market but without gtalk i cant download from market and its a big issue
You'll probably end up spending less total time on this if you just bite the bullet and wipe, flash a ROM, and then reconfigure from scratch.
Even when flashing new ROMs, it has been widely reported on these forums that over-flashing a gapps package after the ROM has already been booted once does not seem to produce the correct results. I can't honestly say I know what the problem is there, but that's what has been reported - so I'm not optimistic that overflashing a gapps package is going to help you.
If you knew exactly what files you deleted from /system, and then you performed a factory reset, and then you put them back in place (using adb and the command line with the phone still in the recovery boot), that should work - but at that point you are already doing a factory reset, so why bother with the extra effort?
( I might be reading something into this which is not warranted from the facts you presented - do you have a custom recovery installed, and know how to use it, or did you perform a rooting operation which just kanged some stuff into the factory OS? )
bftb0
I use these
http://www.mediafire.com/?bupx532u98cfrj9
I'm not sure how well it will install on yours.
Sent from my KaosFroyo V39 Eris using XDA
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
jbergen said:
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
Click to expand...
Click to collapse
Whatever you do, DO NOT DO ANYTHING ELSE UNTIL BTFB0 responds to your plea for help.
Do not just start trying different solutions, DO NOT FLASH ANY RUU, if you know what that is. BTFB0 is the guy who can get your phone unbricked if anyone can. He is the expert, I won't pretend to be able to duplicate his knowledge in this area.
Be patient until he has a chance to see this. You don't have to PM him, I'm sure he'll respond when he has a chance here in public. He will ask specific questions about what version of bootloader you have, 1.47 or 1.49, and you might as well find out if it's S=OFF or S=ON.
Also, do you have Amon RA recovery on your phone and can you get to it?
Have you tried flashing anything else since your phone has gotten stuck in this boot loop? If not and you can get into recovery still, then simply wipe data, wipe dalvik, and try flashing again. Don't worry you're phone doesn't sound bricked, just like you got a bad download or an error when flashing the rom. I would probably try a different rom or at least re-download the one you want to use.
It may still be wise to wait for BTFB0 to get here and offer some more advice as I am sure he has more knowledge in this area than me. But I do feel confident that he will say the same thing as I have.
Well, the OP merely said that he is having trouble with a specific ROM; he didn't mention failures during flashing; so, his problem could be as simple as having failed to "wipe" before flashing his ROM.
jbergen:
If you can boot into a custom recovery, your phone is not "bricked". It's not even soft-bricked; it's just not booting into the main OS correctly.
Providing as much detail as you can is helpful to people that are offering help to you; in particular, the following pieces of information:
- What recovery is on your phone? (Amon_RA, Clockwork? What version #?)
- When you are flashing the ROM file with your recovery, do you notice any "E:" messages?
An "E:" at the beginning of a line on the screen means that an error occurred!
- Are you having this same trouble on more than one ROM, or is this the only ROM you have tried since you rooted?
- What method did you use to root the phone?
- Did you use the "Wipe data/factory reset" menu item before you flashed the ROM file?
- Did you make any Nandroid backups that you still have on your SD card? If yes, did you attempt to restore one? What was the result? (BTW, every rooted phone user should be making Nandroid backups before they flash ROMs - no exceptions.)
- Do you have a media card slot or USB card reader device that will allow you to copy a different ROM file onto your SD card? -OR-
- Do you know how to "mount" the SD card onto the PC when your recovery is booted? (On Amon_RA, it is called "Toggle MS-USB" or something like that; it's also in the Clockwork menu somewhere too)
Given the information you have provided, there are any number of things that could be going on. I would suggest downloading a different ROM to your PC (let's say the stock HTC Eris March 2011 ROM), and then transferring it to your SD card. Then,
- Verify the exact size of the file and/or MD5 signatures of the file (if the developer provided it).
- make sure your phone is well charged
- perform a "Wipe data/factory reset" from the recovery menu
- Flash the ROM file from the recovery menu - and pay attention to the screen to see if there are any `E:' errors
- If there are errors, there is no point in attempting to boot the phone
- If there are no errors, boot the phone.
- Report your results here - and answer the questions that I asked.
EDIT 3/30: This problem should be solved with the updated version of CWR found here: http://forum.xda-developers.com/showthread.php?t=1017817
Remember that until devs start bundling it with their roms, you will need to flash it after you flash a new ROM. (Superclean 2.9.2 and before includes the broken recovery).
The problem was in the fact that cwr didn't have root access. The updated one now contains this fix.
If you are trying to restore a nandroid from an old backup, you might have issues. I'll try to see about this scenario to see the easiest way to do it (the steps from the previous post in this thread should work.)
Also, it looks like dbdata doesn't auto-mount, so you need to go into the mount menu and mount it before being able to run the fix_permissions script, if you want to run that.
I think I got it fixed so that it will auto-mount it in the script, but it won't be recompiled until JT does it.
Original thread:
Info and links:
http://forum.androidcentral.com/ver...s/72212-warning-trouble-nandroid-backups.html
http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/72185-3-days-hell.html
This seems to explain a lot of the issues people have been having. Probably best to check that thread for updated info, but copying and pasting for those who are other forum-phobic:
Landshark said:
Do not try to restore a themed nandroid backup for the time being!!
DroidXcon has done a great job of putting together the thread about clockworkmod recovery (cwm), how to install it, use it, and how to fix permissions since that is not working in cwm right now. That is not the only thing not working in cwm right now. Right now you are also unable to wipe battery stats and restore a nandroid backup that includes a theme through cwm. What is a nandroid backup? Well you can check out posts 6, 7, & 8 of DroidXcon's clockwork mod thread for a detailed description with visual aids:
DroidXcon's Clockwork Thread Here
The problem seems to stem from not being able to fix permissions in cwm. If you read DroidXcon's thread it should make more sense and I can only do an injustice to his work by trying to explain it here myself. Bottom line is like I said above we are unable to successfully restore nandroid backups that include a theme at this time without ending up in a force close loop of hell (FCLOH) at boot animation, a.k.a. boot loop. Jaekar99, Suicide Shift, and I have been working at this for some time without any solution. We have only been able to successfully restore a nandroid backup of only the base ROM. Which is basically pointless since in basically the same amount of time it takes to restore a nandroid backup of just the base ROM, I can boot into cwm, flash the base ROM, reboot, boot into cwm, wipe cache and dalvik, flash a theme, reboot, boot to cwm, wipe cache and dalvik, flash a patch or two, and reboot my phone.
There is also a problem trying to flash a ROM and a theme in the same cwm session. Doing so will almost certainly put you into a FCLOH at boot. Best advice is as always try to only flash ROMs when your battery is at or near 100%. I have also had fewer problems when I flash while my phone is plugged in, either to an outlet, or into the usb on my computer. In addition to that, you will have fewer problems, if any, flashing the ROM by itself, rebooting, booting back into cwm, wiping cache and dalvik cache, flashing a theme if you want one, rebooting, booting back into cwm, then flashing any additional patches or mods, then rebooting. I know that is a lot of steps to take, but it's better than the alternative, which is ending up in a FCLOH, THEN having to take all those steps. You know, it's that whole ounce of prevention thing.......
For more information about flashing themes, patches, mods, and boot animations, you can get great information in Jaekar99's Themes, ROMs, Kernels, Boot Animations thread. I believe he is also covering some of this warning material in an effort to get it to as many people as we can.
Jaekar99's Themes Thread Here
So for the time being, do not try to restore a themed nandroid backup through cwm. If you have already created nandroid backups in cwm, I would think you can just leave them there for when we figure out a solution or fixing permissions gets repaired in cwm.
Any questions about this, you can usually find Jaekar99, Suicide Shift, or me here in the forums. Post your questions here and we'll do our best to answer them. I will also keep this updated with any new information or results of what we are testing. Thank you, and sorry to anyone who ended up in a FCLOH because I didn't get this information out sooner. (davey11)
Also for instructions on how to wipe battery stats since it can't be done in cwm, check out Gunnermike53's [How to] [Discussion] Improve Battery Life thread. It also involves commands entered in Terminal Emulator.
Gunnermike53's Battery Life Thread Here
And let's get one more plug in here. If any of this terminology is confusing to you, or you are new to rooting and want a great guide to get you started and better informed, check out Sheepdog Elite's [How to] First time rooting walk-through.
Sheepdog Elite's First Time Rooting Thread Here
Click to expand...
Click to collapse
There is a workaround in process of being written up.
The workaround is to reflash your theme over the nandroid once you get the restore finished. It's been mentioned that after a few days some one had it go bad that way, but it's what we've got for now.
Thanks GizmoDroid,
I was going to post the same info here when I woke up this morning. A group of us over at AC were up til the wee hours working on solutions and I was falling asleep at the keyboard. I'm trying to be more active over here and will update my OP at AC and this thread here.
For now a solution that gets you past the FCLOH is to boot back into cwm and flash whatever theme you have in the nandroid. That will get you past the FCLOH, but some patches and mods are being overwritten by doing that. So far, Adrynalyne's nuance patch stayed, but the mod settings patch did not. We are still working on other possible solutions. For now, other than doing this testing, I am not even bothering with nandroid backups as I can boot to cwm, flash ROM, reboot, boot to cwm, wipe cache & dalvik, flash theme, reboot, boot to cwm, wipe, flash patches and mods, and reboot all in about the same amount of time it takes to safely restore a nandroid of just the base ROM to avoid the FCLOH.
Right now I am going to see if restoring a nandroid, then flashing the theme in the same cwm session avoids the FCLOH.
Result of latest test - PASS
So flashing the theme over the nandroid restore in the same cwm session resulted in a clean reboot with no FCBLOH (Added in the B for Boot -Force Close Boot Loop of Hell.) Same problem as before though as Adrynalyne's settings mod was overwritten by the theme. So while this takes care of the FCBLOH problem, but it involves extra steps. Which like I said before kind of defeats the purpose of having a nandroid backup to restore - creating a complete build you can then restore all at once instead of having to do it piecemeal. Well at least for now there is a way to get around the FCBLOH when restoring a themed nandroid backup. Thanks Sheepdog Elite for all the help and for finding this workaround. Everyone just remember if you use this workaround and have any additional patches or mods included in your themed nandroid backup, after you restore check to see if all of your mods and patches are still in place.
Since I don't use nandroids/themes much, instead of doing a bunch of testing myself, I'll just ask you guys this:
We are possibly talking about a permissions issue. Why not do a system partition dump before nandroid, and then after restoring, then see what's different? After that point, you can make a script that sets the permissions on those files.
Or if files are actually missing or corrupted, then you will be able to find this out too.
GizmoDroid said:
Since I don't use nandroids/themes much, instead of doing a bunch of testing myself, I'll just ask you guys this:
We are possibly talking about a permissions issue. Why not do a system partition dump before nandroid, and then after restoring, then see what's different? After that point, you can make a script that sets the permissions on those files.
Or if files are actually missing or corrupted, then you will be able to find this out too.
Click to expand...
Click to collapse
Thank you sir. I will pass this along and see what we can find out.
landshark68 said:
Thank you sir. I will pass this along and see what we can find out.
Click to expand...
Click to collapse
Actually, after some preliminary research, my suspicions are not the system partition but the dbdata partition (/dev/block/stl10).
Clockwork has had problems with this one in the past. I don't know if it's on the backup end or restoring end, but I bet it's an issue with one of the scripts mounting the wrong partition, or folder. (clockwork mod mounts it to /datadata while stock rom calls it /dbdata)
GizmoDroid said:
Actually, after some from preliminary research, my suspicions are not the system partition but the dbdata partition (/dev/block/stl10).
Clockwork has had problems with this one in the past. I don't know if it's on the backup end or restoring end, but I bet it's an issue with one of the scripts mounting the wrong partition, or folder. (clockwork mod mounts it to /datadata while stock rom calls it /dbdata)
Click to expand...
Click to collapse
Shark. This is sounding like one of us needs to go back to school to become a script editor. This is getting beyond me.
JaeKar99 said:
Shark. This is sounding like one of us needs to go back to school to become a script editor. This is getting beyond me.
Click to expand...
Click to collapse
Yeah, he pretty much got beyond me at Actually, I'm just a guy who has learned quickly and gotten good at flashing, rooting, and problem solving to help other people. I am completely lost when it comes to the technical side. I am trying to learn as much as I can though so I'm not so lost. If we can eventually get this info to the right people I would be happy with that. If those right people are the devs, I am more than happy putting this issue on the shelf until they are completely done with their current projects. But anything I can do in the meantime to help I will certainly do or try.
landshark68 said:
Yeah, he pretty much got beyond me at Actually, I'm just a guy who has learned quickly and gotten good at flashing, rooting, and problem solving to help other people. I am completely lost when it comes to the technical side. I am trying to learn as much as I can though so I'm not so lost. If we can eventually get this info to the right people I would be happy with that. If those right people are the devs, I am more than happy putting this issue on the shelf until they are completely done with their current projects. But anything I can do in the meantime to help I will certainly do or try.
Click to expand...
Click to collapse
The good news is I just successfully restored a themed nandroid!
The bad news is that I'm not exactly sure what I did to fix it.
Nandroid backed-up a themed install.
Nandroid restored same themed install.
Rebooted.
Eternal bootloop ensued.
Rebooted to CWM.
While in CWM, I plugged in the usb and connected via ADB shell. I then typed the following (replace the red part with whichever nandroid backup folder you want to restore)
Code:
/sbin/nandroid restore /sdcard/clockworkmod/backup/[COLOR="Red"]2000-01-01.00.06.31[/COLOR]/
Did some other stuff
Rebooted and was greeted with a successfully working phone!
Now, I did some other things too, so I'm not sure if this was the only thing it needed. If this is all it was, then it should be an easy CWM fix. Someone want to try that and let me know?
If that's not it, I'll tell you the other things I did. It's got to be one of them
Things to remember: nandroid doesn't back up your kernel or modem at this time. If you try to restore an nandroid backup with an incompatible kernel or modem, you will have problems. Flash these first.
GizmoDroid said:
The good news is I just successfully restored a themed nandroid!
The bad news is that I'm not exactly sure what did it.
Here's what I think I did:
While in CWM, I plugged in the usb and connected via ADB shell. I then typed the following (replace the red part with whichever nandroid backup folder you want to restore)
Code:
/sbin/nandroid restore /sdcard/clockworkmod/backup/[COLOR="Red"]2000-01-01.00.06.31[/COLOR]/
If this is what did it, then it should be an easy CWM fix. Someone want to try that and let me know? If that's not it, I'll tell you the other things I did. It's got to be one of them
Click to expand...
Click to collapse
I will try it and let you know.
Nope, that one wasn't it. Nothing happened in adb or on the phone. Next?
landshark68 said:
Nope, that one wasn't it. Nothing happened in adb or on the phone. Next?
Click to expand...
Click to collapse
Nothing happened... at all? Like it just went back to the prompt without saying anything?
If that's the case, we have bigger fish to fry, because it should have at the very least complained or showed some text.
GizmoDroid said:
Nothing happened... at all?
Click to expand...
Click to collapse
Never mind. Jut took a while for it to start rolling in adb. stand by for results.
Boot loop city
landshark68 said:
Boot loop city
Click to expand...
Click to collapse
Not being facetious here, but I need to know exactly what I did different than you.
Can you tell me all the steps you did, in as much detail as you have patience for?
GizmoDroid said:
Not being facetious here, but I need to know exactly what I did different than you.
Can you tell me all the steps you did, in as much detail as you have patience for?
Click to expand...
Click to collapse
Well I'm going to start over. After I went through the procedures I scrolled back up and noticed you tried to restore your nandroid through cwm first. I flashed to just plain sc 2.9.2v through cwm, booted to recovery, ran the commands through adb, rebooted when adb said restore complete. I will now follow your exact steps and try restoring the nandroid through cwm first.
And since I've been flashing so much stuff today I'm going to wipe data, cache, and dalvik before trying to restore the nandroid if you think I should start from a clean slate.
Actually, hold off a second. I just redid the steps myself, and that wasn't all of the commands needed, apparently.
Before you jump through a bunch of hopes again, let me try some stuff.
landshark68 said:
Well I'm going to start over. After I went through the procedures I scrolled back up and noticed you tried to restore your nandroid through cwm first. I flashed to just plain sc 2.9.2v through cwm, booted to recovery, ran the commands through adb, rebooted when adb said restore complete. I will now follow your exact steps and try restoring the nandroid through cwm first.
And since I've been flashing so much stuff today I'm going to wipe data, cache, and dalvik before trying to restore the nandroid if you think I should start from a clean slate.
Click to expand...
Click to collapse
Ya, best bet would be to start clean, flash ROM and theme, nandroid backup, nandroid restore, then do the manual nandroid restore from adb. Try to eliminate all the variables.
If that's not it, then it had to be some funky mounting stuff I was doing. But I'd rather not get into that if I don't have to, because I tried a bunch of stuff all at once.
Standing by. I just made a build of sc 2.9.2v and ultimate honeycomb 3.1.1. I'll make a nandroid backup of that while waiting.
ETA - And don't worry about the appearance of being facetious or hurting my feelings or insulting me. I'm a grown person with thick skin. And I've read a bunch of your posts and have the same mind set. Don't insult, but tell it exactly like it is.
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Alright so I was enjoying my newly rooted and unlocked 4.4.2 dna, but that was ended abruptly when I found out about the resolution changer apk in the app store. I change the resolution once, all was okay except the dpi was too low. So I upped it by like 100 (note that it wouldve only been maybe 20dpi over the inital factory 440dpi it came with) and then I reboot and cant even see anything on the screen. It's black with glitchy-like lines through the screen. Can't unlock.
Things I have tried:
Re-Flashed the rom I had installed, that failed.
Re-Flashed my firmware for the installed rom, also failed.
Searched FOR DAYS for help (because I am a noob and don't want to just post a thread instantly after registering, but I really have no choice at the moment.
I even sent the producers of the app an e-mail but I have no hope in that pulling through.
Anyways,
I desperately need help, and any recommendations or ANYTHING will be highly appreciated.
Thanks,
Joey
You might try navigating to the offensive app via Twrp Recovery's File Manager, while in Recovery, with system mounted.
Then delete the apk from /data/app and reflash the rom.
I don't know if that will resolve the issue, but it may.
Good luck! :good:
santod040 said:
You might try navigating to the offensive app via Twrp Recovery's File Manager, while in Recovery, with system mounted.
Then delete the apk from /data/app and reflash the rom.
I don't know if that will resolve the issue, but it may.
Good luck! :good:
Click to expand...
Click to collapse
Hey, I really appreciate the reply, but after so much frustration with it I just wiped everything and reinstalled my rom and flashed supersu. It worked! I'm just glad I got my beloved dna back in working order!!