ATT Tilt. Running DZO's 09-09-10 nbh and 02-09-10 froyo system.
Phone runs flawlessly. Everything that I've tried works, extremely fast and responsive. It's all perfect except for one thing. Randomly upon rebooting I'm greeted with hundreds of the following errors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Followed by
After that android boots but immediately gives force close errors for system, bluetooth, google framework, messaging, and others. The phone is unusable until android is reinstalled.
There seems to be no apparent cause or warning. It may work for 2 weeks or less than 24 hours. Also doesn't seem to matter if there are lots of apps installed or just none other than what it ships with (other than google voice).
edit: I see DZO released a new kernel yesterday so I'm trying that for now but since I can't find this error on these forums (or anywhere) it's probably not on his list of things to fix.
That it is a problem with the new kernels. The solution is a system on NAND data on EXT2 for now.
Use my latest kernel (2.6.32) the problem is fixed.
where can i find the new kernel for kaiser??
here use atool to change device
Thanks a ton! I feel a little slow for not figuring that out but I couldn't find any info for android and yaffs errors. Giving your kernel a shot.
Oh and it may already be in the Atools thread but ubuntu users will also need the package "python-tk" to run it (awesome tool BTW!).
Edit: OK I just may be a little slow. I can't find the kernel at the link you posted, just the nbh and zimage.
.nbh is what you are looking for
Thanks, I had my terminology messed up. I thought the kernel was with the core files in the androidinstall.tar
Camera in Froyo??
Just flashed your new Kernel and have not seen any yaffs errors at all.....I was restoring Data almost daily with the older .32 kernel....Everything seems great except I seem to be having problems with the camera. I remember when android was early in development, the camera app would load but then immediately FC. This is something different where as the app never loads and my Kaiser completely hangs, requiring a reboot....
Using your latest kernel, Thoughtlessskyles newest build(based of new DZO Fresh Froyo) and latest radio.
Might flash an older Radio and see if that helps....
Anyone else seeing this awkward behavior??
Yeh the camera issues have not been sorted, switching to video will cause a FC right away where with the camera you can usually get one or two crappy pictures before a FC. Auto focus does not work, I could not get the wheel to work for focus either, add to that that brightness, white balance, etc do not work.
It could be a radio problem. Even with the new kernel I can still take pictures using the wheel to focus. Switching to video works for a few seconds now, used to be an instant FC. I'm using either the 1.70 or 1.65 radio (not sure how to tell with nand flashed android).
But even when it takes pictures in focus they are still pretty bad quality.
Camera works...
Just reinstalled Thoughtess' new rls and camera works...I'm starting to wonder if it is an app that is breaking the camera. I'm going to reinstall my apps from scratch and test to see when the problem arises....Trying a 170. radio version as well to see how it goes...
l1q1d said:
Use my latest kernel (2.6.32) the problem is fixed.
Click to expand...
Click to collapse
No such luck.
Worked for about a day then I went to use google maps and as soon as the GPS locked my position the phone froze. After that the yaffs errors were back. I tried to replicate the problem but it's worked fine all day. Scratch that, it's back.
I guess I'll stick the data partition on SD as mentioned earlier. How much of a performance hit is it?
If your phone freezes, and that leads to data corruption, that is different from data corruption when all else is good. Kernel crashes can cause corruption on any r/w filesystem that doesn't support journaling.
So, you got a GPS lock, and your phone froze. We should look into that. Is it reproducible?
Your other data corruption occurrences, do they happen after a crash, or out of the blue?
It's not always freezing. Most of the time it's a normal reboot when it happens. Unfortunately I can't reproduce the GPS freeze. It's worked normally all day and I've tried a dozen times today (including the location I had the first lockup).
Now that I've figured out how easy it is to backup and restore the /data partition ( I wasn't aware that's what was getting corrupted) it's not such a catastrophy when it happens. I'll just keep better backups until it gets solved in the kernel.
n2rjt said:
If your phone freezes, and that leads to data corruption, that is different from data corruption when all else is good. Kernel crashes can cause corruption on any r/w filesystem that doesn't support journaling.
So, you got a GPS lock, and your phone froze. We should look into that. Is it reproducible?
Your other data corruption occurrences, do they happen after a crash, or out of the blue?
Click to expand...
Click to collapse
I've been experiencing a lot of this issues on my Kaiser. I don't know if this info helps but I've been getting it the most when restarting the phone. Sometimes I would start seeing my wallpaper changed to default, some apps start force closing, it gets worse and worse until a lot of processes force close and I am unable to use the phone anymore.
I am using donut 1.6 with latest eclair kernel from dzo. I am unable to flash anything on my phone due to spl problems so I was looking for a solution. I'll attemp the EXT2 on SD and see how it goes. Thanks for the info in the thread.
Mi 2
Yep, happened to me too...
Reinstalled from scratch, and its ok... fast and everything...
I had just reinstalled it, with all the apps... and NO FREAKIN' BACKUP!
But still... the best build I ever tasted...
yaff no error with ext2 partition in sdcard
h4rdw4r3fr14k said:
Yep, happened to me too...
Reinstalled from scratch, and its ok... fast and everything...
I had just reinstalled it, with all the apps... and NO FREAKIN' BACKUP!
But still... the best build I ever tasted...
Click to expand...
Click to collapse
Hi i was in the same trouble with yaffs error and i install almost version of android donuts eclair froyo etc and my trouble was that I install the system and data in the flash memory, when i read the guide who explain how to install android in ext2 partition and i have 4 days my phone and i install software and works wonderfull...im testing but never more errror of yaffs my phone has installed kernel 2.6.32.9, with Thoughtlesskyle's Not So Super Froyo [RLS17] [10/20/2010] Kid Tested Mother Approved!
its work fine i hope my information be usefull thanks a lot of this forum. sorry my english
furiac3lta said:
Hi i was in the same trouble with yaffs error and i install almost version of android donuts eclair froyo etc and my trouble was that I install the system and data in the flash memory, when i read the guide who explain how to install android in ext2 partition and i have 4 days my phone and i install software and works wonderfull...im testing but never more errror of yaffs my phone has installed kernel 2.6.32.9, with Thoughtlesskyle's Not So Super Froyo [RLS17] [10/20/2010] Kid Tested Mother Approved!
its work fine i hope my information be usefull thanks a lot of this forum. sorry my english
Click to expand...
Click to collapse
I came to the same conclusion after a lot of trials and errors.
The only way to stop FC from popping up on startup after a freeze was to put data on sd card in ext2 partition.
I'm still keeping the system partition on NAND though, and so far so good.
My advice is to use MiniTool Partition Wizard Home Edition to change partitions on sd card. It is free, it is fast and it is so much more practical than gparted
Related
Hi everyone,
So I just flashed Synergy RC2 over RC1 and everything is amazing...can't wait to try out the pano cam. I would have posted this questions in the thread in development but I don't have enough posts to do so.
I'm not sure if I had this in RC1, but I've flashed RC2 twice with a dalvik and cache only wipe and still had this problem.
In the dropdown on the quick settings tab (where you can toggle the wireless networks), all of them say FC for some reason, and if they're on...well, refer to the screenshot. It doesn't seem to interfere with connections, just kinda annoying that they say that. I'm guessing I need to clear data in an app, but I'm not sure which. If I'm way off base, please point me in the right direction.
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
twinsin said:
Hi everyone,
So I just flashed Synergy RC2 over RC1 and everything is amazing...can't wait to try out the pano cam. I would have posted this questions in the thread in development but I don't have enough posts to do so.
In the dropdown on the quick settings tab (where you can toggle the wireless networks), all of them say FC for some reason, and if they're on...well, refer to the screenshot. It doesn't seem to interfere with connections, just kinda annoying that they say that. I'm guessing I need to clear data in an app, but I'm not sure which. If I'm way off base, please point me in the right direction.
Thanks!
Click to expand...
Click to collapse
That is strange. I'll say that I tend to come from the camp of full wipes before putting in a new ROM, not installing over an old one unless its specified that you can (even then I tend not to). My best recommendation for the least number of headaches for you would be to copy your SD to your comp, use amon_RA to wipe everything 3x, then flash the rc2 and enjoy the ROM.
If you really feel like trying to make it all play nice, try wiping dalvik and cache.
Sent from my PC36100 using XDA App
Watcher07 said:
That is strange. I'll say that I tend to come from the camp of full wipes before putting in a new ROM, not installing over an old one unless its specified that you can (even then I tend not to). My best recommendation for the least number of headaches for you would be to copy your SD to your comp, use amon_RA to wipe everything 3x, then flash the rc2 and enjoy the ROM.
If you really feel like trying to make it all play nice, try wiping dalvik and cache.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
+1 with the exception of wiping the SD card. Being that he has already had success in flashing RC-2, a wipe of the card shouldn't be necessary, but like you, I'm a fan of full wipes...
So what you guys are saying is:
- copy my entire SD card to my comp (i.e. go into E: and copy all contents to the desktop)
- amon_RA "wipe everything 3x." What wipes am I doing specifically (data/cache/dalvik/system/etc.) and what does everything mean? SD card and...?
- put everything back from the comp onto the SD card and reflash
Please correct me on anything I got wrong as I want to make sure I don't brick my phone.
Also, this may be a noob question but whenever I flash a new ROM, I do a Titanium Backup of app data, flash, and restore the app data. Yes, this restores my apps but is there a way to make it so I don't have to redo my home screens with the widget locations and apps I had on there prior to flashing? It's getting annoying having to do this every time I flash.
Thanks in advance.
twinsin said:
So what you guys are saying is:
- copy my entire SD card to my comp (i.e. go into E: and copy all contents to the desktop)
- amon_RA "wipe everything 3x." What wipes am I doing specifically (data/cache/dalvik/system/etc.) and what does everything mean? SD card and...?
- put everything back from the comp onto the SD card and reflash
Please correct me on anything I got wrong as I want to make sure I don't brick my phone.
Also, this may be a noob question but whenever I flash a new ROM, I do a Titanium Backup of app data, flash, and restore the app data. Yes, this restores my apps but is there a way to make it so I don't have to redo my home screens with the widget locations and apps I had on there prior to flashing? It's getting annoying having to do this every time I flash.
Thanks in advance.
Click to expand...
Click to collapse
No worries. To answer your questions.
1) Yeah, copy your entire sd card to your computer. Any flashaholic will tell you that cards can go bad and that when flashing, things can go wrong so its very helpful to have all your photos and whatnot saved on your computer regularly.
2) Wipe everything on the list that can be wiped. As DJ said though, wiping the card isn't always a necessity, I simply do it because I love a good, solid clean start when going from say an AOSP rom to a Sense based one.
3) Usually I keep all my data and personal stuff in the cloud so I tend not to do alot of sd backups and restores. Every photo I take is regularly uploaded to picasa, my contacts come from gmail, all my emails are server hosted by gmail, documents are in google docs, you get the idea. So when I come into a new rom, I just download the apps I need and everything populates as I need it to. However if you have alot of photos or music and such, find it on the card backup on your comp and just copy that stuff back. Dont forget your nandroid backup as well.
4) As I'm not big into restoring and more into clean starts, I don't tend to use titanium backup for anything, so that question might be better geared for someone else to answer, but I think one of the big points of the program is to actually try to restore everything to the way it was, so I would imagine that it is a feature of the program, but again, really not sure.
As for bricking your phone, experience and observation of thread upon thread of people worrying about having bricked their phone has shown that for the most part, your EVO is a pretty damn durable beast. Really the ways to brick it are few and far between (dont pull the battery when updating radios and such). For the most part, anything you screw up can be undone. When I was first learning how to root and all that, I saw all sorts of threads and ideas and how to's that lead me down SO MANY wrong paths. I thought I bricked it like 5 or 6 times, but it just turned out I had pressed a wrong button on boot up, didn't flash the right recovery, didnt wipe something enough times, etc. etc.
These forums have alot of great people on them, if you think you borked your phone, dont do anything to it, toss up a message and a description of what happened, and you should get some decent responses pretty quick. Good luck with your rom flashing.
You're so helpful Watcher, I thanked you twice
Anyways, I forgot to mention I've had a couple of random power offs since installing Synergy so it's probably a good idea I go all-out on my wiping anyways.
I'll report back with results later today when I get around to reflashing.
twinsin said:
You're so helpful Watcher, I thanked you twice
Anyways, I forgot to mention I've had a couple of random power offs since installing Synergy so it's probably a good idea I go all-out on my wiping anyways.
I'll report back with results later today when I get around to reflashing.
Click to expand...
Click to collapse
lol, I appreciate the gesture. I work wednesdays through saturday 10+ hour shifts, so generally not around too much on those days, but since I've been more proactive in the community, I keep my xda app handy when my evo isn't busy telling me where my next stop is. Anyway, good luck and by all means let us know how it works out.
@Watcher07, you're alright, my friend....
Posting & replying from my EVO 4G
Well, looks like it worked...thanks guys. Did a triple wipe on everything and it all looks good.
I don't know if I should start a new thread on this, but I just saw that Spare Parts got carried over even after wiping and flashing. I don't use it often and the battery history button FCs on me. So I tried to uninstall it via Market and Manage Apps and it doesn't have the option to uninstall anywhere! So I have a supposedly installed app that won't let me uninstall it...wtf?
Make a new thread or can anyone assist with this?
twinsin said:
Well, looks like it worked...thanks guys. Did a triple wipe on everything and it all looks good.
I don't know if I should start a new thread on this, but I just saw that Spare Parts got carried over even after wiping and flashing. I don't use it often and the battery history button FCs on me. So I tried to uninstall it via Market and Manage Apps and it doesn't have the option to uninstall anywhere! So I have a supposedly installed app that won't let me uninstall it...wtf?
Make a new thread or can anyone assist with this?
Click to expand...
Click to collapse
Spare Parts comes pre-installed on several custom roms so I doubt that it was carried over after a wipe, my friend, but i could be wrong. Still, I'm glad you got everything all taken care of. As for removing it, you will have to maneuver to the system/app folder via ADB or a system level file manager like Root Explorer to delete it or anything else you don't want.
Posting & replying from my EVO 4G
dougjamal said:
Spare Parts comes pre-installed on several custom roms so I doubt that it was carried over after a wipe, my friend, but i could be wrong. Still, I'm glad you got everything all taken care of. As for removing it, you will have to maneuver to the system/app folder via ADB or a system level file manager like Root Explorer to delete it or anything else you don't want.
Posting & replying from my EVO 4G
Click to expand...
Click to collapse
Yeah, it must be bundled into Synergy (don't see that on myn's feature list). I went into Root Explorer and only thing in there was the Spare Parts installer, so I just left it and guess I'll deal with it.
Consider this thread resolved.
dougjamal said:
Spare Parts comes pre-installed on several custom roms so I doubt that it was carried over after a wipe, my friend, but i could be wrong. Still, I'm glad you got everything all taken care of. As for removing it, you will have to maneuver to the system/app folder via ADB or a system level file manager like Root Explorer to delete it or anything else you don't want.
Posting & replying from my EVO 4G
Click to expand...
Click to collapse
+1 to this.
Sent from my PC36100 using XDA App
twinsin said:
Yeah, it must be bundled into Synergy (don't see that on myn's feature list). I went into Root Explorer and only thing in there was the Spare Parts installer, so I just left it and guess I'll deal with it.
Consider this thread resolved.
Click to expand...
Click to collapse
That file is safe to remove. If you'd like, you can 'freeze' it with Titanium Backup.
Posting & replying from my EVO 4G
Hey all, I've been getting "Insufficient storage available - Installation errors" on my EVO 4G eventhough I have a 32GB sdcard (but only 30MB of internal storage & yes I've moved all existing installed possible apps to sdcard, cleared caches & unmounted-remounted sdcard), what's the best way to resolve this?
I'm still running 2.2 unrooted but considering rooting soon & maybe cm7 or other rom but I'm not sure I want to risk issues when I need it working..
Also notice it is slow to respond upon reboot, maybe due to apps trying to update but encountering the insufficient storage available installation error..
-Appreciate helpful replies
BumpBump..
Dude you need to be rooted and switch rom bc stock evo don't allow you to place Apps on sd card, even with the apps2sd application
Sent from my PC36100 using XDA Premium App
You can try formatting your sd card. Also you should obtain S-OFF asap while you still have 2.2. I read a few threads about people's phones auto updating and now they are SOL!! Even if you don't flash a new rom you can get S-OFF b4 its too late. Get S-Off and ruu back to stock at least...
smartboy36 said:
Dude you need to be rooted and switch rom bc stock evo don't allow you to place Apps on sd card, even with the apps2sd application
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Not true. It just doesn't let you move all of them.
OP, rooting is going to give you some options, notably the ability to use an ext partition for your apps and/or dalvik cache. How many apps do you have? Even if every app were movable to SD (which of course it isn't), dalvik cache will eat up space on your /data partition. This is basically an optimized version of each installed application's code, and it can eat up as much as 1-2 MB per app. It's not listed in the app's storage usage under Settings -> Applications, and you can't do anything about it if you're not rooted.
Of course, another thing to look at is whether any apps are using excessive amounts of data. For example, I use Good messaging from work, and I have to clear data about once a month because the app accumulates data that never goes away. There's no option to purge or limit the amount of email it stores locally from within the app, and it stores big log files too.
Dude I'm on kings Alliance and I have 150 Apps with room for more. Come to the alliance and don't worry again
Sent from my PC36100 using XDA Premium App
This phone should've had more space for apps anyhow. Lol
I tried a new card today, same crap, I have about 100 apps..
jayare313 said:
This phone should've had more space for apps anyhow. Lol
Click to expand...
Click to collapse
Totally agree especially since it was originally released with 2.1, I got it the day the Nexus S was released which I seriously considered but since I use it a lot for Nav preferred EVO's larger screen & louder speaker.
I've been tempted to root & custom ROM since even before I got it but every time I read about brick risk I become less inspired to try it until I have another device I like as much as the EVO 4G..honestly what is the brick risk?
BTW, people keep telling me how much better the battery life is on cm7 etc, is there are a comprehensive chart of all the ROMs & battery life-feature set?
-Thanks
SMARTPHONEPC said:
I've been tempted to root & custom ROM since even before I got it but every time I read about brick risk I become less inspired to try it until I have another device I like as much as the EVO 4G..honestly what is the brick risk?
Click to expand...
Click to collapse
Very, very low. I can't say there's no risk, but as long as you follow the instructions, it's very low. I personally used Unrevoked back in the day. As others have mentioned, since you're still on 2.2, you should do it. Once you take the OTA update to 2.3, it's game over on rooting for now. You can even just root but leave the stock ROM on there. Just get S-OFF while you can.
the way i see it you have to purposely want to mess up your phone when it comes to rooting as long as you you got a recovery yer good
Ugh i have the same issue.
TO preface:
Yes I know how to free room up...see here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yet every time i try to install an app from the market OR even an APK on my SD card I get the insufficient storage space available.
I am rooted and on Synergy ROM but have never had this issue before. if ANYONE knows how to fix this that would be great. I can't even finish my restore from Titanium Backup.
DougB541 said:
Ugh i have the same issue.
TO preface:
Yes I know how to free room up...see here:
Yet every time i try to install an app from the market OR even an APK on my SD card I get the insufficient storage space available.
I am rooted and on Synergy ROM but have never had this issue before. if ANYONE knows how to fix this that would be great. I can't even finish my restore from Titanium Backup.
Click to expand...
Click to collapse
Hmmm rooted with space & you still have this ?
I think ive answered this question 10 times already .
All you have to do is install a task killer...kill all apps...then go download and install your app.
This always works for me
The error is memory..not storage
-storm
http://forum.xda-developers.com/showthread.php?t=855424
How bout everytime I post this, nobody lets me know if it worksfor them or not....
-storm
r.storm85 said:
How bout everytime I post this, nobody lets me know if it worksfor them or not....
-storm
Click to expand...
Click to collapse
Nope..
The other day when you posted it I was actually able to update-install a few apps without the error so I didn't need to try it but now that I was getting that error again I tried your suggestion with no difference. I was hoping it would be that easy but no such luck
SMARTPHONEPC said:
Nope..
The other day when you posted it I was actually able to update-install a few apps without the error so I didn't need to try it but now that I was getting that error again I tried your suggestion with no difference. I was hoping it would be that easy but no such luck
Click to expand...
Click to collapse
Oh ok cool.
It always works for me.
So maybe it is storage??
Its weird. First time I came across this I was trying to flash a recovery through terminal emulator.
I got this read memory error. Thay totally screwed my recovery.
It was fixed by killing all apps then installing the recovery.
Have you tried installing your apps right after a reboot??
-storm
r.storm85 said:
Oh ok cool.
It always works for me.
So maybe it is storage??
Its weird. First time I came across this I was trying to flash a recovery through terminal emulator.
I got this read memory error. Thay totally screwed my recovery.
It was fixed by killing all apps then installing the recovery.
Have you tried installing your apps right after a reboot??
-storm
Click to expand...
Click to collapse
Yup on trying to install apps right after reboot, it may have worked a couple times but doesn't work consistently now..
It's lame that the EVO only came with 1GB internal storage, I refused to get it until 2.2 in part because when it released with 2.1 you couldn't even natively run apps off microSD so you would have to rely on that whopping 1GB. I didn't anticipate having this issue with 2.2.
I still love my EVO but this is aggravating. Before I would try to root-customROMs I'd try to delete some non-essential apps, any suggestions on how much storage room to shoot for?
I didn't expect to still be unrooted stock 2.2 at this point but I may be more pissed if something went wrong than psyched with the added freedom-at least until I see my next phone in the market I like more than the EVO..
So my EVO became so unresponsive part of me wanted to take a bat to it, I had to remove the battery, reboot where it was still ridiculously slow, saw that my storage was down to 500k..
I deleted a couple apps & got it back up to 40MB, was able to update an app without this error but couldn't download another where the error occurred again. After another reboot was still getting a Low on space Notification but at least the EVO was useable again except when trying to open the Market-just hangs..
Considering backing everything up & doing a factory reset (& even dumping Android if the next iPhone is cool enough-but probably not )
I still can't believe HTC only put in 1GB internal storage for an otherwise great phone, EVO 3D is pretty cool but its speaker seems quite weak compared to EVO..
Thoughts?
I just started using boot manager and after some frustration it appears that I have it working now. I was wondering though after booting into a rom from slot 2, getting the settings, sounds, wallpapers, folders, widgets, etc.. setup will all that stay the same after booting into a rom from another slot or going back to the phone rom and then back to slot 2 rom. Thanks for your help.
scott7044 said:
I just started using boot manager and after some frustration it appears that I have it working now. I was wondering though after booting into a rom from slot 2, getting the settings, sounds, wallpapers, folders, widgets, etc.. setup will all that stay the same after booting into a rom from another slot or going back to the phone rom and then back to slot 2 rom. Thanks for your help.
Click to expand...
Click to collapse
Yes, everything you change/mod/add/delete will save to this slot. I have fully customized ROM's running on each slot and I like to use this as an evaluation for new ROM's.
Has any one had any luck getting skyraider zeus to work with BM. It will install to a slot just fine but it won't boot. I do have the force large boot.img checked.
The only way i got Zeus to work was to load onto phone then restore to a slot on boot manager an it will run fine.Sense roms seem to be more tricky to run with boot manager.
I tried installing a nandroid twice and each time it finished the notification said click here for boot options. I clicked it and it just went back to BM and the only option was to stop install. Any ideas?
Don't mean to hijack, but I get an error when installing cm7, when boot manager is making a boot.img. I already set the setting for larger boot.img. Any body got ideas?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Make sure logging is disabled in Superuser settings and make sure to turn on "screen on during install" in Boot Manager settings along with the force large boot.img. If both those settings are set like that and it still won't work just keep trying it will after a few attempts. I have struggled with this app but have stuck with it and now I love it. I started a thread in the General section called, "Boot Manager Discussion", I am hoping to get some user support, tips and tricks started like I have seen in other forums on XDA but for other phones.
RRF12 said:
The only way i got Zeus to work was to load onto phone then restore to a slot on boot manager an it will run fine.Sense roms seem to be more tricky to run with boot manager.
Click to expand...
Click to collapse
can you explain how you did this? I am not sure how to restore to a slot. I would like to have MIUI as my phone rom (since you can't get data as a slot rom) and restore my phone rom (bindroid) to slot 3. I looked under all the settings I could find, but can't seem to find the answer.
thanks in advance!
420fan said:
can you explain how you did this? I am not sure how to restore to a slot. I would like to have MIUI as my phone rom (since you can't get data as a slot rom) and restore my phone rom (bindroid) to slot 3. I looked under all the settings I could find, but can't seem to find the answer.
thanks in advance!
Click to expand...
Click to collapse
Install the ROM like normal, (ie: wipe and install via recovery) set it up like you want, backup, and restore the backup of whatever you want to, start up boot manager, then select this option. "restore nandroid"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So to brake it down, install Rom like normal, make a backup and use that backup to move Rom to a slot instead of being the phone Rom?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
JHumBL3 said:
So to brake it down, install Rom like normal, make a backup and use that backup to move Rom to a slot instead of being the phone Rom?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Click to expand...
Click to collapse
Essentially yes.
Ok I will try that now
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
tylerlawhon said:
Install the ROM like normal, (ie: wipe and install via recovery) set it up like you want, backup, and restore the backup of whatever you want to, start up boot manager, then select this option. "restore nandroid"
View attachment 869251
Click to expand...
Click to collapse
Thanks a lot, I don't know how many times I have looked for this and went right by it. Trying it now.
Edit: Tried that with a sense rom (bindroid) and it hangs at splash screen. Had to do the two finger salute and get back into recovery. hmm. Got large boot.img checked, any other thoughts?
Still not working but every now and again I will try it again to see if it works.
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Besides checking "force large boot.img", also make sure to check "screen on during install" in boot manager settings. You also need to disable logging in the settings of superuser. It was suggested to me and seems to work, use ext2 instead of ext4 as long as boot manager detects ext2 for the rom you want to install to a slot.
JHumBL3 said:
Still not working but every now and again I will try it again to see if it works.
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Click to expand...
Click to collapse
I had a couple of times the boot process stuck at splash screen. What worked for me, in addition to checking the large boot image, disable su logging, screen on during flashing etc- was choosing ext2, not ext4.
The splash screen lingers a little longer than usual, so be patient for a couple of minutes before giving up and pulling battery.
However, after trying a few roms and although boot manager is really cool, I can't say it is different than wiping, flashing a rom and then restoring other roms from recovery- it takes more or less the same amount of time (and sdcard storage).
Also, I noticed that although I have flashed gasps, after boot it didn't recognize them, Boot Manager doesn't like it (don't know why, maybe some licence check? is this really necessary???). So, to revert back to phone rom I always need to go through recovery and flash boot.zip again.
The same applies if for whatever reason with the booted rom one cannot gain Wifi access or data, then BM won't start, back again to recovery.
IMHO it is just a hassle to use, takes too much time, but is nice if one doesn't like to go too much through recovery, doesn't trust rom manager and so on. Or, if one wants to keep several roms and go back and forth between them.
Sent from my HTC Glacier using Xparent Cyan Tapatalk
Hey everyone,
Sort of an odd problem here. So I've been flashing ROMs for over a year without only a few scares and oopses. Recently, I tried to use
the in-ROM updater, and it crashed the phone. Then after being unable to reboot the phone or get into CWM, I tried to use a one click restore
to get back to stock and then install the update through CMW. But something went wrong with ODIN and the phone became unrecogizable by the computer. Long story short, after hours of reading, the phone went to Sprint, where i was handed a new phone.
Got home, stuck in my old microSD card, to restore my data from my Nandroid. I rooted the phone, installed CMW, installed Blu Kuban with no issues. BUT THEN, I restored my data. It took a long time...like almost half an hour. The majority of that time on the MD5 check. The phone seemed to work fine. Then, in the middle of launching an app, it crashed...and it crashed HARD. But I could get into CMW. Any attempt to wipe did not help. I reinstalled the ROM, it would fail in the middle. The only way to break out of this and make progress was to throw a DIFFERENT ROM on the microSD and install that. I got Kuban back on, restored my data, and had it crash again, same symptoms, same problems. My question is: Could all this be caused by a corrupt nandroid? If it isn't that, what is causing all of this?
HELP!!
hint, stop restoring your data lol.
But yeah, def your data(probably). Try installing a rom and without restoring your data(after a full wipe) and go from there
Sent from my SPH-D710 using xda premium
Agreed, consider your restore toasted. Wouldn't the first fail or two deter you from trying to restore anymore? Haha, no offense or anything.
Sent from my SPH-D710 using XDA
Well it all just seems so mysterious. The latest is that rather than restoring data, I did a full restore. Then I updated to the latest zip in CWM. The phone ran fine most all day.....and then crashed and burned again. I'm wondering if it could be a disagreement between the Tegrak program and the kernel? I'm going to try to do a full restore and, while it's still on the old version, uninstall Tegrak, then update and see what happens. Why do you suppose the data is passing the MD5 test if it's corrupt? Any input is greatly appreciated.
Okay, got it up and running again. Uninstalled Tegrak and I'm not going to update to the latest and see what is what. If I were to install Titanium and do an app backup while it's still running, would that suffer from the same corruption as Nandroid backup? I'm assuming doing a Android backup of it while it's running would do nothing to address whatever corruption is there?
Titanium pro can pull apps and data from nandroids btw.
sent from MY BAD A$$ ET4G
I would suggest odin back to stock then reformat you sd card from within settings/storage/unmount ext sd/format then start fresh. Reroot, reinstall CWM, do a fresh install of all your apps from the playstore then do your backups. I have heard of new phones having conflicts with sd cards maybe that will fix your problem
bigdaddy619 said:
I would suggest odin back to stock then reformat you sd card from within settings/storage/unmount ext sd/format then start fresh. Reroot, reinstall CWM, do a fresh install of all your apps from the playstore then do your backups. I have heard of new phones having conflicts with sd cards maybe that will fix your problem
Click to expand...
Click to collapse
He is right some times that's the best way to go. Also along with titanium backup I use rom toolbox to back up apps. It backs up the actual apk so its the fastest way to start fresh.
Sent from my SPH-D710 using xda app-developers app
Titanium backs up the actual apk too. Just when restoring choose app only.
sent from MY BAD A$$ ET4G
TiBu also makes a flashable zip of your apps now too that you can just flash in recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So after Titaniuming things after a restore I waited to see if the phone would crash. Sure enough, it did. So I did one click Odin back to stock rooted I27. Added CWM. Then after a double wipe, flashed Blue Kuban 1.5.1. Then installed Titanium, restored my apps, signed back into Google....etc, etc.....and, on the way to the gym it CRASHED AGAIN. HOW IS THIS POSSIBLE? What could possibly have come with the phone? Does my particular phone just not play nicely with this ROM? Any suggestions would be appreciated. My next experiment is to go from stock again and install a different ROM, restore apps, and see what happens. If that crashes too I don't know what to think.
Macros746 said:
So after Titaniuming things after a restore I waited to see if the phone would crash. Sure enough, it did. So I did one click Odin back to stock rooted I27. Added CWM. Then after a double wipe, flashed Blue Kuban 1.5.1. Then installed Titanium, restored my apps, signed back into Google....etc, etc.....and, on the way to the gym it CRASHED AGAIN. HOW IS THIS POSSIBLE? What could possibly have come with the phone? Does my particular phone just not play nicely with this ROM? Any suggestions would be appreciated. My next experiment is to go from stock again and install a different ROM, restore apps, and see what happens. If that crashes too I don't know what to think.
Click to expand...
Click to collapse
Did you reformat your sd card?
No. Is doing the X2 wipe in CWM not enough? How would I do that? Anyway I could keep the MASSIVE downloads from various games? If I shifted them to my harddrive and then moved them back?
Macros746 said:
No. Is doing the X2 wipe in CWM not enough? How would I do that? Anyway I could keep the MASSIVE downloads from various games? If I shifted them to my harddrive and then moved them back?
Click to expand...
Click to collapse
Transfer your games to your pc, then go to settings/storage/unmount ext sd card/ then it will give you the option to format
also, seeing as this saga started on a different phone...and obviously that SD card is no more, I don't understand how it could be that. Or are you suggesting it's an issue with the external microSD?
Macros746 said:
also, seeing as this saga started on a different phone...and obviously that SD card is no more, I don't understand how it could be that. Or are you suggesting it's an issue with the external microSD?
Click to expand...
Click to collapse
From what I understand from seeing other posts the data on your card is not matching your phone
bigdaddy619 said:
From what I understand from seeing other posts the data on your card is not matching your phone
Click to expand...
Click to collapse
Okay, so I'm formatting my internal SD card correct? And I'm doing this through CWM? I just tried in the format/sdcard and I got an error mounting it. Sorry to be thick here. By the way, it's Kuban_recovery 0.0.1
Thanks for the help so far, I really appreciate it.
Macros746 said:
Okay, so I'm formatting my internal SD card correct? And I'm doing this through CWM? I just tried in the format/sdcard and I got an error mounting it. Sorry to be thick here. By the way, it's Kuban_recovery 0.0.1
Thanks for the help so far, I really appreciate it.
Click to expand...
Click to collapse
external sd card!!!!!!! your micro sd card. that can be done settings/storage/unmount ext sd card/ then it will give you the option to format
bigdaddy619 said:
external sd card!!!!!!! your micro sd card. that can be done settings/storage/unmount ext sd card/ then it will give you the option to format
Click to expand...
Click to collapse
Reformatted....crashed. Operating without external SD....crashed. Clean install of Blu Kuban with no restore except though account sign in with Google.....crash. Clean install of Venum's ROM....crash. My final test is a restore of system ROM....but I am beginning to suspect that the replacement phone they gave me at Sprint is faulty. Because now it obviously has nothing to do with a corrupt backup. Anyone have any last minute suggestions?
Macros
Macros746 said:
Reformatted....crashed. Operating without external SD....crashed. Clean install of Blu Kuban with no restore except though account sign in with Google.....crash. Clean install of Venum's ROM....crash. My final test is a restore of system ROM....but I am beginning to suspect that the replacement phone they gave me at Sprint is faulty. Because now it obviously has nothing to do with a corrupt backup. Anyone have any last minute suggestions?
Macros
Click to expand...
Click to collapse
So the verdict is in all: Faulty phone AND faulty battery WOO HOO! Thanks for checking those refurbs Sprint....grrr....when I think of the hours of grief.....sigh. New phone arriving tomorrow. Thanks so much for all of your help. Everyone who tried to help I SO appreciate it! Can't wait until I have Blu up and running on the new phone.
Macros746
NEED HELP RIGHT AWAY! WORK PHONE DEAD IN WATER!
My battery died during a boot and the phone is still stuck at the Samsung S screen. The boot sound plays and the samsung animation plays continuously but never gets further. I left it for 20+ minutes and rebooted trying several times without success.
I can still access TWRP recovery. I tried fix permissions and clear caches but same problem exists. I mounted the internal and external sd and did full backups to my PC but I do not have a current full backup in TWRP or nandroid I may have an older TWRP backup from just after flashing the ROM but does not have apps or data.
Is there anything I can do to repair the boot without reflashing the ROM? What would happen if I flashed the same ROM over the current ROM? Just want to know if there is a possibility that I would not have to completely resetup the phone.
I have been on here before but just created a new account to ask for help. I have read the ENTIRE Jedi Mind Trick Rom thread before but dont remember seeing anything that would help this and I really could use a solution ASAP!
Thanks in advance. Any help is very appreciated!!
DirtyBreakz said:
NEED HELP RIGHT AWAY! WORK PHONE DEAD IN WATER!
My battery died during a boot and the phone is still stuck at the Samsung S screen. The boot sound plays and the samsung animation plays continuously but never gets further. I left it for 20+ minutes and rebooted trying several times without success.
I can still access TWRP recovery. I tried fix permissions and clear caches but same problem exists. I mounted the internal and external sd and did full backups to my PC but I do not have a current full backup in TWRP or nandroid I may have an older TWRP backup from just after flashing the ROM but does not have apps or data.
Is there anything I can do to repair the boot without reflashing the ROM? What would happen if I flashed the same ROM over the current ROM? Just want to know if there is a possibility that I would not have to completely resetup the phone.
I have been on here before but just created a new account to ask for help. I have read the ENTIRE Jedi Mind Trick Rom thread before but dont remember seeing anything that would help this and I really could use a solution ASAP!
Thanks in advance. Any help is very appreciated!!
Click to expand...
Click to collapse
I think you would have to reflash, sorry . You should:
1.) Delete cache
2.) Delete dalvik cache
3.) Delete data/factory reset
4.) Flash new ROM
5.) Flash GApps (if not included in the ROM).
You might be able to salvage some data back by going into download mode, but I'm not to knowledgeable in that area. Good luck.
If you flash over your current rom with same rom you will still have your apps and data. All a dirty flash does is install new system apps from the rom itself so your data should not be effected.
Sent from my SGH-T989 using Tapatalk
Still wont boot
richardlibeau said:
If you flash over your current rom with same rom you will still have your apps and data. All a dirty flash does is install new system apps from the rom itself so your data should not be effected.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ok, I thought I remembered hearing that. I just reflashed the ROM over the old one without clearing any caches. Unfortunately the phone still gets stuck at the Samsung S boot screen. The animation continues and it does not appear frozen but it never goes anywhere.
I am thinking of wiping the system/factory reset then reinstall the ROM. before I do that though, is there any way to copy over files from the system partition before flash and then copy them back overwriting the current ones after flashing the ROM. Will this work since it is the same ROM? I dont care if its stable. Just want to recoup my data and backup and then I will completely redo the ROM again.
Thanks for your input guys!
Restore a backup
----------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm full of great idea's, but don't have the time to create them or learn the coding to create them. If you want to make one of my ideas a reality just message me and I will give you my idea as specific as possible.
ideas:
-launcher/lock screen
-line rider type game where you control the character
-2d fighting game like art of fighting for the SNES
-multiplayer fps where you create your own map with a creative mode (minecraft style)
-roller coaster tycoon style game
-many more!
Just message me which idea you want info on and I'll tell you!
----------------------------------------------
DirtyBreakz said:
Ok, I thought I remembered hearing that. I just reflashed the ROM over the old one without clearing any caches. Unfortunately the phone still gets stuck at the Samsung S boot screen. The animation continues and it does not appear frozen but it never goes anywhere.
I am thinking of wiping the system/factory reset then reinstall the ROM. before I do that though, is there any way to copy over files from the system partition before flash and then copy them back overwriting the current ones after flashing the ROM. Will this work since it is the same ROM? I dont care if its stable. Just want to recoup my data and backup and then I will completely redo the ROM again.
Thanks for your input guys!
Click to expand...
Click to collapse
Do a full back up now then wipe the whole phone, Flash new rom then boot into recovery and go to advanced restore and you can just restore system or data instead of the whole back up. But it sounds like your problem is in your system somewhere though since it is not booting all the way. Do you have scripts that clash? Tweaks etc. Try flashing a new kernel and see if it boots up.
richardlibeau said:
Do a full back up now then wipe the whole phone, Flash new rom then boot into recovery and go to advanced restore and you can just restore system or data instead of the whole back up. But it sounds like your problem is in your system somewhere though since it is not booting all the way. Do you have scripts that clash? Tweaks etc. Try flashing a new kernel and see if it boots up.
Click to expand...
Click to collapse
Ok. I flashed the same rom over top of the current one and got the same results. I then booted into recovery, wiped system, flashed the rom again and got the same results.
One thing I noticed is that when I ran fix permissions both before I reflashed and after, it was super quick to finish lasting only a couple seconds where normally it takes a couple minutes for fix permissions.
I did a backup in TWRP right after the crash. I will try flashing a kernal as a last attempt before doing a full wipe and flash. I have to find which kernel it is. Do you recommend flashing the same kernel or a specific kernel?
DirtyBreakz said:
Ok. I flashed the same rom over top of the current one and got the same results. I then booted into recovery, wiped system, flashed the rom again and got the same results.
One thing I noticed is that when I ran fix permissions both before I reflashed and after, it was super quick to finish lasting only a couple seconds where normally it takes a couple minutes for fix permissions.
I did a backup in TWRP right after the crash. I will try flashing a kernal as a last attempt before doing a full wipe and flash. I have to find which kernel it is. Do you recommend flashing the same kernel or a specific kernel?
Click to expand...
Click to collapse
What rom and os are you on ics or jb? Same kernel is ok but a new one might be better
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
What rom and os are you on ics or jb? Same kernel is ok but a new one might be better
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I'm running Jedi Mind Trick x4 (JMTx4) ICS with its kernel. It looks like it uses Faux kernel. Not sure where to get it or one that will work. I was just looking through the thread here and also googled it but didnt get much. I went to the Faux repository but it was a bit confusing. I have never downloaded or flashed a separate kernel. Always just used the one packaged with the rom. Please direct me to a link to place to download the kernels that I could use with this rom.
DirtyBreakz said:
I'm running Jedi Mind Trick x4 (JMTx4) ICS with its kernel. It looks like it uses Faux kernel. Not sure where to get it or one that will work. I was just looking through the thread here and also googled it but didnt get much. I went to the Faux repository but it was a bit confusing. I have never downloaded or flashed a separate kernel. Always just used the one packaged with the rom. Please direct me to a link to place to download the kernels that I could use with this rom.
Click to expand...
Click to collapse
Any of these will work. I can't find faux right now. Just flash and reboot.
richardlibeau said:
Any of these will work. I can't find faux right now. Just flash and reboot.
Click to expand...
Click to collapse
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.[/QU
Corruption is usually in the system somewhere so that's odd. Hopefully one of the kernels will help you.
Click to expand...
Click to collapse
richardlibeau said:
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.[/QU
Corruption is usually in the system somewhere so that's odd. Hopefully one of the kernels will help you.
Click to expand...
Click to collapse
Ok. I restored data again and confirmed no boot, then flashed the new kernel and still no joy
Looks like something is corrupted in the data. Do you know of anything else I can try before fully wiping/reflashing again?
Click to expand...
Click to collapse
Not at this point sorry. Seems that something really weird. Best just to reflash now and be glad it's not fully bricked.
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
Not at this point sorry. Seems that something really weird. Best just to reflash now and be glad it's not fully bricked.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Right on! Thanks again for all the advice. Just a quick question before I am off to reflash again...
Is it possible to recover any information from the data in the twrp backup once I have reflashed? Mainly looking for text notes from Note Everything and SMS messages.
If it's a tar file you can through a file explorer that can open tar files like winrar, winzip. etc. You just extract what you want. So yes you can salvage things that way.
Sent from my SGH-T989 using Tapatalk
file and data recovery
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.
Click to expand...
Click to collapse
I know I'm about two weeks after this one, but here are some thoughts on accessing the data in the backup.
My arsenal includes Root Explorer, FX Explorer by nextapp (File Explorer is the name that shows up in google play), ROM Manager, and Titanium Backup.
I do not use Root Explorer nearly as much as I use FX. To me, FX is easier to use, runs in the background, and can run multiple operations at the same time.
FX Explorer can extract .tar files so you can pull individual files from the archive, but it extracts the entire contents of the archive. FX Explorer can also mount read/write of the /system if the phone is rooted. You will get a little nag screen every time you mount r/w, but that's about it.
Yes, it's worth paying the couple of bucks in Google Play for the full versions of these apps. The only caveat with FX Explorer is that in order to get FULL app functionality, you have to install it in modules. I think there are a total of 4, maybe 5 modules for the app. The main app which is free, the root module which is NOW free, there is a paid module for media, and a paid module for network functionality which includes hosting a file server on the phone as well as accessing Google Drive, skydrive, and other cloud based storage solutions.
Titanium Backup can also pull individual app apk's out of a Clockwork Nand backup, but it will miss /lib files that some apps like swype need.
FYI, I just installed JMTX4 for my T989, and wanted the Swype from the stock rom. Turns out, installing JUST the swype apk out of the backup wasn't enough. Using FX, I extracted the system .tar portion of the backup, and extracted the two files I needed, including the swype apk, and using FX, I pasted them into the /system/app and /system/lib directories as the link I found said to do, only I did it directly on the phone without having to use the adb interface from my pc.
Not to revive an old thread but I wanted to update so others may be able to use the info.
Found out that the reason for the crashes was a hardware (power button) issue. The power button would get stuck in several different positions causing the phone to reboot or boot loop and not boot at all. T-mo was nice enough to replace my phone out of warranty for me after a little haggling so no more issues
I have since updated and running Jedi Mind Trick JBv4 now. I actually think I like JMTv4 better. It runs great. I'm just not entirely fond of some of the new Android changes in JB.
DirtyBreakz said:
Not to revive an old thread but I wanted to update so others may be able to use the info.
Found out that the reason for the crashes was a hardware (power button) issue. The power button would get stuck in several different positions causing the phone to reboot or boot loop and not boot at all. T-mo was nice enough to replace my phone out of warranty for me after a little haggling so no more issues
I have since updated and running Jedi Mind Trick JBv4 now. I actually think I like JMTv4 better. It runs great. I'm just not entirely fond of some of the new Android changes in JB.
Click to expand...
Click to collapse
my phone is doing the same thing. what did you say to tmobile?
adamwithane said:
my phone is doing the same thing. what did you say to tmobile?
Click to expand...
Click to collapse
Call tech support and tell them you are having problems with your power button. Hopefully you will get a helpful rep. If not, call back and try again. If you are in warranty it should be no issue.