Related
Greetings,
Am rooted, unREVOked, Clockwork recovery, s_off, froyo ROM and 2.XX radio and all of that working well. A couple of days ago my internal speaker blew, not sure why but is is all a buzz now and a replacement will be here in the morning. I am all clear and set with putting the old unit back to stock, but with a NANDROID backup, Titanium backup, and contacts backups all ready, can I just run unREVOked on the new one and do a NANDROID restore and all will be back, radio, s_off, and all ???? Or perhaps a good step by step so I do not break the new one ??? Thanks ;-)
no. you still have to run unrevoked, soff, and the 2.15 radio...after that, you can do anandroid restore
All done Grazi ;-)
I thought so,,,,all done flawlessly ;-)
Please report back
Sorry about your speaker ... I had to return 1 incredible over speaker issues myself.
I note that you ran S-OFF. I have avoided doing so for the exact reason that you are now experiencing ... blown speaker = warranty; S-OFF = no warranty; and one had NOTHING to do with the other.
There is some debate out there as to whether Verizon will figure out you ran S-OFF. Can you please report back and let us know if Verizon denies your warranty?
Thanks!
I would advise against restoring tha nandroid of the first device. There's a good chance that your old phone is going to be repaired and given out as a FRU. As such, both devices would share the same device id.
http://androidforums.com/all-things...05-warning-do-not-share-nandroid-backups.html
adrynalyne said:
Even if your apps aren't there, and no personal information has been entered on a fresh wipe.
If someone asks for a stock Nandroid backup, kindly tell them to get lost
contagous and I learned the hard way. I sent him a completely tweaked and clean nandroid, with none of my personal info or anything like that. He has been using it and it works great.
Until AppBrain fast web installer is used. See, it IDs your device by the Android_ID, which is unique to every phone, or is supposed to be.
Nandroid backups will record this device ID, and clone it onto another device. Well, when contagous installs an app using the web installer, I get it. Without a prompt or nothing.
While I can do the same thing, and it was fun sending him pron apps and sexy men wallpapers, it has a real potential for a security nitemare. I trust contagous, but let this serve as a warning to everyone. Its also not so simple as installing another ROM and factory reset. So far as I can tell, as long as you stay on the same build OS, you will keep the same ID. The only thing that changed my ID to something else was going back to 2.1.
So friends, don't let friends share nandroids. If you do, play it smart, and delete all but the system and boot images and recalculate the md5.
Click to expand...
Click to collapse
Nope
najaboy said:
I would advise against restoring tha nandroid of the first device. There's a good chance that your old phone is going to be repaired and given out as a FRU. As such, both devices would share the same device id.
http://androidforums.com/all-things...05-warning-do-not-share-nandroid-backups.html
Click to expand...
Click to collapse
While I do not intend to get into a debate about facts (facts are facts), the above is false.
I am on Incredible # 3. Each time I have nandroid restored on my new device. Each time I did so, I got a ton of FORCE CLOSES from Mobile Defender, which had to be uninstalled and reinstalled. Why? BECAUSE THE DEVICE ID WAS DIFFERENT.
If i log into Mobile Defender now, I see all 3 of my Incredibles all 3 with different device ID. Please understand, that's 3 phones, all of which used the same Nandroid, and all showing DIFFERENT Device IDs.
Ok steering my own thread, is that ok ????
Sort of still on the same tack but to address the above, I hope that the device ID thing being cloned by nandroid is false because I did not even think of it happening and I hope that I do not get whacked because of it. My old one was visually perfect so I hope they just replace the speaker, do a magic factory flash of some sort, which will hopefully S_ON the thing, and send it back out. An interesting thing is that I think some 3rd party company does the refurb because the box has a return label sending it to some other company, so maybe if they are not on the lookout then they will not check, just pass it thru like cattle on to the next customer. I will report back if VZW gives me any grief later on. If they do not honer warranty and charges me full price for the new one then they better send me my old one back and I will find the speaker myself from HTC and do an ESN swap with my old TP2.
On another note, steering my own thread yet again, when I did my restore I lost my pictures because I did not set the camera to store to SD card, but I assumed that they would be contained in the NANDROID backup, but they are not back in the new phone. I have serceral backups I could look thru but does anyone know how or what to use to open an .img file and which one they would be in ???? Thanks ;-)
Hello XDA-Community,
I am in a little bit of trouble with my HTC Desire and I was unable to find any documentation on here on via google to help me out so I am hoping anyone of you guys can give me a hand. Any input is very much appreciated, thank you beforehand!
So, the situation is as follows:
I have a branded T-Mobile HTC Desire (not a T-Mobile customer, though) with Froyo 2.2 stock running, I am a regular user and haven't messed with the software previously apart from installing apps as usual. Until today, where the mess started..
It is one of the old Desires with AMOLED, I think HBOOT version 0.93 or something?
I just want to say I am not bad with computers but I've only started to wrap my head around anything android-tech related as in rooting, flashing, etc. , which is why I'm here.
Now today I decided I want to go and first off, root my device so I can have a titanium backup and possibly tomorrow or sometime soon flash the oxygen rom because I hear I can have increased batterylife with that, which is my main concern (and app2sd for everything) with the HTC Desire.
So I read through lots of guides and arrived at using unrevoked³ to root the phone which worked fine. I then went and bought Titanium Backup Pro so I could make a backup of the entire thing and start flashing sooner or later.
Now I guess I made the first mistake right at that point when I did not make a backup immediately but first used TB to delete some T-Mobile bloatware which I dont use, I used the Filter option and then Remove Bloatware in the Settings to tag the apps in question ("TopApps" and "MobileTV", they are silly and just for customers anyway). TB said I have to restart the phone to remove them, which I did. I wanted to remove them before I did the backup because it was already complaining about low space after I put TB on (you know the desire and its space limitations..). And what good are useless apps in a backup, anyway?
Now, when it rebooted, at first everything looked fine, it starts up normally and goes on with loading all the stuff, I have a few widgets, GoLauncherEx, etc. which takes a bit to load at first start. But having loaded for about 1 minute after pressing the button, and when I can already see some of the UI elements properly in place (I can actually enter SIMcode and everything, or just wait at the code-login-form) - the phone just soft-resets itself and starts booting again. and again. and again. always up to the same point, I reckon.
I have tried getting the SDK and look into adb logcat while it boots (where I am an absolute noob, admittedly), and I was going to paste the entire thing here but my windows 7 "cmd" only has the last 300 lines of output selectable and I can't figure out how to "save" the rest of the log flying by when booting. It shows a lot of k9-mail errors in the log but I am not sure of that is the problem because I havent messed with k9 for months (using it as push mail client).
I am now unsure if the problem is because of TB or because of the removed bloatware, or what is going on. Right now, the phone is unusable.
I wonder if anyone can help me get the phone going again or how I could access the phone data to retrieve the phone's calendar entries and SMS, and possibly as much of the settings/data so I can just go and flash oxygen on it. I would, however, love to have a complete backup of the stock thing running, with TB and NANDroid backup, so I require a running phone I guess. I have previously synced the phonebook entries to MyPhoneExplorer on my desktop but it apparently didnt catch anything else.
I have attached the logcat output that I could capture in the txt file, if it helps with anything.
Thanks anyone for help really! Much appreciated!
Teaches you not to mess around without backing up first. You can get quite a bit of stuff to sync to your Google account like contacts and calendar entries. It also backs up other bits of data too.
From now on, it looks like you can only flash another rom or use an ruu, either way your data is gone like SMS and all that good stuff.
Sent from my HTC Desire using XDA Premium App
Honestly, you probably won't be able to get your data if it doesn't even get passed the first lock screen cause you may have deleted something compulsory for it to boot.
Just flash a new rom or the stock rom if you want then after you've set it all up run a titanium backup batch to save everything. Then and ONLY then should you consider installing Oxygen because Oxygen will require a number of modifications to your desire.
thanks for reading through all of it, I didnt realize the post grew so long when I posted it last night.
I know it is a prime example for the backup sense, Meape.. :/
Aegishua, It does get past the first lock screen. if I enter the SIM Code (or just leave the SIM Out), I can actually interact with the phone for several seconds, it loads widgetlocker and requests the unlock pattern, but there's not enough time to actually do anything when I see the the home screen.
I was wondering if there is a possibility to, say freeze the bootup sequence via USB adb commands or something, like you would press Pause on a desktop PC during the POST screen (yeah I know, the comparison is a little off). So at that point I could at least have time to fetch stuff from the phone to the PC.
and I noticed, if it helps anything: when the backlight is off (display dimmed), shortly before the reset the backlight flashes a couple of times which it doesnt usually do at that point of booting.
oh, and a little question for the next probable step: aegishua, what do you mean only then? I was following this guide http://rootmydroid.co.uk/guides/gen...esire-wildfire-evo-incredible-with-unrevoked/ , and would I not just get the oxygen ROM and follow Pt.3 From Step 2 onwards? Since I cannot do Step 1 anymore (full TB). I.e. just put the rom on SDcard and wipe + flash? btw, the original Oxygen thread ( http://forum.xda-developers.com/showthread.php?t=971904 ) does not say what Radio I need to flash (do I ?)- anyone care to point me in the right direction? Thanks again, I know I'm a noob at this.
Thanks a lot for any input guys
I will not be able to look at this thread for the next few hours but here's a quick update, I now started the phone without sdcard or SIM and it actually works! I mean, lots of apps are missing and icons and stuff, but the phone stays on regardless. I'm gonna go figure out whats wrong with the sdcard content, but first: backup time
Hi guys,
I've got a bit of a problem. My phone is stuck in a boot loop, which is a problem I've dealt with before, with help from these threads.
But this time I'm really stuck. I can't access the HBoot screen like I normally can, by holding down the volume up and power off buttons simultaneously.
I am using (racks memory) I think it's the War something mod of Cyanogen 7 I believe. I installed it 5 months ago and it's been working fine. This is not a new or recent install!
The phone does suffer from low memory issues a lot, as do all Wildfire S's. I have managed to get around that previously by moving apps to the SD card or linking to it or making user apps into system apps. I was in the middle of chatting on whatsapp when suddenly the phoned just blipped and died on me.. then it went into the boot loop. It's never happened before and my suspicion is that it ran out of memory or something.
I've tried removing the battery and leaving it out for some time, no luck. I've tried restarting without the SD card and Sim card. No luck. I've tried connecting it to my laptop... no luck. All the usual tricks just aren't working.
I have TiBu installed and my most recent back up was less than 4 weeks ago. I also did a Nandroid system backup a few months ago, so I should be able to restore ok, I just can't access the HBoot screen.
The other weird thing is, when I left the loading screen going round long enough, like in the time it would normally have booted.. suddenly the sound of my new emails popping up plays... and today, even tho it was on the load screen, it made clicking sounds like when I activate apps when my finger touched the screen. It's almost like the phone has started up as normal, but the load screen just won't go away and underneath it all is normal.
I've never had anything quite like this happen before and I've been without my phone for 3 days now, so came here in desperation for some inspiration! hehe.
I am probably going to buy a new HTC phone with a large system memory cos altho I dearly love my Wildfire S, the low memory has caused me nothing but problems since I first bought it, and I have wasted hours and hours on it, trying to get around the problems caused by it. But until then, I need to get my contacts and messages back and continue to use it for now. I would also ideally like to keep it going and give it to my sister perhaps who doesn't have a smart phone. She won't need as many apps as I do, so it would likely suit her, or maybe my Mum.
Any help anyone can give would be massively appreciated. Thanks guys!
Can't access HBoot!
Hey is anyone out there? I know lots of people get stuck in boot loops and there's a million threads of support for that, but this is different. I can't access the recovery system either. I have clockwork mod on it and normally you can get into that fine. Trying to find help on this problem is really tough cos I have to wade through all the noob threads for standard easy fix boot loops. If anyone could help me on this I'd be extremely grateful.
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Thank you!
MiCeltic said:
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for this... I'm willing to grasp at any thread at the moment. I did try the volume down option too but no dice there... but the whatsapp thread sounds promising, so I'm going to follow that up right now. It's after 4am and I've been sitting here working on this for hours and hours and at my wits end, so thank you! Fingers crossed!
Accessed HBoot!
Update:
Ok, I couldn't find the thread about whatsapp that was referred to above, but I have just tried accessing the recovery menu, using the volume down and power key, after first removing the sim card, but leaving the sd card in place. Suddenly that seemed to work! The menu came up!
I tried accessing it again with the sim card back in, and it refuses to come up again as before. So that at least is one issue resolved.
Now I'm having trouble mounting my SD card, which it says can't be mounted. I know the backups and recovery files are on the the SD card, but it just doesn't seem to see them there.
I wiped the dalvik cache in case that was causing any problems and it doesn't seem to have resolved this current issue so far. I'm going to keep trying other options as see how I get on, but I least wanted to share the solution to one of the problems my thread raised.
Further Update
I couldn't remember the name of my mod in the first post.. it was the WildChild mod.
After getting my phone into HBoot by removing the sim but keeping the SD card in, I found I was unable to mount the SD card. I researched this problem and some suggest the card may be corrupted.
I have checked the card on an external reader plugged into my PC and it read perfectly fine, and I managed to copy every bit of data on it across to the computer with ease. Others however found that after a reformat it eliminated any problems with mounting.. so that is what I am going to do and then try and restore the copy of the data I saved to the PC back onto the SD card.
Attempting now to reboot normally with the sim back in and the SD card removed this time produced a very desirable result. My phone started back up, albeit without the normal operating system. I was able to connect to wi-fi and my network and see a missed call voice mail message symbol. There are however no apps at all as yet and no background screen. I should mention that the phone did ask me to allow SuperUser permissions again.. I should also mention that I foolishly tried to Fix Permissions in CWM which then sat for a long time, eventually I removed the battery cos I thought it wasn't gonna do anything.. this is a big no no I now find out from the threads and I may have buggered it up a bit. I don't know.
My saga continues anyhow, and although I've not had much support on this, it might still be helpful for others to read and follow should whatsapp crashed their phone too and mess with their SD card somehow.
Another Update - Making Progress!
Next update on this...
I removed the SD card and put it in an external reader again on my PC.
Then I installed the free program Mini Tool Partition Wizard Home Edition and selected MiniTool Partion Wizard rather than the Power Data Recovery.
The Wizard allowed me to see the hidden partition on my drive. I understand now why it has always had trouble reading and writing to the SD card in the Ext section that was hidden. This should have been an EXT-2 or EXT-4 format partition I think, and mine is an EXT-3.
Maybe I'm wrong, I don't know much about these things and just learn as I go and by experiementing.
I had hoped to back up the hidden data in the partition but I was unsuccessful. Instead I found the Rebuild MBR (Master Boot Record) option and applied that to the entire SD card.
I then put it back in my phone, again without the Sim, and went into HBoot and recovery. I then went to my advanced back up and restore section and now the SD card is mountable and readable! I didn't have to wipe it or reformat!
I found my most recent up date which was the end of August... I wish I'd done them monthly, but oh well not too bad... and selected it and chose to Restore Boot.
Once it had completed I tried to reboot, but no dice. I put the sim card back in.. still didn't work... BUT I was now able to get into recovery again, this time without removing the Sim!
So inching along slowly here with this but making progress.
Next I plan to restore boot again, this time with the Sim card in.. and try and restart.. if that fails, I will go back into advanced recovery and try to also Restore System, and lastly restore SD-ext and see if each of those options repairs whatever damage that stupid Whatsapp did to my phone! I hope the little solution to various problems I've had are of some use to someone else here. Now wish me luck!
Wow, you were busy last night while most of the western world slept . I'm guessing if I posted at 11:10 PM and you said it was 4:00 AM, that your in the London timeline. I thought a little bit more, later, and I think that person's post I read fixed his phone by eventually getting into recovery and restoring, which as I remember worked that one time, until he reinstalled and used Whatsapp again some time later (it was at the insistence of a girl that used it). Whatsapp has, like 300 million users, but it does seem to give some people serious problems, and that's why I think most people are hesitant to try and help. They don't want to make things worse, since there are those instances of totally bricking a phone...but as long as a person can get into recovery, it's not bricked!
Interesting...I have done the, "fix mbr" in PCs many times, but I think you've taken it to new levels using it in phones! At least I don't remember reading anything much about someone doing it (in phones) before and it's brilliant, IMHO. You really did a great job sharing what you've done and I hope you get it fixed. I clicked a, "Thanks" for a good post follow up.
Insert standard disclaimer here: I'm not telling you to do anything, or what will or won't work, but sooner or later you're gonna have to restore that backup, but it's your choice on what to do; and, it sure seems like you know what you're doing, especially having made a backup to work from. I can appreciate the way you've gone piece by piece in your restore efforts to try and find where the problem occurred. The nice thing about the Wild Child ROM is it all works, and incidentally I think the developer uses ext2 for his extended SD card partition! It sounds like you reformatted to ext2 or ext4 from ext3, so the only thing there now is what came from restoring that backup piece in Clockwork; therefore, there's nothing that would be lost that isn't already; and, you backed up everything else on the SD card. So I don't want you to brick your phone either, but I'm wondering about wiping the cache and then the dalvik-cache, and then restoring your whole Nandroid backup?! I think your Whatsapp contacts are saved and so if the phone boots to a working condition you could just uninstall Whatsapp right away, boot into recovery and wipe cache and dalvik-cache again just to be safe, and then decide what to do about using Whatsapp again. As long as you can get into recovery, ultimately you could wipe, wipe, wipe and reinstall Wild Child to start all over if nothing else works.
On the other hand maybe you've already got this whole mess straightened out, if not, I'll again wish you - Good luck!
Solved!
So I next wiped the cache partition 3 times, as someone on another thread said sometimes it takes more than one go to clear it all properly for some reason.
I also wiped the dalvik cache again a couple more times. Then I went back to my back up and restored system. Then I tried to boot my baby back up.
I was falling asleep at this time but I remember the phone partially recovered. But most of the apps were broken. I had low memory issues too, so I uninstalled a few apps, managed to restore some individual apps or update them, and log in long enough to send messages to contacts with my email so I wouldn't lose them.
Then I fell asleep with the phone in my hand haha.. when I woke up I immediately continued with it and finally worked my way back to whatsapp being the last app I wanted to deal with. I managed to get into it and send some messages.
Then I did a full nandroid restore on everything.
The phone returned to it's state as of 2 months ago when I last did a nandroid back up. But some of my TiBu apps were backed up more recently. So I manually restored those and things were mostly back to how they were before and I am fairly happy with the low loss of data.
Whatsapp was working fine for a while.. but then it started having problems. It first had all my contacts there... then it lost their names but kept their numbers, then it lost all the old messages and right now I'm in the middle of trying to restore everything again and it's stuck on a restoration. I did a full uninstall of the app, restored the back-up, then it tried to update, but it always fails and now it's just hanging. So it definitely appears that whatsapp is one of the major causes of problems on my phone.
It was also one of the largest apps I had on there. Wildchild is an awesome rom, it only lacked video really and I installed a codec and player for that and got it working again, despite the guys on the Wildchild thread saying they didn't think it was possible. Yes I had trouble with it sometimes, but most of my trouble stems back to the low memory issues and the fact I broke all my apps up by spreading parts of them over the SD card, internal storage as user apps and system memory. That's a Wildfire S problem, not the fault of the Rom.
Anyway, I've made note of all the important numbers and will be buying a larger capacity HTC phone this week. Not sure which yet, but possibly a Sensation or Sensation XE, depending on my budget.
Thanks for your support MiCeltic. Yes I'm in London hehe. And I hadn't read anything about using MBR on a phone, but it was the SD card which had the problem and that certainly fixed it without having to wipe all my data.
I think what I have here is multiple layers of problems.. and I'm really pleased that after 3 days effort I managed to get past most of them. Once I get my new phone and transfer the contacts, I will have to think twice about using whatsapp.. it's my favourite app of all tho, so it will be hard to part with. This phone has many bugs.. I will completely erase it and reflash it when I get time and either keep it as a back up and maybe gift it to my sister or mum as I said before.
:good:
Last update
OK this is my past update on this... Whatsapp had one last surprise in store for me.
After it started messing up my phone again. I gave it one last chance. I completely removed it from the phone and installed it as new from the GooglePlay store. Then when I loaded it, it found the backed up Titanium BackUp messages and restored those.. then when I opened the app, it also had restored all my most recent messages, up to the day before it crashed the whole phone. I was amazed. They must have been stored on the server or something.. I think they sit there for 3 weeks. So I'm likely only missing one weeks worth of messages at most, about 4 weeks ago! Ha! Brilliant. I'm not doing a Nandroid backup cos everything is stable again and I hope to have no more troubles until it comes time to transfer all the date to the new handset... that's gonna take a while cos I will have to learn how to gain the boot mod rights all over again and maybe even flash a custom rom as the stock is sure to be loaded with bloatware. Still.. if it has a 1GB internal memory it shouldn't slow the phone down too much.. not compared to the tiny 150MB this little baby has!
If someone wants to close this thread now, feel free.
Cheers. :good:
You inspired me to read a little more last night and I did see where some people found a fix by uninstalling and then installing new (not from backup), then restoring their contacts. Seems like you've proved that point! Interestingly I read that ALL of your contacts are stored on the Whatsapp server, not just your contacts that have Whatsapp (Remember those permissions you accept when you install an app!). As I said, there are 300 million users, obviously not everyone has the problems, so hopefully it will work for you now and on your new phone, which after reading your posts I know you will make a back up of immediately and again after rooting...AND definitely before installing Whatsapp ! ! ! You might even find your next phone easier to root as a lot of them don't need an update of the bootloader on htcdev for the first step when unlocking and/or many can gain Soff!
Glad you got it working and now all's right with the world...well for now
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I also have a similar issue as the OP. I am currently rooted, stock rom. ZVD update has downloaded and is ready to install. However, what would be the nessesary steps to take prior to updating my phone? I dont care if I have to re-root again. I rooted me device using IOroot25. How can I unroot?
Thanks!
Supersu has the option to unroot permanently. Doing a full unroot. Weather the system accepts that, I'm not sure.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
...Only safe way right now is to tot back to stock zvc...
Click to expand...
Click to collapse
But, reflashing the ZVC tot will erase all data, correct?
jlv3 said:
But, reflashing the ZVC tot will erase all data, correct?
Click to expand...
Click to collapse
Yes, complete everything. Data, pictures, documents, downloads.
Sent from my Nexus 7 using Tapatalk
mtcellph said:
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
Click to expand...
Click to collapse
From what i understand , you will need a stock ZVC recovery and boot loader to apply the update. if you have any modification done in ROM (debloat/deleting/modifying system files) then the update might not complete.
So flash stock aboot(bootloader), recovery and kernel and then only apply the update.
TOT reflash is too cumbersome process and requires lot of restoration of apps setting etc.
I have same situation and am searching for stock files from ZVC. Please if any one has these stock file please do share.
Cheers
Phuq! I wish I read these forums more frequently.
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if there is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
ZVD bit me too-not sure how, NEVER told it to install
adamant_orcinus said:
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if te youhere is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
Click to expand...
Click to collapse
Sorry Dude, I was in the same spot, maybe I can save you hours of reading. This is what I had to do:
http://forum.xda-developers.com/showthread.php?t=2432476 it's the dreaded tot to zvc
Hey there guys!
So I'm having a bit of a situation with my Nexus 5. It is a first production run as I ordered it the hour it came out.
Today it started having HUGE issues. This is a few days after I downloaded Marshmallow 6.0. The device would shut down and then go into a boot loop for HOURS. Sometimes it'd start back up fine and be usable for a few minutes, but then shutting down and becoming unusable. Sometimes it'd start up and the "Optimizing Apps" screen would come up as if I had just made an Android upgrade, and it would complete after some minutes and become usable until it restarted again.
The phone "seems to be working" now OK. This thread is gonna be a bit multi-faceted, so sorry for asking so much :/ Just having a situation with my phone I want to remedy.
First, I'm looking for a good unrooted backup program I can use to backup the stuff on my phone to my computer or somewhere else. I want it in case I get the phone working again or I get a new android and want to transfer stuff over. Is it possible to move data from one backup to a new phone? Not sure. Either way, just looking for a good backup program I can use, if anyone can recommend me one.
Second, besides the obvious possibility of Marshmallow messing my phone up, a lot of people say it could have to do with a "stuck internal power button" and that "smacking the phone against a hard surface near the camera" could help. This seems mega sketchy, but at this point Im willing to do it after a backup. Does this solution have any merit or is it, as we say, "bulls***"?
Third, is there any possible way to remedy a bootloop software-side?
Thank you!
Since you are talking about downloading 6.0, and don't mention the N5X, I'm assuming you are in the wrong forum
That said:
You can run backups with adb (search for "adb backup"), without root. Just need adb debugging turned on in Android. This will also let you restore apps.
I've always used Titanium or a custom recovery myself, so I'm not familiar with the whole process.
I think you can clear the cache in the stock recovery too - might help? Fastboot & TWRP would offer more options, of course.
No idea on the stuck button theory - hopefully mods move this over so N5 veterans can you help out.
Thanks for the help!
To be perfectly honest, I didn't even know a Nexus 5X existed until now :$ Sorry for posting in the wrong forum, thought the X just stood for some production run number. My bad!