Develop Bugs

Upgrading to GB

Hi all,
I really hope someone can help and I am sorry if I am being an idiot on this but a while ago, I rooted my HTC Desire HD and installed the LeeDroid rom, from this site.
I have had this for a while now and have just decided to upgrade it to Gingerbread so I can install some of the latest rom sets but every time I try to upgrade I get issues:
Downloaded the update via the phone. When it runs and tries to install, it just comes up with a triangle, with an exclamation mark in it and the droid icon next to it. It never gets further than that.
I have grabbed the relevant file from the htc developers site and ran that but it came up saying that it could not update the rom file and to download the right one (triple checked this)
I have done a complete factory reset , so the phone is as was originally.
Has anyone got any idea how I actually get my phone to android 2.3?????
Been out of the phone hack scene for well over a year now so treat me as a newbie if needed lol
I'm pulling my hair out now. Could it be something in the LeeDroid rom set that is causing this?
Thanks in advance to anyone that can help

Shouldnt you get thr gingerbread update from settings>about phone?
Sent from my Desire HD using XDA App

If your rooted let alone running a custom rom you cannot install an ota. If you want gb you can either flash an ruu or my recommendation install a new custom rom

Well eventually tried to install the latest LeeDroid Rom set, which I believed would have gingerbread already packed in to it but it just came up with Installation Aborted all the time.
After many factory resets, my Desire HD now won't boot past the HTC screen at all. I've tried everything but nothing gets me past that point.
Any ideas on this issue or is my phone well and truly bricked now???

Are you able to go into recovery from hboot?
If yes simply download a rom and reflash. Maybe it was a bad download the first time. Or if you have a backup made do that.
If you have no recovery you can flash an ruu or pd98 file from hboot. I made a guide for this just search for threads I've started

Yes I can boot in to recovery but I have a mini SD card in the phone, so I assume I need to get that attached to my pc somehow and pop another rom on it and run install from clockwork yeah?
If that's the case, I have to seriously find the standard SD car adapter from somewhere.
I'll report back later as I have to go out now for the day. Appreciate your patience on this mate.

No need for an adapter. Should have mention this before. Within cwr you have a setting to mount the SD card.(mounts and storage). So you mount it, transfer rom, unmount,then full wipe,maybe also format system,cache dalvik, and flash rom

Exactly what marsdta said. Boot into recovery, but download a rom before that and place it into root of your SD card. From recovery wipe data and cache, select install zip from SD card and off ya go. Initial boot after flashing ANY rim may take 5 or 6 minutes so bear with it. Everything you need to know about proper flashing can be found here, just look.
Sent from my Desire HD using XDA App

OK happy to be looked at as stupid here but how can I transfer a rom to my SD card when it's in a phone that won't boot up????
I assumed I would need to put it in to an SD card adapter and then pop in to my computer.
Are you saying that, once I mounted the sd card in CWR, my computer should see it, even though the phone won't boot???

Correct. Once you mount it in cwr your PC will be able to see it

