Related
Looking for help/suggestions.
I have 2 aria that developed random reboot for no apparent reason...
My work aria was rooted and s-off running cm7.1 for about a month with no issues, I've flashed kang cm7.2 and all seemed ok, but the next morning the phone was dead (it was at 50% before going to sleep). charged it in the morning (the battery was 0%), came to work and while it was on my desk the phone rebooted and continued to do that through out the day. At home, i did factory reset, did not help. I've put it back to s-on and put back the stack ATT 2.2, same results, continues to re-boot at random intervals. Thinking it was hardware, got my job to get me a different phone.
3 weeks later, my wife's aria (rooted but still s-on) running cm7.1 started to run extremely slow and battery would drain in about 5 hours. I've done factory reset, clear everything and it still doing random re-boots just like my aria.
With one aria, I thought that it was a hardware issue, but now 2 arias, looks like os/software. Resetting/ re flashing does not help.
Any suggestions would be highly appreciated.
Are the devices overclocked?
Theonew said:
Are the devices overclocked?
Click to expand...
Click to collapse
yes, they both were overclocked, do not remember at what level, i think whatever the cm7.1 default was.... I did put them back to 600, which did not help.
Thank you
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
dimon2242 said:
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
Click to expand...
Click to collapse
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Did you try doing "format system" before doing a clean install? Also make sure you are using a recent version of Clockworkmod (5.x).
strykme said:
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Click to expand...
Click to collapse
You should touch your wife('s) more often
Sorry, couldn't resist
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
yar2 said:
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
Click to expand...
Click to collapse
yea i do
malware
wipe the phone , then check it out
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
yar2 said:
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
Click to expand...
Click to collapse
Can, because possible errors on the SD card
I still have not solved the random reboot issues. I have two Arias with the exact same problem. I think I somehow contaminated the 2nd phone by swaping SD cards and loading a Nandroid backup from the 1st phone. Both phones are rooted.
I have tried loading 4 roms -- Liberated, CM7.1 stable, CM7.2 RC and Menjeni's version of CM9 and have the exact same random reboot problem Seems like the phones works for anywhere from 5 minutes to over an hour and then reboot.
When I load the different ROMs I wipe everything -- the factory data reset, all the caches and re-formats that CWM offers. I also reformatted the SD card and reloaded CWM via Rom Manger in an effort to completely clean the phone. I also ran two a virus/malware scans on the phone and SD card -- which found no errors.
Is there something else I can do to further clean the phones? Since the same problem is with both phones, I seriously doubt its a hardware problem.
Anyone interested in purchasing 2 somewhat functioning Arias?
yar2 said:
I still have not solved the random reboot issues.
Click to expand...
Click to collapse
yar2, what HBOOT version do you have on the two devices?
HBOOT 6.02.1002
Thanks for trying to help me with this!
yar2 said:
HBOOT 6.02.1002
Thanks for trying to help me with this!
Click to expand...
Click to collapse
OK. I'm assuming you have an AT&T Aria. If not let me know.
Here's what I'd suggest you do. I'm basically trying the most extreme steps to correct the issue so we can verify if the issue is something that can be corrected or not.
1) Reformat your SD card(s) with SD Formatter 3.1. This tool sometimes fixes hard to detect problems that aren't corrected when formatting with other methods. (Default settings are fine.)
2) Run the AT&T 2.2.2 RUU to revert your phone to almost 100% stock. I say almost because the RUU will NOT change your HBOOT, which means even after doing this process, you will still have S-OFF.
3) Try using the phone with the stock unmodified ROM to see if you experience the random reboots you described. If you do, the rest of the steps are not necessary and it's probably a hardware issue.
4) Install CWM by putting your phone into FASTBOOT mode, then using the Android Flasher utility to install the latest version of Clockworkmod. Use this version: http://www.mediafire.com/?lg6b63aqpi1cvbg (source). If you know how to do this from command line with the fastboot command line tool, that is fine too.
5) Boot into CWM. Do factory reset/wipe data and format system partition. Then install the ROM of your choice. I'd suggest something like a recent version of CM7 since it is very stable. If using CM7, install 20110828 gapps immediately after flashing CM7. Reboot and see how it goes.
Even if you already downloaded any of the above files, delete them and download them again this time around (or check the md5 sums if you know how). It's possible the files were corrupted when you downloaded them before and that is why you keep having problems.
Also, as an aside: Are you using third-party batteries with your devices?
Aria random reboot
Thanks drumist for all you advice! When I did my last attempt at a clean install, I used a spare SD card that had never been in the phone.
Both phones are AT&T Arias with the original batteries. I liked the Aria size so much that I upgraded my wife's expired Iphone contract when AT&T was providing a free Aria upgrade just to have a spare in case I damaged one by rooting. Now I have managed to mess up both phones!
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Regardless, I will try what you suggest and let you know the results.
yar2 said:
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
Click to expand...
Click to collapse
Reverting the HBOOT to stock (and yes, returning to S-ON) has some risk -- i.e., if you make a mistake during the process, you can permanently brick the device, so I wouldn't recommend that except as a last resort. The RUU will reflash every other partition on your phone back to stock besides the HBOOT and is safe to do, so stick with that.
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Click to expand...
Click to collapse
Yeah, it's possible. If that is the case, though, the HBOOT wouldn't be the problem (because Nandroid backups do not touch the HBOOT). The RUU will reflash every partition that Nandroid touches.
If you already tried using a different SD card, then I wouldn't worry about using that SD Formatter tool.
Can't find a copy of the AT&T 2.2.2 RUU. They took it off the HTC website. The instructions there are for an OTA update, which I can't do since I'm not running the stock rom.
---------- Post added at 02:51 PM ---------- Previous post was at 02:12 PM ----------
Never mind. I found a copy of the RUU on my laptop.
I have installed the hboot drivers and the phone shows up as a device on my computer, but the RUU says it can't find my phone. I am running Windows 7, if that makes any difference.
Got the RUU to load from an XP machine. Bad news is that the phone still randomly reboots.
I guess the only other step is to un-root and S-On. What have I got to lose. Can't use the phones as they are now.
Got a good way to do this?
I cannot for the life of me coax my Rezound into creating a nandroid backup. I kind of a n00b, so I'll give you my info and how I rooted.
ROOT
I rooted by following Scotty's noob friendly root guide: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
I followed his instructions for "temporary recovery" which installed Amon RA 3.14
MY CURRENT SOFTWARE
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
FIRST ATTEMPT
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were.
I selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection.
It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
SECOND ATTEMPT
I installed ROM Manager.
I selected "Flash ClockworkMod Recovery" ... not realizing exactly what I was doing. None the less ...
I booted into CWM.
CWM freezes while making a nandroid backup. Every time. Battery pull. Every time.
THIRD ATTEMPT
I followed Scotty's "temporary recovery" instructions to install Anon RA 3.15 (different version this time)
The md5 in the command window did not match the md5 at download site (http://forum.xda-developers.com/showthread.php?p=23781936)
Seeing no alternatives, I flashed it anyway ... Nothing catastrophic happened.
Did same thing I did in the first attempt, and it gave me the same message.
Anyone have any other ideas?
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
You realize that after the OTA your backup won't work right? If you're just trying to cover yourself between now and then, maybe just copy your whole system and data partitions manually??
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
I don't understad why I can't enjoy these things and create a nandroid backup of my current ROM in case I decide to try other ROMs.
Are you saying that a permanent recovery is the difference between it working and not working?
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
bloodymurderlive said:
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
Click to expand...
Click to collapse
I can't say for certain because I've never gone through that situation before, but if you want to be stock...Why not just let the OTA update you to ICS stock and keep it as it is? Do you really like Gingerbread Stock that much? I guess I just don't understand your reasoning behind all of this. If you were flashing a new ROM after wiping everything in a recovery I would understand your need to nandroid...
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
bloodymurderlive said:
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
Click to expand...
Click to collapse
The firmware that is updated with an OTA update will most likely break Gingerbread compatibility if you try to restore a temporary nandroid backup.
With S-Off none of this would be a problem because we would just flash old radios and kernels right from recovery. HTC makes it difficult to downgrade
uToTMeH8
I want to have the option to return to whatever ROM I want.
If I OTA-update to ICS, I want the option to return to GB (especially given how notoriously buggy OTAs are).
If I install a custom ROM, I want the option to return to stock if I don't like it.
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
bloodymurderlive said:
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
Click to expand...
Click to collapse
This is why everyone is going mental about s-off in this thread:
http://forum.xda-developers.com/showthread.php?t=1578449
Honestly unlocking your bootloader, flashing Amon-Ra and backing up your stock is the way to go. I've had my phone unlocked for 3 months with no problems and the devs on this site are amazing! You're going to want to try every gingerbread ROM once you get really good at backups and flashing. I was getting around 6-8 hours on the stock ROM for battery life. I flashed NilsP's Business Ginger Sense and I hit 30 hours. It's ridiculous how much better battery life is after stripping the ROM down and adding tweaks.
This Toolkit really makes it very easy...Good Luck!
http://forum.xda-developers.com/showthread.php?t=1504824
The error is commonly not enuff space on the SD,or insufficient battery charge.
It has nothing to do with leaving the stock recovery in place.
The only reason you won't be able to restore your gb backup after ics is the fact that it takes a different hboot and.radio,and until the s off method is released,there is no way to revert those. With htcdev,you can only go fwd,not back.
MrSmith317 said:
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Click to expand...
Click to collapse
uToTMeH8 said:
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
Click to expand...
Click to collapse
the reason for leaving the stock recovery is simple: a custom recovery will not install an OTA.
if you leave the stock recovery in place,the OTA will happen,quite naturally,and without isrupting your personal data. sure,it will break root,and anything youve frozen will pop back up,so you do have the minor inconvenience of re-freezing some bloat,and re-launching the temp recovery to flash root files. not a big deal,IMO. remember,htcdev is more like s-off in that you will always be able to root,or re-root. its not an exploit that will disapear.
even if a person wishes to permanently install a recovery,i strongly recomend to get into the habit of launching recovery from fastboot when messing with your phone. as we know,htcdev only unlocks boot,recovery,and system,and we cannot write 'boot' from 'recovery'.
however,launching recovery from fastboot(what ive been calling a 'temporary' recovery) does allow recovery to write to boot. it doesnt do much good(yet) for flashing,as rom devs are still not including the neccessary scripts to install the kernel,but it does allow you to restore nandroids without a seperate kernel flash,making them quicker and easier.
until you switch to ICS firmware(i.e.,install the leaked ruu,or take an OTA) you can flash,backup,and restore any gingerbread roms,and GB firmware based ICS roms,as you desire.
again,what the guys were trying to say when the said you cant restore the GB backups after ICS is simply because the hboot and radio are different. sure,you can physically power up your recovery and restore a GB backup with ICS hboot and radio(firmware),and it will restore,and even boot. you will just have issues due to the incompatible firmware,such as the disapearance of your SD card
hope that helps clear a few things up for you. sorry the above reply was short,i was trying to reply on my phone at work
edit:
one last thing: since youve downlooaded rom manager and used it to flash clockwork recovery,you now have a permanently installed clockwork recovery. you can still temp launch amon with cw in place,but you now are missing the stock recovery,and as such will not be recieving OTAs. if this is important to you,you need to download the stock recovery,and permanently install it(fastboot flash recovery recoveryname.img)
http://www.mediafire.com/?wb21d2gdurui2c6
Thanks Scotty!
First, I'm a complete moron and assumed that my 32GB microSD had enough space. I deleted a movie and made my backup.
One question though about the CWM recovery ... I was concerned that it was permanently installed. However, I attempted to boot into recovery from my phone (power + volume down), and it booted into what looked like the stock recovery ... No dark Amon or CWM recoveries ... Is it possible that CWM didn't permanently flash after all? I know that I have been in both Amon and CWM, and CWM was installed from within the ROM Manager app ...
Are you sure you were in recovery, because power and volume down boots to the bootloader, called boot, which is entirely different.
Sent from my ADR6425LVW using xda premium
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
bloodymurderlive said:
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
Click to expand...
Click to collapse
Yes, Once and OTA is released it should not be long till someone posts here the zip install of the same OTA. Give it another day and I say you will see a cleaned up debloated, rooted etc... zip of the same OTA. These days there is really no need to rush for the OTA downloads, let the Dev's do their magic and offer you something better than Big Red will offer.
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Spaded21 said:
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Click to expand...
Click to collapse
You can simply flash a stock rom that has the update & flash the newer stock kernel that goes with it but you wont be able to update the radios. You wont lose any info this way unless something goes wrong.(always backup everything just in case something goes wrong).
As for backup, you will only be able to backup aps & data with titanium backup or some sort of program like that because If you do a nandroid backup and then restore after applying the update, you would be restoring your old rom basically over the new one and lose most update enhancements.
You should just follow the thread here http://forum.xda-developers.com/showthread.php?t=2155069 and go S-Off. I know you will have to restore everything because you will wipe your phone when you do this but its only gonna make things easier for you in the future.
Do a nan backup and save it in case you want to use it in the future and go back to what you had. Once you have S-Off, you can flash kernals, radios, & roms and put in any version you want.
Thanks for your response Jrocker,
So it looks like the best way to do this would be to backup my apps with Titanium, get S-off, install a stock ROM with the update, flash the kernel and radio, then restore from Titanium.
Step 1. Make nandroid
Step 2. Backup apps with Titanium, copy backup along with pics and video to PC
Step 3. Get S-off
Step 4. Flash Stock ROM - http://forum.xda-developers.com/showthread.php?t=2149095
Step 5. While still in recovery, flash stock kernel http://forum.xda-developers.com/showthread.php?t=2149951
Step 6. Flash stock radio http://forum.xda-developers.com/showthread.php?t=2155915
Step 7. Restore apps and pics.
Does that look correct? Do I have to worry about flashing a boot.img or modules(don't know what those are)?
Spaded21 said:
Thanks for your response Jrocker,
So it looks like the best way to do this would be to backup my apps with Titanium, get S-off, install a stock ROM with the update, flash the kernel and radio, then restore from Titanium.
Step 1. Make nandroid
Step 2. Backup apps with Titanium, copy backup along with pics and video to PC
Step 3. Get S-off
Step 4. Flash Stock ROM - http://forum.xda-developers.com/showthread.php?t=2149095
Step 5. While still in recovery, flash stock kernel http://forum.xda-developers.com/showthread.php?t=2149951
Step 6. Flash stock radio http://forum.xda-developers.com/showthread.php?t=2155915
Step 7. Restore apps and pics.
Does that look correct? Do I have to worry about flashing a boot.img or modules(don't know what those are)?
Click to expand...
Click to collapse
Have you unlocked the bootloader? (this step is usually done in connection with rooting the phone at the htcdev.com website). If you have an ulocked bootloader, then you can flash an alternate recovery (eithe cwr or twrp) and do a nandroid backup.
Then follow the steps to get s-off. Note: the step where you have your data wiped is unlocking the bootloader, not obtaining s-off. If you already have an alternate recovery, and root, then s-off generally will not wipe your phone. But do an nandroid backup in cwr or twrp just in case Although a nandroid won't backup pictures etc.
Once you have s-off, flash the stock (but rooted) rom you linked to in step 4. This step SHOULD flash the stock kernel if the .zip file was prepared properly. If you boot into the rom and have flickering or wifi issues, then you will need to flash the stock 2.04 kernel (in fastboot). You can also verify if the new kernel was installed when the rom is booted by looking at the Settings:About:Software Information:More (baseband, kernel etc). You should see there kernel version 3.4.10. The baseband (radio) should be 1.01.01.0110 once you have updated the radio (see the step below). The kernel file is the boot.img file you were asking about. The modules will already be built into the stock rom.
While in fastboot (not recovery) you can flash the updated radio files (that will make the baseband referred to above be 1.01.01.0110.
The time when you need to worry about flashing a kernel (boot.img) and modules is if you are s-on, or if you are s-off and the zip file was prepared as you were s-on. When you flash a "kernel", it consists of a boot.img file, along with some extraneous files (the module). When you are s-off, these can both be flashed together while in recovery. When you are s-on, the boot.img file must be flashed from fastboot (or else an alternate method using an app like Flash Image GUI). Because until recently, most DNA's were s-on, the kernel developers prepared their files for s-on devices, with instructions for s-on devices.
When you flash a rom that uses a different kernel than the one you are using, if the .zip file is prepared for a s-off device, then there are no additional steps necessary.
You may want to do a factory reset when you flash the updated 2.04 rom. I think it would be wise. As I said earlier, you shouldn't lose your /sdcard partition UNLESS you haven't already unlocked your bootloader. s-off doesn't reset your device.
Wow, all I can say is thank you so much! That was an awesome, detailed answer. It makes so much more sense when someone fully explains everything all at once, instead of me trying to piece everything together myself from various threads.
Yes my bootloader is unlocked. So you are saying once the bootloader is unlocked wiping data won't touch the SD card partition, just as if I had an actual SD card? When I rooted my Thunderbolt and did subsequent factory resets on that, it never touched the SD card. When I rooted my DNA it wiped everything. Either way I will always make backups and copy those to my PC.
I will be trying this later today and I will report back with the results. Seriously, thank you so much.
Spaded21 said:
Wow, all I can say is thank you so much! That was an awesome, detailed answer. It makes so much more sense when someone fully explains everything all at once, instead of me trying to piece everything together myself from various threads.
Yes my bootloader is unlocked. So you are saying once the bootloader is unlocked wiping data won't touch the SD card partition, just as if I had an actual SD card? When I rooted my Thunderbolt and did subsequent factory resets on that, it never touched the SD card. When I rooted my DNA it wiped everything. Either way I will always make backups and copy those to my PC.
I will be trying this later today and I will report back with the results. Seriously, thank you so much.
Click to expand...
Click to collapse
I was looking for this exact solution as well. This was before we had s-off. For a while my solution was to freeze a couple apps in TB so the OTA pop up would stop popping up. I think it was HTC DM 1.0.2219251543..... and HtcDm 1.0.221982913.... Looks the same but they are different.
I like stock but I eventually flashed ViperDNA. It looks like stock but you are able to customize the $h!!t out of it. Its an awesome ROM that I highly recommend. Although you might want to wait until he comes out with 1.2 (the new version with the latest firmware) becuase you have to wipe data. Data wiping isn't a big deal if you use TB.
Ether way you go - Stock ROM or ViperDNA - The recommended way to wipe your device is this way:
(I'm using TWRP but CR should be similar, might be in different menus)
Backup everything using TB
Backup Pics and other docs on internal SD card (JUST IN CASE)
Make Nandroid Backup in Recovery
Wipe Menu-> Wipe Dalvik Cache (some like to wipe 3 times others think its just a waste of time)
Wipe Menu-> Wipe Cache (Factory Reset wipes cache but I like to wipe cache anyway just for completeness )
Wipe Menu-> Factory Reset
Wipe Menu-> System
Don't Format Data and Don't wipe Internal Storage. You will loose SD card contents.
Once you install your ROMS, flash your kernals, flash radios...whatever you want to do...You can restore apps and data from TB
As always, follow the ROMS instructions on their page for more information.
Only Restore User Apps and Data
Never restore any system apps in RED. May not be compatible with new ROM
You can however restore system Data that is in Yellow or Green (DATA ONLY)
Thanks devilsaces
Once I get everything updated and get a good nadroid of the newest firmware with all my apps I will definitely give ViperDNA a shot. I tried a few custom ROMs on my Thunderbolt, and while they were great to customize, they weren't always stable. Like I said I use my phone for work all day so I really need something dependable, and so far stock hasn't let me down.
Thanks again everyone, a lot of great info in this thread. Hopefully this will be useful to others as well.
Spaded21 said:
Thanks devilsaces
Once I get everything updated and get a good nadroid of the newest firmware with all my apps I will definitely give ViperDNA a shot. I tried a few custom ROMs on my Thunderbolt, and while they were great to customize, they weren't always stable. Like I said I use my phone for work all day so I really need something dependable, and so far stock hasn't let me down.
Thanks again everyone, a lot of great info in this thread. Hopefully this will be useful to others as well.
Click to expand...
Click to collapse
Yeah, I had the same problem on the Thunderbolt, nothing stable. Viper however feels great. I would definitely freeze the HTC apps in Titanium Backup to get rid of the annoying pop ups. I noticed Viper has them uninstalled.
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Spaded21 said:
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Click to expand...
Click to collapse
I'm actually running that rom right now.
You don't need to flash the radio if you don't want. If you are happy with your cell reception, and battery life, as well as wifi, then you can stay on the original radio.
Or if you'd like to try the new radio, you can flash that (once you have s-off) with this thread: http://forum.xda-developers.com/showthread.php?p=38197525
I'm not sure if there is a radio flash prepared to go back to the original radio. Generally speaking, once to are s-off, you can change radios at will.
From what I understand, if you flash the rom you linked to, and the radio above, then you will have everything from the update, except the updated hboot. I haven't bothered changing my hboot. changing hboot won't affect the day to day operation of the phone, but it can change the fast boot commands that are available. Until I see a good reason, I am not going to worry about my hboot.
FYI: about changing radios, from what I understand, the radio file is the code that tells the phone how to communicate with the towers. It tells the phone how to adjust the power output of the radio according to the strength of signal from the cell. This can be very aggressive, leading to better signal, at the expense of battery life (increasing power output of the phone radio takes more power from the battery), or it can be conservative, with a little lower quality signal, but conserving battery life.
It seems that the engineers at the carriers are constantly tweaking the radio code to find a sweet spot between signal quality and battery life. Different carriers may tweak the radio for the same phone with a different priority. Sprint may prioritize signal, while verizon prioritizes battery. So each carrier may have a different radio file for phone that is in the same phone family. And then each carrier may have multiple radios. On the thunderbolt there were about 6 or 7 I think, but it is generally believed that newer radios work better than older ones.
Some people on xda will often experiment to see which radio file works best for them, depending on where they live and work.
I always try to be careful to only flash redid that others have reported to work with my device, rather than experimenting personally. I would think that you can brick your phone flashing the wrong radio file.
Sent from my HTC6435LVW using Tapatalk 2
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Spaded21 said:
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Click to expand...
Click to collapse
Firmware is the Android system. The Droid DNA is on on 4.1.1 (Jelly Bean). That version has not changed in the new OTA update so I don't know why that ROM even mentioned it.
The Kernal is the interface that alows the software to access the hardware. A more detailed explanation can be found here: http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
HBOOT is 'kinda' like your BIOS in windows. It is the bootloader. It is the first thing that is loaded on your phone. This too I believe has not changed with the latest OTA update.
This is the change log for the 2.04.605.2 710RD update
Bluetooth connectivity and volume level for specific models have been improved
Enhanced reliability and stability of the Contacts List have been made
Enhanced Recent Apps functionality has been improved
Incoming messages display with the correct timestamp
Improvements to Hotspot connectivity have been made
Improvements to Audio Quality for wired headsets and earpieces have been made
Improvements to default browser for zooming capability have been made
User can load videos on HuluPlus
Wi-Fi Connectivity has been improved
As you can see it is mostly stuff related to your radio so the radio is the main part you would want. I personally just updated my radio and din't worry about anything else.
---------- Post added at 12:15 PM ---------- Previous post was at 11:56 AM ----------
Spaded21 said:
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Click to expand...
Click to collapse
I don't think it is deodexed otherwise it would tell you. I think deodexed is good if you want to theme.
I'm using the first one, which isn't deodexed. But I'm keeping my rom close to stock this week
Next week, when the Viper rom has been updated to 2.04, I'll be flashing that, and probably a theme.
You indicated that you aren't currently running any mods or themes. Unless you are looking to change, I would suggest you flash the first rom you linked, which is stock, except for the root capability being added to it.
The de-odexed rom you asked about will have been modified, deleting the .odex files so that the rom can further be customized by themes etc. When a phone boots a rom that is missing the .odex files, it will take longer to boot because it will essentially create the missing .odex files on the fly while booting. But when you are modding your rom, adding themes etc., existing .odex files get in the way, so that is why developers remove the .odex files, even though the rom will take longer to boot. Once the phone is booted, whether the rom was odexed or not becomes irrelevant.
For now, if you are looking to be on the latest radio and HTC rom, I suggest you get s-off, then flash the basic 2.04 rom (the one you linked to first), and the updated radios. Hopefully HTC will soon release the updated source files for the 2.04 kernel, and then we will have more customization.
If you are looking to customize now, I would get s-off, then flash the updated radios, but stay with a rom based on the original released rom and source (like Viper). The latest Viper rom (with updates to 1.1.3) has modifications so that you won't have to worry about getting bugged to update your ROM for 2.04. If you decided to go with Viper, it is a little confusing when viper is updating from 1.1 to 1.1.1 to 1.1.2 to 1.1.3, because it uses an over-the-air (OTA) update process similar to the stock OTA update. So you may see notices for updates - but the updates would be for Viper. Once you have gotten your phone s-off, you don't need to worry about updates causing problems.
Spaded21 said:
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Click to expand...
Click to collapse
Ok so I have done everything, S-off, deodexed stock ROM, 3.4.10 kernel (it flashed with the ROM), and updated radio. I'm able to boot up but I don't have wifi.
Edit: Flashed the boot.img from the zip and it's working now.
Spaded21 said:
Ok so I have done everything, S-off, deodexed stock ROM, 3.4.10 kernel (it flashed with the ROM), and updated radio. I'm able to boot up but I don't have wifi.
Edit: Flashed the boot.img from the zip and it's working now.
Click to expand...
Click to collapse
Congrats!
I think that rom you used wasn't set up properly to flash the boot.img from recovery, so that is why you had to do it manually. As time goes on (and there are more users with s-off), I think most new roms will be set up properly, so you shouldn't run into that again.
The whole process wasn't that hard, and using TiB made it really easy to get everything back.
So how do I go about removing bloatware now that I have S-Off and I am deodexed?
Although there are several ways to start removing bloatware, one of the easiest ways is to go into TiBu, and freeze apps. Make a nandroid backup first, and start slow.
Some apps have dependencies, you freeze one, and another might not work, like contacts and dialer.
After you have frozen an app, and are confident that it isn't necessary, you can delete it if you want.
Sent from my HTC6435LVW using Tapatalk 2
Spaded21 said:
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Click to expand...
Click to collapse
I would highly recommend using the OTA blocking zip to kill the update messages. I'm not very handy with posting zips yet but search the threads for the disable OTA. I am on the Viper DNA rom also but I put the OTA blocking on just in case. If I were on my PC instead of my phone I could have posted the zip file for you. I'm sure with each rom the developer has added a file to make sure the OTA is killed but you can never be too sure.
Easiest way to get 2.04 OTA for rooted DNA phones
Hat-tip .Torrented from our discussion here: http://forum.xda-developers.com/showthread.php?t=2152993&page=12
Get Facepalm S-Off: http://forum.xda-developers.com/showthread.php?t=2155069
Download stock recovery from: http://goo.im/devs/Flyhalf205/DNA/dlx_recovery_signed.img
Flash the stock recovery using:
fastboot flash recovery dlx_recovery_signed.img
Click to expand...
Click to collapse
Once you are on stock recovery, and assuming you're on stock kernel, it allows you to take the OTA update!
After you take the ota just flash the custom recovery of your choice again. CWM Touch is a good option: http://www.clockworkmod.com/rommanager
Flash the superuser-busybox.zip to root.
This gives you a completely clean "factory" upgrade to 2.04, without losing any of your data (YMMV - so pls always take a backup before you do this).
It worked for me - yippee!!!
Software number: 2.04.605.2 710RD
Kernel version: 3.4.10-ga02d2c6
Baseband version: 1.01.01.0110
Whole procedure took less than 15 minutes
zanyguy said:
Hat-tip .Torrented from our discussion here: http://forum.xda-developers.com/showthread.php?t=2152993&page=12
Get Facepalm S-Off: http://forum.xda-developers.com/showthread.php?t=2155069
Download stock recovery from: http://goo.im/devs/Flyhalf205/DNA/dlx_recovery_signed.img
Flash the stock recovery using:
Once you are on stock recovery, and assuming you're on stock kernel, it allows you to take the OTA update!
After you take the ota just flash the custom recovery of your choice again. CWM Touch is a good option: http://www.clockworkmod.com/rommanager
Flash the superuser-busybox.zip to root.
This gives you a completely clean "factory" up to 2.04, without losing any of your data (YMMV - so pls always take a backup before you do this).
It worked for me - yippee!!!
Software number: 2.04.605.2 710RD
Kernel version: 3.4.10-ga02d2c6
Baseband version: 1.01.01.0110
Whole procedure took less than 15 minutes
Click to expand...
Click to collapse
Thanks zanyguy for the procedure and process outline. I have a question regarding my current format and was wondering if going to a stock rooted version would work for me. Since every end user is different then there are different things they want of course. For me the process is very simple. I like a very lean system. I also like to try and achieve many things to look as close to AOSP as I can get and keep functionality. My current setup has the phone unlocked, rooted, s-off and running Viper 1.1.3. My radio is the OTA update radio of 1.01.01.0110 and my kernel is the same 3.4.10-ga02d2c6. What I wonder is this. Should I even bother trying to flash the stock Rom? Is there any benefits to doing so? And if I do give it a spin should I just restore the Viper DNA rom or re flash anew?
Thanks
I've flashed my phone a few times before, but the last time I've done so, Titanium Backup decided not to work, so I had a newly flashed ROM but no data to go with it. I backed up everything on my phone once (by means of copying&pasting all of the folders) on my computer, but putting them back on my phone didn't do anything.
Now I want to flash again, but I'm clueless as to what app I should be using to back up my phone, and which app would make it possible for me to have my data backed up. I know it sounds a bit vague, but basically, I'm looking to back up my phone so that when I clear everything and flash it, I'd like to restore my apps as well as the data along with it (like high scores in games). Does anyone have any idea what I should do? I currently backed up my current ROM (Android 4.3 and HTC Sense 5.0) with ROM Manager (v5.5.3.7), but I don't know if I can use that back up since I'm looking to flash Android 4.4.2 onto it.
Any and all help is appreciated. Thanks in advance!
EDIT: And I have one off-topic question... Should I flash gapps before or after flashing the ROM? I flashed gapps before and after last time and it worked fine, but I'm curious to know what the correct order is.
Any help or guidance will be appreciated.
I just got a replacement phone from Verizon with 46A and these are the steps i followed to try and restore a stock rooted lollipop rom from my old phone.
-flashed to 10B by TOT method
-rooted with Stump
-downloaded TWRP from play store
-flashed and got to TWRP recovery successfully
-created a new backup with just the boot.img
-placed the old nandroid backup in that folder
-wiped cache and dalvik/art
-flashed XDABBEB's VS985 24B bootstack
-restored my nandroid backup
...and then i kept getting a "secure boot error" at startup. Boot verification error. I could only get onto TWRP and download mode. I don't know what i did wrong. I looked through this forum for solutions but couldn't find any. So long story short, i ended up flashing back to 10B via TOT method. Any solutions to restore my old backup?
also another strange thing was when i moved my old backup to the new folder, it wouldn't show the checkboxes for boot, data, system etc to restore. i had to place the old backup in the same folder with the boot.img and i had to copy and replace it with the old backup for it to show when trying to restore it.
Hi! Please in the future don't post the same question in two different threads. Since your other post in the toolkit thread didn't mention you having actually used the toolkit, here was the appropriate place to post it so I'll answer this one. I can't keep track so if your previous questions when I gave you advice were in the toolkit thread, it would've been fine to only post this question in that thread instead of making a new post. Obviously, if you didn't use the toolkit at all then this post here would be the more appropriate place.
You could wipe, re-flash the 24B Bootstack, flash whatever ROM (presuming Android 5.0.1 since you determined the 24B Bootstack was the correct one) it was you were using (the same one the TWRP backup was of), then restore only the data partition from the TWRP backup.
The other thing isn't necessarily strange although the way you explain it is confusing, so depending on what you mean.
i.e. This is an example of the folder structure of what I meant in whatever the original thread where you asked and I gave you my advice.
Original phone, original TWRP backup:
External MicroSD card:
TWRP/BACKUPS/VS985q34134pdygf/2016-04-06--11-43-58_MRA58K (random letters and numbers after the VS985)
New phone, new TWRP backup:
TWRP/BACKUPS/VS985adf346zdldd/2016-05-11--09-58-00_MRA58K (different set of random letters and numbers after the VS985 because of the new phone)
On the new phone, move your original backup folder "2016-04-06--11-43-58_MRA58K" from "TWRP/BACKUPS/VS985q34134pdygf/" to the new backup folder "TWRP/BACKUPS/VS985adf346zdldd/". The purpose of creating the new small backup of just your kernel (boot.img) or anything was just to create the new "VS985adf346zdldd" folder.
So now you'd have:
TWRP/BACKUPS/VS985q34134pdygf/ (empty folder)
TWRP/BACKUPS/VS985adf346zdldd/2016-05-11--09-58-00_MRA58K (new small backup)
TWRP/BACKUPS/VS985adf346zdldd/2016-04-06--11-43-58_MRA58K (your original TWRP backup from your old phone)
From there, you should be able to flash the 24B Bootstack and restore the "2016-04-06--11-43-58_MRA58K" backup.
I hope that clears things up.
Thanks for your response. My apologies regarding the double posting. I wasn't sure if you saw the questions i asked yesterday so i just needed some assistance.
So just wipe, flash the bootstack again and just restore the data? I will do that now. I just wasn't sure if it was the bootstack causing the issue or my backup. Some one mention the oversharpening mod. would that help or no?
Regarding the TWRP backup structure. I did what you did last night regarding placing the old backup in that folder but when i went to restore it, it didn't have any partitions to select. It wasn't until I copied the old backup to the exact location and overwrote the new and copied/replace the boot.img with the one from my old backup. then i was able to select the partitions. It was strange to me too. i didn't know if that caused the issue either.
soulfulb said:
Thanks for your response. My apologies regarding the double posting. I wasn't sure if you saw the questions i asked yesterday so i just needed some assistance.
Click to expand...
Click to collapse
You're welcome!
I can't speak as to others but most of the time when I check the forum, I check all the Verizon G3 sections to see if there's anything new anywhere. I probably won't see a post in a CM or a CM-based ROM thread, but probably everywhere else.
So just wipe, flash the bootstack again and just restore the data?
Click to expand...
Click to collapse
No. Wipe Cache, Dalvik/ART and Data, flash the bootstack, flash the original ROM zip that matches what you were running when you made the original TWRP backup, then restore the TWRP backup of only the Data partition.
I will do that now. I just wasn't sure if it was the bootstack causing the issue or my backup.
Click to expand...
Click to collapse
Unable to tell what's causing the issue but to paraphrase House M.D. "It's never the Bootstack."
Some one mention the oversharpening mod. would that help or no?
Click to expand...
Click to collapse
Help with what specifically? Help with the problem you're having booting the ROM you restore from the TWRP Backup? No. Help with oversharpening? Maybe. I've never felt a need to bother with it. I'd worry about getting your system working at all first, then think about additional modifications. Just do a new backup before any further modifications, once it's running fine.
Regarding the TWRP backup structure. I did what you did last night regarding placing the old backup in that folder but when i went to restore it, it didn't have any partitions to select. It wasn't until I copied the old backup to the exact location and overwrote the new and copied/replace the boot.img with the one from my old backup. then i was able to select the partitions. It was strange to me too. i didn't know if that caused the issue either.
Click to expand...
Click to collapse
Strange but I wouldn't think too much about it - as long as you found a way which worked for the partitions to show up. If I was there and could see everything it's possible I could figure out what happened. I don't know if you knew, but you can take screenshots in TWRP. Then, of course, you could mount your phone to the PC via USB with TWRP's mount menu to transfer the screenshots. Just out of curiosity, which TWRP did you install? 2.8.7.0 or 3.0.0? And which did you make the original backup in on your old phone? Either works fine but just in case ther was some kind of small change in behavior that I'm not aware of yet...
Also, what precise ROM were you running when you made the old TWRP backup?
roirraW "edor" ehT said:
You're welcome!
I can't speak as to others but most of the time when I check the forum, I check all the Verizon G3 sections to see if there's anything new anywhere. I probably won't see a post in a CM or a CM-based ROM thread, but probably everywhere else.
No. Wipe Cache, Dalvik/ART and Data, flash the bootstack, flash the original ROM zip that matches what you were running when you made the original TWRP backup, then restore the TWRP backup of only the Data partition.
Unable to tell what's causing the issue but to paraphrase House M.D. "It's never the Bootstack."
Help with what specifically? Help with the problem you're having booting the ROM you restore from the TWRP Backup? No. Help with oversharpening? Maybe. I've never felt a need to bother with it. I'd worry about getting your system working at all first, then think about additional modifications. Just do a new backup before any further modifications, once it's running fine.
Strange but I wouldn't think too much about it - as long as you found a way which worked for the partitions to show up. If I was there and could see everything it's possible I could figure out what happened. I don't know if you knew, but you can take screenshots in TWRP. Then, of course, you could mount your phone to the PC via USB with TWRP's mount menu to transfer the screenshots. Just out of curiosity, which TWRP did you install? 2.8.7.0 or 3.0.0? And which did you make the original backup in on your old phone? Either works fine but just in case ther was some kind of small change in behavior that I'm not aware of yet...
Also, what precise ROM were you running when you made the old TWRP backup?
Click to expand...
Click to collapse
Thanks again.
I'm on 2.8.6.0. Should i uninstall and do 2.8.7? Is there a way to tell what my backup was on? Sorry i don't know off hand.
I know i''ve been a bit of a bug, but which/where can i find/should i flash 24b rom ? i was looking through and only saw the jasmine but i just wanted to flash the stock.
i'm at work now but when i get home i will try again and if errors show, i will mount and upload the screenshots.
roirraW "edor" ehT said:
Also, what precise ROM were you running when you made the old TWRP backup?
Click to expand...
Click to collapse
Stock 24c rom
soulfulb said:
Thanks again.
I'm on 2.8.6.0. Should i uninstall and do 2.8.7? Is there a way to tell what my backup was on? Sorry i don't know off hand.
I know i''ve been a bit of a bug, but which/where can i find/should i flash 24b rom ? i was looking through and only saw the jasmine but i just wanted to flash the stock.
i'm at work now but when i get home i will try again and if errors show, i will mount and upload the screenshots.
Click to expand...
Click to collapse
You're welcome!
You don't have to uninstall anything. Just download 2.8.7.0 (or 3.0.0) and flash it from inside your current TWRP. Don't know if that would've necessarily caused a problem, though.
JasmineROM 8.x is the closest you're going to get to completely stock 24B. In the case of JasmineROM and SkyDragon, ALWAYS flash the Bootstack AFTER flashing the ROM. It won't hurt if you flash any bootstack before flashing either ROM, but you MUST flash the bootstack after flashing the ROM. This most especially pertains to 35B of both ROMs, but might as well just get used to it on any version of those two ROMs.
You can also always upload the TWRP log although it doesn't sound like you're having a problem actually flashing or restoring anything. I mainly meant for showing the organization of the TWRP backup files, you could've used screenshots but I doubt if that's an issue so I wouldn't worry about that.
I hope you don't mind me adding that 35B runs a lot better than 24B or 23C. You can always use the built-in LG Backup to backup your user apps, user data and limited system data, to move between different versions of Android on stock LG ROMs. @xdabbeb 's VS985 v2.0.0 in particular is the schnitzel.
roirraW "edor" ehT said:
You're welcome!
You don't have to uninstall anything. Just download 2.8.7.0 (or 3.0.0) and flash it from inside your current TWRP. Don't know if that would've necessarily caused a problem, though.
JasmineROM 8.x is the closest you're going to get to completely stock 24B. In the case of JasmineROM and SkyDragon, ALWAYS flash the Bootstack AFTER flashing the ROM. It won't hurt if you flash any bootstack before flashing either ROM, but you MUST flash the bootstack after flashing the ROM. This most especially pertains to 35B of both ROMs, but might as well just get used to it on any version of those two ROMs.
You can also always upload the TWRP log although it doesn't sound like you're having a problem actually flashing or restoring anything. I mainly meant for showing the organization of the TWRP backup files, you could've used screenshots but I doubt if that's an issue so I wouldn't worry about that.
I hope you don't mind me adding that 35B runs a lot better than 24B or 23C. You can always use the built-in LG Backup to backup your user apps, user data and limited system data, to move between different versions of Android on stock LG ROMs. @xdabbeb 's VS985 v2.0.0 in particular is the schnitzel.
Click to expand...
Click to collapse
Thanks to you I just was able to restore my backup! I followed your steps and flash jasmine, then the bootstack, and then my backup data only and boom....back in service.
I can't thank you enough. I was nervous yesterday, but much relieved now.
In the future, lg backup would be my best option if i wanted to save my apps and data and switch to a newer rom (ie xdabbeb, 46a)?
soulfulb said:
Thanks to you I just was able to restore my backup! I followed your steps and flash jasmine, then the bootstack, and then my backup data only and boom....back in service.
I can't thank you enough. I was nervous yesterday, but much relieved now.
Click to expand...
Click to collapse
Awesome! Nothing makes me happier on XDA than to hear everything went as planned and it works.
In the future, lg backup would be my best option if i wanted to save my apps and data and switch to a newer rom (ie xdabbeb, 46a)?
Click to expand...
Click to collapse
Absolutely, in my opinion yes. LG Backup has a small quirk or two but it works so fast and painless. It can't replace TB completely but for the usual work of just backing up and restoring your user apps/data and just a little bit of system data I think it's far superior an experience.
If I move away from LG whenever I upgrade then I sure will miss LG Backup.