Database Info

Wifi Tether (any fixes)?

I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.

fatkitty420 said:
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
Click to expand...
Click to collapse
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.

thecodemonk said:
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
Click to expand...
Click to collapse
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.

fatkitty420 said:
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
Click to expand...
Click to collapse
No sweat! If you look at my join date and postcount, you can see I'm not exactly the veteran around here either.
The MoDaCo ROM doesn't modify very much yet...just adds functionality (it's not the heavily optimized kernel that the GSM users have for example). I'm finding it fairly stable...there's a few quirks but those have fixes pretty easily found so far.
I can still purchase from the market...the stuff you purchased already is tied to your google account, not your phone. I bought Docs2Go before I rooted and flashed and I was able to redownload and install without any hassle or added cost.
On a custom ROM, future updates do depend on the person who is building the ROM. However, MoDaCo has proven pretty reliable thus far in keeping up with releases so it's a bit of a trust thing, do you trust MoDaCo to continue that trend or would you rather place your trust in the manufacturer? (It's a preference thing and willingness to risk either way).
The upside is that once you root to a recovery image (Not even changing your OS), you can take a Nandroid backup of your phone, which is an image you can drop back on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.

thecodemonk said:
k on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
Click to expand...
Click to collapse
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?

fatkitty420 said:
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
Click to expand...
Click to collapse
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)

thecodemonk said:
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
Click to expand...
Click to collapse
Great, this really clarified things.
I love technology but, like most of these things, it's very overwhelming at first.

[Q] Comprehensive Tutorial on switching to GB / CM7

I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!

You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod

Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App

You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.

So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.

OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.

really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.

So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?

Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.

Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.

NVIDIA-was trying to Root from 2.3.3 and chose "Flash Stock Recover!"

Hello,
First post, and greetings.
After following TGA_Gunnman's steps in order to Root from 2.3.3, I
chose "Flash Stock Recover" (the third one) instead of the middle one.
Now all my apps and contacts are gone. Am I pretty much screwed?
My wife just fell asleep and this is her phone so I dead meat if I can't
restore it.
I'm thinking I wiped all the existing internal data since I selected the option
that is only used if I'm "returning to T-mo." All the SD card pics seem to be
though (thank God).
Is there a way to restore though if I've never backed up with NVIDIA?
I'm now proceeding to normal root options and will report how that goes.
Thank you in advance.

Unless you did a backup there would be no way to undo it. If you synced your Google account you could get it back via google
Sent from my LG-P999 using XDA App

First, you used nvflash to install recovery, not Nvidia ... that's the name of a company. Second, flashing stock recovery wouldnt have deleted that info. However, if after flashing stock recovery you attempted to boot into recovery by holding volume down + power, then it WOULD most definitely delete that info. Here's how it works:
-- With stock recovery (which is what u flashed) holding volume down + power performs a factory reset. A factory reset deletes all user-installed apps and user settings. System apps and anything on your sdcard are left intact and not deleted.
-- With clockworkmod recovery (what you intended to flash) holding volume down + power boots into recovery where you can make backups, flash roms, etc.
The good news is you didn't cause any permanent damage or lose anything you can't replace. You'll just have to download apps and change the settings back to the way she wants them.
If you still want to root. Use the nvflash tool again and install clickworkmod recovery. Then flash the root zip that jboxer posted in the development section.
Sent from my LG-P999 using XDA App

Should warned everyone I'm a total noob too
Ultimately, was able to root and think I'm going to like
the benfits. All pics were still on sd card so lucked out there
atleast.

[Q] Information about ADB manual backups

Hey guys,
I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.
The phone is unlocked and rooted, running the stock Android 4.2.1.
I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.
I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.
I'm right now trying to copy /data into my computer. Is it of any use?
Is there anything else that I can backup before sending the phone out?
Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc
Thanks in advance!