OK I downloaded, what I considered to be a Stock rom for the HTC Ace, which is also the desire, copied to sd card and then tried to install. This is what I got:
Installing /sdcard/RUU_Ace_Gingerbread_S_HTC etc etc etc.zip
Finding Update Package...
Opening Update Package...
E:Can't open /sdcard/RUU_Ace_Gingerbread_S_HTC etc etc etc.zip (Bad)
Installation Aborted.
Honestly, I thin kI need a direct link to a ROM that should work. :-(

From the looks of it your trying to install a ruu zip from recovery which you can't do. Those are flashed through hboot.(must be named PD98IMG)
if you want the stock feel but without the bloat and better optimized I would say to try cleardroid.

Sent from my HTC Desire HD with Beats Audio using XDA App

OK Popped PD98IMG on to my SD Card and booted to CWR and it automatically picked up on it. It tested the image file for a while, then said loading and then, after about 4 minutes, it went back to the recovery screen.
What now?
Everything I seem to be throwing at this phone either says bad image or Installation Aborted

did you read my last comment? You can't flash a pd98 from cwr.
If you want to go the pd98 route you need to place the file in the root of your SD card.(not in a folder) boot into HBOOT. it will scan and ask to lad it press up to accept

If you're being a **** then you're being a helpful one.
Read my last post too. It's what it did. It scanned the P98 image and then said loading but I got no prompt to accept anything. It quickly says parsing P98IMG then it just goes back to the recovery screen.
I'm only going down the P98 route because that's what a lot of forum threads say is best to do, if you're having issues like mine.
I will try to find the cleardroid one you mentioned and see if that works

You said cwr in your post. That's why I said what I said.
When it fails to parse it could be two things the download was bad or your SD card is acting up. You could try to redownload the pd98 and try again
Just to clarify. Hboot is the white background.
{
"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"
}
Cwr is with black background.
Are you able to enter cwr? Or just hboot

Yes can enter both. White screen to start with and then the black one when I hit recovery.
Would it be a benefit for me to format the SD card via CWR screen and pop the image back on there?

Ok just wanted to make sure we were on the same page as hboot and cwr are not interchangeable.
I was going to suggest that too but you beat me to the punch. Reformat then try the pd98.
I would try a custom rom. But that's just my preference. I forgot what XDA section I was in. Cleardroid is an inspire rom not sure if it will work for.dhd. you van try android recvolution seems to be a popular one. I'm more of a cm fan, so.you can try that if you so.choose

OK I think I will end today, for me at least with a simple question:
Can you recommend a custom ROM that will take me up to gingerbread at least or do I have to do something different to get me there, as I think the LeeDroid one I have is Froyo?
Sorry, wrote this after you had responded

[Q] Flash nightmares and figuring out the aftermath

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

[Q] PLEASE HELP!! Work phone w/ JMTx4 stuck at Samsung logo after battery died

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.

[Q] Soft Bricked? GS3 Sprint

So I had to create account just to post my problem before taking any drastic measures. I have been on the XDA forums for a while and I'm not a complete n00b(disclaimer here) when it comes to rooting and ROMing but I done messed up.
So I had this ROM installed which was being a little finicky with the screen. It would flash randomly when either texting or in Facebook. Mostly when the keyboard was up(swiftkey 3). Anyways, I had no real expertise in flashing Kernels so I thought a would give that a try to see if that might help anything.
Went into the forums about intalling custom kernels and came across this thread.
Followed ChaseBroyles steps that he gave, the exact method( this may where I have messed up) then I reboot, it shows the SAMSUNG logo but then turns its self off. So I try to go into recovery, shows at the top Recovery Booting, then shows Samsung Galaxy SIII logo then turns its self off.
So the next logical step is to go into Download mode. It boots into download just fine, then I try to get it to connect to the computer. Tried all of my USB ports and all the cables that I have for Micro USB, still nothing. Odin wont detect it and neither will my computer. I tried removing the battery and letting it sit for a while, and that didn't work either.
So all the help will be apprecited, I do have a jtag but not available to me til this weekend sadly. If that is what I need to do, I'll try that but if I can get it fixed today or sometime this week it would be most appreciated!

Korumaru said:
So I had to create account just to post my problem before taking any drastic measures. I have been on the XDA forums for a while and I'm not a complete n00b(disclaimer here) when it comes to rooting and ROMing but I done messed up.
So I had this ROM installed which was being a little finicky with the screen. It would flash randomly when either texting or in Facebook. Mostly when the keyboard was up(swiftkey 3). Anyways, I had no real expertise in flashing Kernels so I thought a would give that a try to see if that might help anything.
Went into the forums about intalling custom kernels and came across this thread.
Followed ChaseBroyles steps that he gave, the exact method( this may where I have messed up) then I reboot, it shows the SAMSUNG logo but then turns its self off. So I try to go into recovery, shows at the top Recovery Booting, then shows Samsung Galaxy SIII logo then turns its self off.
So the next logical step is to go into Download mode. It boots into download just fine, then I try to get it to connect to the computer. Tried all of my USB ports and all the cables that I have for Micro USB, still nothing. Odin wont detect it and neither will my computer. I tried removing the battery and letting it sit for a while, and that didn't work either.
So all the help will be apprecited, I do have a jtag but not available to me til this weekend sadly. If that is what I need to do, I'll try that but if I can get it fixed today or sometime this week it would be most appreciated!
Click to expand...
Click to collapse
Let me make a summary and you can correct me if I'm wrong:
You had a rooted phone with a custom Rom (JellyBam) and a custom Recovery (CWM or TWRP). Please clarify which Recovery you had (and version, if you remember it). Also, please clarify which version of JellyBam you had installed (latest is 7.6.2).
You decided to flash a new Kernel, thinking it'd help with the random screen flickers. Please clarify which Kernel you flashed.
Now when you try to boot into the Rom, you get stuck in a bootloop (phone doesn't progress past or turns off at the Samsung Logo).
When you boot into Recovery Mode, it gets to the recovery loading screen then turns off.
Download mode works fine, but your computer doesn't recognize it.
You have a JIG.
So it sounds like you flashed a Kernel which was not meant for your Rom. JellyBam is a 4.2.2 Rom, but there are two types of kernels for 4.2.X Roms: those based off of Linux 3.0 and those based on Linux 3.4. After a little searching, I couldn't find which version JellyBam is using, but if it's based off of 3.0 and you flashed a 3.4 Kernel, it'll give you a bootloop. It doesn't exactly explain why your recovery got messed up, but others have had their recovery partition borked by a bad kernel flash, so it's not out of the realm of possibility. Tis is why I want to know which version of JellyBam you had and which kernel you flashed. This will help us know how to help you.
Ok, so your phone is not beyond repair. I'm a little disconcerted that you cannot boot into Recovery, but that happens every once in a while when flashing, so it's not the worst thing to happen. You can, however, boot up into download mode. This is very good. Make sure you have the latest Samsung drivers on your computer and that you don't have Kies installed (Kies has been known to interfere with Odin). See if that works to get Odin to recognize the phone.
If the above works, all you have to do is follow the rooting guide to get a custom recovery back.

Okay so you followed instructions on how to flash a kernel but what kernel did you flash? I think you flashed a kernel for the gsm variant which is completely different than the Sprint kernels. Well if you flashed the kernel he recommended you flashed kt747 Koontz kernel. Which is correct but did you download the correct one? There is one for Touchwiz one for AOSP and there are several for AOSP depending on the romantic and build date. So if you can provide this info it should be easy, but quick way to fix your problem is to just refresh your room right now.
Edit: hats off to Topherk beat me to it...
Transmitted with a portable device using Xparent Blue Tapatalk 2

topherk said:
Let me make a summary and you can correct me if I'm wrong:
You had a rooted phone with a custom Rom (JellyBam) and a custom Recovery (CWM or TWRP). Please clarify which Recovery you had (and version, if you remember it). Also, please clarify which version of JellyBam you had installed (latest is 7.6.2).
You decided to flash a new Kernel, thinking it'd help with the random screen flickers. Please clarify which Kernel you flashed.
Now when you try to boot into the Rom, you get stuck in a bootloop (phone doesn't progress past or turns off at the Samsung Logo).
When you boot into Recovery Mode, it gets to the recovery loading screen then turns off.
Download mode works fine, but your computer doesn't recognize it.
You have a JIG.
So it sounds like you flashed a Kernel which was not meant for your Rom. JellyBam is a 4.2.2 Rom, but there are two types of kernels for 4.2.X Roms: those based off of Linux 3.0 and those based on Linux 3.4. After a little searching, I couldn't find which version JellyBam is using, but if it's based off of 3.0 and you flashed a 3.4 Kernel, it'll give you a bootloop. It doesn't exactly explain why your recovery got messed up, but others have had their recovery partition borked by a bad kernel flash, so it's not out of the realm of possibility. Tis is why I want to know which version of JellyBam you had and which kernel you flashed. This will help us know how to help you.
Ok, so your phone is not beyond repair. I'm a little disconcerted that you cannot boot into Recovery, but that happens every once in a while when flashing, so it's not the worst thing to happen. You can, however, boot up into download mode. This is very good. Make sure you have the latest Samsung drivers on your computer and that you don't have Kies installed (Kies has been known to interfere with Odin). See if that works to get Odin to recognize the phone.
If the above works, all you have to do is follow the rooting guide to get a custom recovery back.
Click to expand...
Click to collapse
To answer your questions in order:
1) I had CWM v 5.x.x I cannot remember correctly. It is the one Zedo max gives in his tutorial. And for Jellybam, I had the latest stable build that was released from their website which is 7.6.2
2) I used this Kernel (http://forum.xda-developers.com/showthread.php?t=1800576) from the thread I stated, another user provided it.
3) Yes that is correct
4) Yes
5) Yes again
6) Yes that is what it is called, bought cause of something dumb I did months ago.
I thank you for the info, it is really appreciated.
So I just updated my Samsung drivers(forgot to do it when I reformatted) and that worked! Odin recognized it and now I'm on the road to recovery!
Thank you so much for my help
So for future reference, what kernel should I install with that ROM just so I don't **** crap up this time?

