Related
Hey Everyone,
So I was being impatient and wanted to change the Density of my LCD on my Nexus 7. I changed it from the stock DPI to 170 using LCD Density Modder on the Market. Ever since reboot I have not been able to get past the google screen when you first turn on device. I can get into bootloader as well. My bootloader is unlocked and device is rooted if that helps.
Is there any easy way to recover the device besides a adb, or fastboot method? If not, what are the adb, fastboot commands to flash the OTA image to device from my PC?
Thanks
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
I have the nexus root toolkit, but don't you need the device powered on to put in usb debugging mode, etc? All I can do is hit google splash screen and get into bootloader, recovery.
There's buttons that say revert to stock, I believe those work in recovery.
Sent from my LG-P999 using xda app-developers app
redmonke255 said:
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
+1 just unlock and reflash
Sent from my i777 using xda app-developers app
Whenever I try to flash stock + unroot I get error message, "Windows cannot find 'C:\\data\gnexwug_DLnX.exe'. Make sure you typed the name correctly, and then try again."
Im not trying to type in anything, all I am doing is trying to restore to stock.
did you make a nandroid backup?" i am goign through the same thing right now. I am goign to restore from backup.
To change the desinty, it must be manually done in build.prod i assume. LCD Density modder might not be compatible, yet.
edit: Crap, i cant boot to recovery for some reason :/
edit2: it seems the only way to boot into recovery now is from a ROM manager application. Ijust finished restoring using the Nexus Toolkit.
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
mheller91 said:
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
damienleetobin1976 said:
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
Click to expand...
Click to collapse
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
tremblingwater said:
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
Click to expand...
Click to collapse
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
theusername said:
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just using a file explorer (specifically, solid explorer but root explorer should also work), navigating to /system/build.prop, and changing the number ro.sf.lcd_density.
changing that particular number's easy, and the last app I tried somehow managed to make a second build.prop inside the same file. So yeah.
Don't forget to backup your build.prop (preferably externally as well, in case you need to flash it) before trying this. And/or make a nandroid.
damienleetobin1976 said:
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
Click to expand...
Click to collapse
Im not sure, i dont want to advise something that is wrong, but, no, it doesn't take extraordinarily long. How long has it been?
I would boot into fastboot again and try the other route (provided you have a rom on the device or hopefully, better yet, a nandroid)
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
jamesbra said:
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
Click to expand...
Click to collapse
Yep, this is how it got it back and running last night.
I then used root explorer to edit build.prop and it worked like a charm.
Thanks all
Will it work?
Yes. If it's the same device!
Sent from my Nexus 7 using xda app-developers app
kboya said:
Yes. If it's the same device!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Vague, but it's a replacement. Please verify
cmg5461 said:
Vague, but it's a replacement. Please verify
Click to expand...
Click to collapse
I tried this!!! I do not suggest it!!! Nothing went.. wrong per say.. everything restored nicely and I went on my way, but it had more lag spikes, it had random freezes while screen was off that required a reboot, and biggest of all, it semi corrupted the sdcard partition so it couldn't be accessed, I ended up just wiping my device and starting fresh, works fine now to wipe I suggest locking boot loader and reunlocking to get it really well wiped. For the record my restore was with only data which a Dev deemed safer than a full restore but sadly as he suspected, there were problems. You can I think use titanium backup on non system apps pretty safely though
Sent from my Nexus 7 using xda app-developers app
My answer was as specific as your 'question'. Assuming it is N7 to N7, with both in near identical states (I.e. ROM, apps, wipes etc) then it should work. However, restoring data is usually a hit-miss affair and YMMV.
'Old' and 'new device', as you stated, only make complete sense to you and the many mind readers and/or voyeurs and stalkers
Sent from my Nexus 7 using xda app-developers app
kboya said:
My answer was as specific as your 'question'. Assuming it is N7 to N7, with both in near identical states (I.e. ROM, apps, wipes etc) then it should work. However, restoring data is usually a hit-miss affair and YMMV.
'Old' and 'new device', as you stated, only make complete sense to you and the many mind readers and/or voyeurs and stalkers
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well we are in the N7 forum, and asking to restore data from a custom rom to a stock device would just be asking for trouble, lol.
yea golden rule, dont load a backup from one device to a replacement of that same device. apps are fine through titanium backup but dont be loading nandroid backups
I do this all the time across my devices .Restore my CUSTOM TI Backup but you need to selectively choose what to restore. This works ONLY With APPS AND APP DATA. NO SYSTEM APPS OR SYSTEM APP DATA. that is how the sd card becomes currupt. Also if you do a FULL BACKUP SAY OF YOUR PHONE. then selective restore some of it to A Say your tablet with apps and app data. THIS WILL ALSO NOT WORK IN YOUR FAVOR.
FROM the old device . do a backup of APPS ONLY no (some apps will work with apps and app data) THEN Restore that on your tablet or new device . Do not make a full backup of the old device then selectivity restore from it to the new device. This can also cause issues on the new device.
Hope this is not to complicated to understand im no writer.
The above is from my own personal experience with TI BACKUP... The above is how i have been doing it for years.. GOOD Luck
---------- Post added at 11:20 AM ---------- Previous post was at 11:16 AM ----------
cmg5461 said:
Well we are in the N7 forum, and asking to restore data from a custom rom to a stock device would just be asking for trouble, lol.
Click to expand...
Click to collapse
installed apps . (APPS THAT WAS not part of the rom)this will work just fine to backup and restore.. Even most will restore app data.
The problem comes when restore apps from one device to another where the app when it installs sets itself for the device type . Then restored to a different device type.. The issue with system apps is it could replace some system settings or files during the restore and currupt data or apps.
I just RMA my nexus device.
Used the command "adb backup -apk shared all"
That backed up my entire device and I didn't have to be rooted or have my boot loader unlocked.
Typed in "adb restore backup.ab" on my new device and was right where I left off.
You need the latest android SDK on you PC and you also need to run those commands as administrator.
I have an "adb backup" file from a stock, first-gen Nexus 7 16GB that was damaged. We replaced it with a second-gen Nexus 7 32GB, which has been rooted without touching the bootloader. We're having trouble getting the games to recognize their data when we restore them piecemeal, so I'm wondering if it would be safe to restore the adb backup from the old device to the new device? Are there enough differences to cause problems? If it fails, will I still be able to simply do a factory reset and get the new N7 back to factory specs? We've only had the new one a few days.
Hi I have a problem with my Nexus 7 (32 gb wifi only version).
My son in his infinite wisdom decided to install ubuntu on the tablet.
I went to try and restore this back to the android version but all it did was to wipe off ubuntu itself
I then went on jayceooi.com and used the nexus toolbox to see if I could reflash the images etc.Howveer although all the files were downloaded I canot get the laptop to recognise the nexus itself (even though it sems to charge the tablet). There is no menu at all to check whether or not usb debugging is ticked or not..
Im now left with the tablet without no apparent operating system. At the moment all it shows is the green android with fastboot mode but when I hit start it says booting failed.
Could someone help please before I do any more damage and I brick it completly (although I may have already done so)
thankyou for any help
Use wugs tool in dev stickies and make sure right drivers are installed.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Use wugs tool in dev stickies and make sure right drivers are installed.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
thanks it mentions it being a root toolkit. I didnt actually want to root so is it still ok to use to restore back to stock android?
It can do more then just root
Sent from my Nexus 7 using Tapatalk 2
jswarb001 said:
thanks it mentions it being a root toolkit. I didnt actually want to root so is it still ok to use to restore back to stock android?
Click to expand...
Click to collapse
Yes it can do restore back to stock. Just follow the guide to unlock bootloader so it can flash stock image then just re lock bootloader. It covers the process in op.
Sent from my Inspire 4G using xda premium
Ok thanks all. Seemed to be doing everything ok but its been stuck on"waiting for your device to finish booting back up" for about 30 minutes now. It did say it would take 5 to 10 mins but should i carry on waiting or abort and start again do you think?
thanks
I would reset it see if that helped
Sent from my Nexus 7 using Tapatalk 2
If your son re did the partitions for Ubuntu that could have messed things up pretty good. I have only had my nexus for a few days so I couldn't tell you how to fix the formatting quite yet. I would search around on how to verify and correct the partitions if needed.
Sent from my Inspire 4G using xda premium
Bout to get my nexus 4, will be dropped off by UPS tomorow. And i have a few questions, if anyone will be kind enough to answer.
Would it be a smart idea to unlock the bootloader and root it with TWRP recovery like the second i take it out of the box so that way i dont have to back anything up?
And then, when i decide to switch to a non stock ROM i will just need Titanium backup to backup my stuff and then im good to go?
Also, one more question, since nexus's dont have SD cards, wont my titanium backups get wiped when i flash a rom?
Thanks
1) Yes it would probably be a good idea to unlock and root right away. That's what I done with my Nexus 7. I didn't install recovery though because I wasn't interested in custom ROMs. If you're going to be flashing things right away then yes install the recovery aswell.
2) Titanium Backup will do that perfectly for you but you could always just make the backup through recovery. As you said you'll be using TWRP it means you can restore data separately from a backup anyway.
3) You don't need to worry about backups being wiped because they're stored in the internal SD. It's essentially just space to make sure important things can still be safe even if you factory reset.
Hope that helps
Sent from my HTC One using xda premium
Btw I would recommend Helium instead of Titanium Backup for backing up your stuff. Works much more efficiently, at least for me. Helium backs up everything, apps and app data, launcher, WiFi settings, user dictionary, launcher setup, and all your SMS data. I really like it and I've fully replaced Titanium Backup with it.
Sent from my Nexus 4 using xda app-developers app
Instead of titanium backup use go backup pro and save it to the cloud
Sent from my Nexus 4 using xda premium
After you root & unlock the device I strongly suggest you play around with the phone for a few days and see how battery is and its performance as well. After those few days if you want you could just install any rom or kernel you want. You'll thank me later. Lol
KidCarter93 said:
1) Yes it would probably be a good idea to unlock and root right away. That's what I done with my Nexus 7. I didn't install recovery though because I wasn't interested in custom ROMs. If you're going to be flashing things right away then yes install the recovery aswell.
2) Titanium Backup will do that perfectly for you but you could always just make the backup through recovery. As you said you'll be using TWRP it means you can restore data separately from a backup anyway.
3) You don't need to worry about backups being wiped because they're stored in the internal SD. It's essentially just space to make sure important things can still be safe even if you factory reset.
Hope that helps
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
nyyankees1237 said:
Btw I would recommend Helium instead of Titanium Backup for backing up your stuff. Works much more efficiently, at least for me. Helium backs up everything, apps and app data, launcher, WiFi settings, user dictionary, launcher setup, and all your SMS data. I really like it and I've fully replaced Titanium Backup with it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
ayo234 said:
Instead of titanium backup use go backup pro and save it to the cloud
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
scream4cheese said:
After you root & unlock the device I strongly suggest you play around with the phone for a few days and see how battery is and it's performance as well. After those few days if you want you could just install any rom or kernel you want. You'll thank me later. Lol
Click to expand...
Click to collapse
thank you all so much! I really appreciate the answers. I will look into all three of those options for backing up my data! Thank you. and the internal sd card thing makes perfect sense so thank you for that explanation. You all have a good day!
What is the easiest way to downgrade from 4.4 to 4.3? My devise is completely stock. 4.4 is just too laggy
coppercents said:
What is the easiest way to downgrade from 4.4 to 4.3? My devise is completely stock. 4.4 is just too laggy
Click to expand...
Click to collapse
You can flash the factory image but you'll lose all your data. Or you can use wugs toolkit and use flash back to stock option and it will do it for you but you still lose all data. Are you sure you want 4.3? 4.4 is smoother for me
Sent from my Nexus 5 using xda app-developers app
Rooted Device Downgrade
So to be clear, even if the N10 is rooted, in order to go back from 4.4 to 4.3 one has to flash the factory image? Wiping the device and restoring a 4.3 Nandroid backup of a previous 4.3 ROM will not work?
gbeardmore said:
So to be clear, even if the N10 is rooted, in order to go back from 4.4 to 4.3 one has to flash the factory image? Wiping the device and restoring a 4.3 Nandroid backup of a previous 4.3 ROM will not work?
Click to expand...
Click to collapse
Yes it will work but your progress since that nandroid is lost if you dont backup. You can also flash a 4.3 rom. Or mod the Factory image to not wipe your SD.
Sent from my Galaxy Nexus using XDA Premium HD app
If 4.4 is more laggy for you than 4.3, you're doing something wrong.
Maybe just trying a factory reset of 4.4 might cure it.
xsalemx said:
Maybe just trying a factory reset of 4.4 might cure it.
Click to expand...
Click to collapse
I've tried factory reset with no luck. Still laggy.
Thank you all for your replies. It is really appreciated.
So what would be the easiest way for me to return my device to 4.3 using Google's factory images? Sorry for being a little annoying. I don't want to brick my device
My Nexus 10 is also more laggy on 4.4. Strange.
Is it laggy immediately after the factory reset or after you've set up your apps?
Sent from my SGH-I747M using xda app-developers app
gc84245 said:
Is it laggy immediately after the factory reset or after you've set up your apps?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Yes it is laggy even after reset and reflashing the factory image with wugs toolkit. When the screen rotates, there is some stutter. I'm back on 4.3 and it's much better for me.
Thanks to abdel12345 for recommending wugs toolkit. It was an easy process
I installed via the factory image, and have no issues with 4.4. If anything, it's better.
Hi,
i go now also back to 4.3 because Simpsons is not playable on 4.4! It's soooo laggy. But only this Game.
Greets
Chris
jimh425 said:
I installed via the factory image, and have no issues with 4.4. If anything, it's better.
Click to expand...
Click to collapse
Yep I've figured out that the resulting system when you do 4.3---OTA---4.4 is a slower system than if you do a stock flash install. I've also now unclicked the "backup and restore" to not carry over anything.
Prove it yourself, by all means... if you're going to flash down to 4.3, flash to 4.4 first, try it and then flash to 4.3 if its still laggy, but I betta 5cents you'll find it better. That one game - Simpsons - just install it and benchmark.
As I do not know what is the cause of this lag-from-upgrade, I now also don't click on the "backup and restore" to make mine as vanilla as possible. I've just now done this to my N4 also having found it better having done it on my N10 yesterday.
I been using WUGS NRT to do unlock (one time), flash+unroot, and root.
Am thinking of downgrading as well..
Mine is completly stock..but after updating..i get graphical artifacts..battery charge time has doubled...it lasts 25% less...mic is badly placed even before
Google seems to in denial with nexus 10 problems..did not exect this from google
Sent from my HTC One X using xda app-developers app
When my n10 Finish's charging but if still hook up to pogo charger it becomes laggy... Try that if y have pogo chargsr . this does not occur w USB charging.
Anyone successfully bk to 4.3 w.o losing data?
Hi,
If you ever wondered if there was a way to restore stock without losing all your data, there's a way, which is not hard too... Just do the following:
Reboot in your custom recovery and then factory reset your device
Reboot system
Now download the Factory ROM and move it (the img files) to your adb/fastboot folder
Open a cmd there and do the following (remember to have the USB Debugging on)
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot reboot
Now wait for it to boot
Hope this helps you guys who want to downgrade to 4.3 and were afraid of losing your data (remember, the recovery still deletes your apps data, but you can backup it with an app like Titanium Backup).
I may write an script to do this soon... If you want you can wait for it (but it may be delayed up to this weekend).
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
XxLordxX said:
Hi,
If you ever wondered if there was a way to restore stock without losing all your data, there's a way... <snip>
were afraid of losing your data (remember, the recovery still deletes your apps data, but you can backup it with an app like Titanium Backup).
Click to expand...
Click to collapse
That is useful to know but how is it any easier than simply copying to Wifi NAS or connecting external storage, copying it out and back in again? You'd be backing up anyways as a good techie. As you say it deletes everything bar data.
FYI if you did ever want to WRITE to NTFS volume then selinux mode changer app is what I use.
nigelhealy said:
That is useful to know but how is it any easier than simply copying to Wifi NAS or connecting external storage, copying it out and back in again? You'd be backing up anyways as a good techie. As you say it deletes everything bar data.
FYI if you did ever want to WRITE to NTFS volume then selinux mode changer app is what I use.
Click to expand...
Click to collapse
In my case this one is way easier, as I have almost 32GB used, and it takes a whole lot time to just backup, who says copying it back. I know it's good to always backup, however in some cases (like mine) it's a way easier method to do like I explained above.
This is just an alternative method I'd like to share, I actually used this many times already, due to soft bricks, then I can't simply plug a external hard drive on my recovery and it would take ages to backup my data via adb. This is the best unbrick method IMO, as you're installing fresh ROM without the need of formatting your data, and works as well with installing a new ROM .
Just my point of view hehe
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster KitKated S4
XxLordxX said:
In my case this one is way easier, as I have almost 32GB used, and it takes a whole lot time to just backup, who says copying it back. I know it's good to always backup, however in some cases (like mine) it's a way easier method to do like I explained above.
This is just an alternative method I'd like to share, I actually used this many times already, due to soft bricks, then I can't simply plug a external hard drive on my recovery and it would take ages to backup my data via adb. This is the best unbrick method IMO, as you're installing fresh ROM without the need of formatting your data, and works as well with installing a new ROM .
Just my point of view hehe
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster KitKated S4
Click to expand...
Click to collapse
I have made note as I need to get into command line habit, I only go to Windows now to do Android recovery type operations, I use Ubuntu desktop and they have the adb and fastboot commands all native since Ubuntu made their own tablet is. Actually I'd quits like to know if can Android-usb-Android say my phone fix my tablet. Is that possible?
Sent from my Nexus 10 using Tapatalk
nigelhealy said:
I have made note as I need to get into command line habit, I only go to Windows now to do Android recovery type operations, I use Ubuntu desktop and they have the adb and fastboot commands all native since Ubuntu made their own tablet is. Actually I'd quits like to know if can Android-usb-Android say my phone fix my tablet. Is that possible?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Hi,
This one thing I still want to do, I managed to make my Nexus identify my S4, and the same on the other hand, however I didn't manage to get adb/fastboot working yet, I'll try some more researches and then we can see hehe.
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster KitKated S4