igorsantos07 said:
Hey guys,
I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.
The phone is unlocked and rooted, running the stock Android 4.2.1.
I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.
I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.
I'm right now trying to copy /data into my computer. Is it of any use?
Is there anything else that I can backup before sending the phone out?
Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc
Thanks in advance!
Click to expand...
Click to collapse
since the phone itself still works, and the unresponsive screen is the only issue, you might be able to make a nandroid backup (complete backup of everything on phone-apps, settings, etc.)
I assume you probably have a touch based recovery on your phone like twrp or cwm touch. This is obviously an issue.
To counter this you could try using fastboot to flash clockworkmod non touch recovery. This allows you to use the volume rockers and power button to navigate.
To flash the recovery install all the correct drivers, and download the non touch cwm and place it your fastboot directory. Then boot the phone into the bootloader, and use this command:
Code:
fastboot flash recovery "name of recovery file.img"
Then from there you can boot into recovery, go to backup and restore, and finally make a nandroid backup. From there you could copy the backup using adb onto your computer. (the backups are stored in sdcard/clockworkmod/backups)

Thanks! I'll try that.
I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).
And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?
Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?
On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.

igorsantos07 said:
Thanks! I'll try that.
I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).
And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?
Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?
On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.
Click to expand...
Click to collapse
Yep once you get the phone fixed/replaced, you may need to reflash cwm and copy the backup back onto the phone (if they wiped it)
Then just use the restore option in cwm.
If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.

chromium96 said:
If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.
Click to expand...
Click to collapse
Boo =(
Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?
I should just take care on not backing up system stuff, right?

igorsantos07 said:
Boo =(
Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?
I should just take care on not backing up system stuff, right?
Click to expand...
Click to collapse
Yep thats probably your best bet. Although I would avoid backing up/restoring system stuff with TB as it causes lots of bugs.
Just use TB to backup apps+app data, and you can restore them after installing PA. There shouldnt be any problems

Need Help

I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."

Justintoxicated said:
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Click to expand...
Click to collapse
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.

dottat said:
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
Click to expand...
Click to collapse
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.

Justintoxicated said:
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Click to expand...
Click to collapse
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.

dottat said:
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
Click to expand...
Click to collapse
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though. I did not install lolipop because I need to get the phone to USB mode to copy it over, which I cannot do because it will not start up.

Justintoxicated said:
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though.
Click to expand...
Click to collapse
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?

dottat said:
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
Click to expand...
Click to collapse
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
TWRP is now version 2.8.5.0, so apparently it updated correctly (I think before it was 2.8.1)

Justintoxicated said:
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
Click to expand...
Click to collapse
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.

dottat said:
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
Click to expand...
Click to collapse
Ok my internet is not working on my laptop at work (only of the PC I'm on and no way to transfer files without my phone), so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.

Justintoxicated said:
Ok my internet is not working on my laptop at work, so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Click to expand...
Click to collapse
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.

dottat said:
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
Click to expand...
Click to collapse
Update, restarted the computer and I was able to restore the old firmware. I re-installed the old rom afterwards (not my nandroid) and I am unable to get into the OS. Well technically I get prompted to select a language, after which the phone reboots back to the S-off androids with skateboards bootloader. Does this mean my phone is toast?

Hey guys, should I S-on the phone load the stock bootloader and try to return it? It is over a year old so I think I will need to use my insurance ($100). What is the best way to go about doing this?
Also when I get my replacement phone will there still be a way to S-off?
Thanks,
- Jusitn

The problem appears to be something wrong with my micro SD card! I removed the micro SD card and I can boot up fine. I guess I need to find another way to copy the rom to the micro SD install the rom then remove the micro SD card.
edit:
Oh this is worse than paying $100 for a new phone. It appears that creating a backup instead of creating a backup, actually corrupted my memory card. Now all the photos are backed up to the cloud but it will take me hours and hours to get all my apps back to the way they were. Some Security camera settings, Rifle target hand load development all gone. Audio book place holders, all notes taken etc. Nothing life or death but those security cameras will take me forever to figure out. I know I know, why not create a backup right? Well that's what I was trying to do!

So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?

Justintoxicated said:
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Click to expand...
Click to collapse
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.

robocuff said:
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
Click to expand...
Click to collapse
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.

Justintoxicated said:
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Click to expand...
Click to collapse
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.

dottat said:
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
Click to expand...
Click to collapse
I don't remember, probably missing a file or something.