I wasn't able to find it in the jellybam forums with a brief search, but you could ask over there to see if they can tell you. Also, there are two types of 3.4 kernels, one built before 4/19 and those after 4/19. Make sure you're using the court one.
Hope you can figure it out, and please post back here if you can find it!
Sent from my SPH-L710 using xda app-developers app

I think I might have found a reference to what kernel you're you need to flash: http://www.bam-android.com/forum/showthread.php?3443-Fix-For-D2SPR-7-0-Screen-Issue. From the link, it seems like JellyBam uses 3.0 kernel.
On a separate note. This post might give you direction on fixing the screen flicker issue.
Hope this helps!
Sent from my SPH-L710 using xda app-developers app

Oh, I'm a dolt! You can check your version by going to settings ---> About phone. The kennel version box tells you what version it's running. Look arty mine (from LiquidSmooth):
{
"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"
}
Sent from my SPH-L710 using xda app-developers app

[Q] Losing root on deknoxed debloated stock 4.4

My phone has lost root twice now. It acted very strange when this happened. Hopefully you guys can help.
I'm on the stock kitkat 4.4.2 that I personally deknoxed and debloated. I have xposed framework and just a couple modules installed for it (gravity box, app settings, and keepchat) Everything is the same as it was on my phone when I had 4.3 app wise.
The first symptom I notice is that tapping the power button wont make the screen go to sleep. Holding it still brings up the power menu.
The first time it did this it also wouldnt connect to wifi and ate battery like crazy.
Used the flash zip to disable xposed and dirty flashed the rom. This fixed the wifi but not the power button.
Ended up totally flashing back to stock 4.4.2 with Odin and redoing everything. Downloaded pretty much all the apps from the app store and only used titanium backup to restore data on a couple things.
Everything worked fine ~3 weeks. Today it stopped working again. All the same symptoms. Absolutely nothing was changed between when it was working and when it stopped. All I did was reboot because I wanted to run speedtest from a clean boot. (comparing sprint 4G with verizon 4G at a friends)
Went to disable xposed straight from the app and it said it couldnt because I didnt have root. Downloaded rootchecker and it agreed that I did not have root.
Suddenly it started working again. Passed root checker and all. Then a couple minutes later it stopped again.
Downloaded towelroot and re-rooted with it. Everything seems to be back to normal for now.
Any ideas? Theories? Investigative follow up questions?

thedumbass said:
My phone has lost root twice now. It acted very strange when this happened. Hopefully you guys can help.
I'm on the stock kitkat 4.4.2 that I personally deknoxed and debloated. I have xposed framework and just a couple modules installed for it (gravity box, app settings, and keepchat) Everything is the same as it was on my phone when I had 4.3 app wise.
The first symptom I notice is that tapping the power button wont make the screen go to sleep. Holding it still brings up the power menu.
The first time it did this it also wouldnt connect to wifi and ate battery like crazy.
Used the flash zip to disable xposed and dirty flashed the rom. This fixed the wifi but not the power button.
Ended up totally flashing back to stock 4.4.2 with Odin and redoing everything. Downloaded pretty much all the apps from the app store and only used titanium backup to restore data on a couple things.
Everything worked fine ~3 weeks. Today it stopped working again. All the same symptoms. Absolutely nothing was changed between when it was working and when it stopped. All I did was reboot because I wanted to run speedtest from a clean boot. (comparing sprint 4G with verizon 4G at a friends)
Went to disable xposed straight from the app and it said it couldnt because I didnt have root. Downloaded rootchecker and it agreed that I did not have root.
Suddenly it started working again. Passed root checker and all. Then a couple minutes later it stopped again.
Downloaded towelroot and re-rooted with it. Everything seems to be back to normal for now.
Any ideas? Theories? Investigative follow up questions?
Click to expand...
Click to collapse
for some reason that happens to me when I'm on stock not on any other custom rom but when i clean flash a new rom everything is fine but if i Odin back to stock or flash one of the stock rooted via recovery i lose root a lot and when i re-root with Philz touch recovery i cant update the su binary with super su so i cant help you minus the flash a different rom answer I'm sorry :/

Not the answer I want to hear. But it is an answer and its appreciated.
By custom are you meaning stock based custom or full custom/AOSP based?
I know there are some stable custom roms out there but I like the general stability of stock especially since I still need to update my girlfriend's phone. She needs something that works all the time and a reboot will fix 99.9% of the issues she might see.
Our S3s are both ported to Ting. Hers is rooted mainly for the debloat and easy backup/recovery abilities. I told her until I knew mine was stable to just stay on 4.3 and ignore the update notification. She's had zero issues and I've had this one plus the external SD write crap. I'm definitely the nerd of the two of us and getting into flashing custom roms would be too much for her.
This might end up pushing me to something custom. If I do I'll just leave her behind at 4.3 and kill her update notifications permanently.

thedumbass said:
Not the answer I want to hear. But it is an answer and its appreciated.
By custom are you meaning stock based custom or full custom/AOSP based?
I know there are some stable custom roms out there but I like the general stability of stock especially since I still need to update my girlfriend's phone. She needs something that works all the time and a reboot will fix 99.9% of the issues she might see.
Our S3s are both ported to Ting. Hers is rooted mainly for the debloat and easy backup/recovery abilities. I told her until I knew mine was stable to just stay on 4.3 and ignore the update notification. She's had zero issues and I've had this one plus the external SD write crap. I'm definitely the nerd of the two of us and getting into flashing custom roms would be too much for her.
This might end up pushing me to something custom. If I do I'll just leave her behind at 4.3 and kill her update notifications permanently.
Click to expand...
Click to collapse
damn well i meant custom touchwiz and custom ASOP

And now it's deleting system apps. Wtf. My alarm clock and calculator are gone. I sure didn't delete them. Titanium backup list most of the clock stuff as crossed out.

thedumbass said:
And now it's deleting system apps. Wtf. My alarm clock and calculator are gone. I sure didn't delete them. Titanium backup list most of the clock stuff as crossed out.
Click to expand...
Click to collapse
that's strange what rom? and how long have you been using it i will do the research

Still stock ND8 deknoxed. I froze the bloat rather than deleting. I haven't had a chance to flash anything new since starting this thread.
Starting to wonder if my nand is shot... I couldn't find any apps that would do an integrity check on the nand.

Hi
thedumbass said:
Still stock ND8 deknoxed. I froze the bloat rather than deleting. I haven't had a chance to flash anything new since starting this thread.
Starting to wonder if my nand is shot... I couldn't find any apps that would do an integrity check on the nand.
Click to expand...
Click to collapse
Start ultra fresh:
1. Backup anything you absolutely must including from the internal storage.
2. Take the SD card out and leave it out.
3. Download is necessary and check the MD5 hash of the zip or tar of the stock ND8 tar. The hashes are somewhere in that thread, just search it for MD5.
4. Odin the stock ND8 tar.
5. Odin the very latest Philz Touch Recovery tar.md5.
6. In Philz's settings, use the re-root option.
7. Don't restore any data via Titanium Backup or other app. Only restore apps via the Play Store.
8. Observe if all weirdness has gone away.
9. If so, backup what you want from your SD card, reformat it and if you want flash a different ROM. Check the hash of anything you flash, especially ROMs and kernels.
10. Do not restore any Nandroids.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"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"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Just as a quick update bump.
I haven't had a chance to sit and do a proper wipe and flash from scratch. After I missed an appointment due to missing alarm clock I dirty flashed the rebooted nd8. This hit my clock calender and calculator back. Then I had to remove knox and bloat again.
My phone has locked the power button and WiFi a few times since. Running towel root seems to fix it though the towel root app freezes and has to be force closed.
I have noticed what seems to trigger it to screw up is letting the battery run dead to the point it auto offs. Just powering it off/rebooting or pulling the battery doesn't cause it though.
Do plan to wipe it clean soon. Between work and home I haven't had time.

thedumbass said:
And now it's deleting system apps. Wtf. My alarm clock and calculator are gone. I sure didn't delete them. Titanium backup list most of the clock stuff as crossed out.
Click to expand...
Click to collapse
I had the same thing happen to me. I *think* it had something to do with my debloating. Correct me if I'm wrong, but it think that many apps use the same processes. Deleting an app might delete processes needed by another app?
When using tibu, I've made it a habit to go slow. Wipe cache before I delete anything. Make a backup of any app I'm going to remove (after deleting data on that app). Only removing a few apps at a time, and making note if which apps I've removed.
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2