I dropped my phone and broke the screen. While the top 5th of the screen worked initially, it is now completely broken. I have CM9 on it, rooted and unlocked bootloader.
What are the steps I need to take in order to back this thing up to flash the image to a new phone to pick up exactly where I left off?
Should be able to do a nAndroid back up. Than boot back up to android and copy the file to a comp. When you get the new phone rooted and what not put the back up where there normally stored. Dont forget to wipe data, /system and both caches. Not sure but it'd be safe to use the same recovery on your new phone.
Sent from my Galaxy Nexus using XDA
Yes, I'm asking how to do a nandroid backup without using the phones screen
just use adb
adb backup -f filename.bak -all
should backup everything, then when you get the new phone, get the same rom installed and do a restore, no need for CWM
lordgodgeneral said:
just use adb
adb backup -f filename.bak -all
should backup everything, then when you get the new phone, get the same rom installed and do a restore, no need for CWM
Click to expand...
Click to collapse
This command will create a full backup that I can then use CWM to flash to the new phone?
I think I may have disabled debugging.... Is there a way to enable it without the screen?
Was gonna say flash a non touch recovery. But I dunno any way to enable USB debugging if touch input doesn't work. Though if you can put it in fast boot mode flash the non touch cwm and go from there. Don't need USB debugging for that.
Rename recovery to recovery.img for easy sake
Put it in the folder with fast boot
Fastboot flash recovery recovery.img
Sent from my Galaxy Nexus using XDA
armdavid2 said:
Was gonna say flash a non touch recovery. But I dunno any way to enable USB debugging if touch input doesn't work. Though if you can put it in fast boot mode flash the non touch cwm and go from there. Don't need USB debugging for that.
Rename recovery to recovery.img for easy sake
Put it in the folder with fast boot
Fastboot flash recovery recovery.img
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
if i get a different phone, im using a htc sensation now. planning to get a N4, will the back up be compatible? will apps restore to original state before my screen cracked?
Related
hi all
my galaxy nexus dead, i cant get it to boot
i manage to flash ClockworkMod
my question is how i can transfer files using ClockworkMod
or iד there other method like using adb
saturn said:
hi all
my galaxy nexus dead, i cant get it to boot
i manage to flash ClockworkMod
my question is how i can transfer files using ClockworkMod
or iד there other method like using adb
Click to expand...
Click to collapse
Saturn,
If you managed to flash CWM, your device is not that dead.
First thing I would try, is to load CWM and do a Factory reset, and Wipe cache. Than, reboot your device.
If this doesn't work, I don't see how CWM could help you, as Galaxy Nexus don't have external SD Card.
For CWM to work properly, you must first transfer your files to the virtual sdcard, than reboot to CWM and use that files.
If you can't boot, you can't put your files inside the device, so CWM is useless at this point.
So, what I would do right now, is:
1. Revert your device to stock..
Google for it. You'll use FASTBOOT or ODIN to reflash all partitions to stock ones.
This will even replace CWM for a stock recovery.
2. Flash CWM again.
Your device is probably working at this point. So, you can flash CWM again.
3. Reboot to CWM recovery and perform a backup. Keep it for future use, so you can restore your device at any time.
4. Download any roms you would like to, and have fun playing with your device!
Ps: Now I see that the original post was from Dec/2011.. Sorry for that.
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
cyaiphone said:
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
Click to expand...
Click to collapse
Nexus line.
have you tried reflashing cwm recovery via fastboot?
flash CWM via fastboot.
and why do you need a backup of stock? You can always re-flash the stock images to go back to completely stock. Restoring a rooted nandroid backup won't put you back to stock anyways...
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
cyaiphone said:
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
Click to expand...
Click to collapse
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
martonikaj said:
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
Click to expand...
Click to collapse
Crap is there a how to any how to do this? I've never used adb or command prompts.
cyaiphone said:
Crap is there a how to anywherebonnhow to do this? I've never used adb or command prompts.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1529058
And look for the "Setting up ADB for our device:" then "Obtaining Root Access and Custom Recovery:".
Can you boot into the OS? If you can, download Rom Manager from the Play Store and use that to install CWM Recovery.
Did you delete recovery-from-boot.p from /system? I had to do this to "permanently" install the recovery. My first Samsung phone, my first Nexus device, so not sure if this has been a regular thing ... never had to "permanently" install a recovery up until then. That fixed my issue as my recovery was only sticking once per boot ... was blowing my mind for a couple hours.
Not sure if root via toolkit solves this, but I did a manny root and had to do this. Hope it helps.
edit-
- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
Click to expand...
Click to collapse
Could also, apparently, rename it. I just reinstalled recovery, deleted, and haven't had a single problem since.
What bleedblue said; now go into fastboot, and reflash cwm.
Sent from my i9250
My coworker has a T989 with CWM 6.xxx touch that he acquired from the forums. He flashed CM 10 stable but was stuck in
a bootloop. We went back to recovery and flash the darksider scripts which as known to many here shouldn't be used in anything
higher than cwm 5.xx. Any action done in recovery now hangs and freezes. My solution to this would be to go into download mode
and odin a recovery or return the phone to stuck. Now the big problem is the USB port on the phone doesn't work. With properly installed
drivers the phone is not detectable in download mode, nor when the phone was working.
Any suggestions on getting out of this?
Warbuff said:
My coworker has a T989 with CWM 6.xxx touch that he acquired from the forums. He flashed CM 10 stable but was stuck in
a bootloop. We went back to recovery and flash the darksider scripts which as known to many here shouldn't be used in anything
higher than cwm 5.xx. Any action done in recovery now hangs and freezes. My solution to this would be to go into download mode
and odin a recovery or return the phone to stuck. Now the big problem is the USB port on the phone doesn't work. With properly installed
drivers the phone is not detectable in download mode, nor when the phone was working.
Any suggestions on getting out of this?
Click to expand...
Click to collapse
Hhhmm, I have used the darkside super wipe before in CWM 6 and have not seen anything like this [I don't anymore no real need for now it as everything cleans up nice under CWM just use mounts and storage and tap to format /system and /data and then just wipe cache and dalvick cahce and install ROM then install GApps.
You sure you used the right CM10 image [listed under the device name Hercules?
I didn't think we had an official stable CM 10 only nightlies.
If you flashed CM10 that you used on a different device then it replaced some critical files that probably caused this.
If I were you keep trying to get to download mode [there is a trick to it, it is like getting in to recovery manually on boot EXCEPT you need to plug in the USB cable right as you see SAMSUNG logo] and even though I have done it countless times there are those times when it takes me several good tries to get back there.
If you can get in to recovery DONT TOUCH THE DEVICE JUST GET IT THERE then plug in a USB cable and see if you can get to adb
if in windows be sure to run cmd [command prompt] as admin
if you can run adb shell and if it comes up with either just $ or # or a bunch of text then $ or # then...
If it is a $ then type in "su" [no quotes]
that way you get #
If it says # then type [again without quotes]: "restart download"
You should even be able to run the following command without opening the shell first but if it defaults to a user shell and not an admin shell [$ is a user shell and # is an admin shell] it may refuse to follow the command:
[again without quotes] "adb restart download"
This should get the phone to restart to download mode without using hardware keys
If you can get in to recovery and can adb shell to it on the computer that may give you a way to run commands and do things manually, but you will need to find guides on exactly how to run recovery via ADB [I have seen cases where you can copy a recovery to the temp section via adb and then manually run a command in adb shell and basically get the device to use the new file until the next restart.
The darkside scripts will bork any CWM that isn't CWM 5. A much quicker way is to download TWRP recovery and flash it. The recovery will lock up in the the flashing process, but after actually finishing the install. Once it locks up, hold the power button for 10 seconds to reboot. Once the vibration is felt hold both volume buttons and voila! You should be in TWRP recovery now.
I've personally done this myself as I'm the person who actually discovered that the darkside scripts are the cause for borked CWM 6 recoveries. Just don't use them unless you're on CWM 5 or TWRP.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
The darkside scripts will bork any CWM that isn't CWM 5. A much quicker way is to download TWRP recovery and flash it. The recovery will lock up in the the flashing process, but after actually finishing the install. Once it locks up, hold the power button for 10 seconds to reboot. Once the vibration is felt hold both volume buttons and voila! You should be in TWRP recovery now.
I've personally done this myself as I'm the person who actually discovered that the darkside scripts are the cause for borked CWM 6 recoveries. Just don't use them unless you're on CWM 5 or TWRP.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah but keep in mind myself and sevral others have had issues with TWRP not formatting partitions correctly [I almost threw a Nexus 7 through the wall for it] and it would boot loop over several different ROM flashes for a whole weekend.until I got tired of it and in a last ditch effort changed back to CWM [this was only a version or 2 ago, oh and one of the TWRP devs tried to convince me their /data wipe should also wipe /sdcard [/data/media in JB] and there was no way around that when in CWM I can go to mounts and storage and wipe /data without touching my user data on sdcard [I say SDCard to differentiate the user data housed in internal storage mounted as /sdcard and not just the user data in /data I know there is no actual SDCard in a Nexus 7] so that didn't inspire a ton of confidence in me.
I NEVER recommend TWRP to new users as it has also incorrectly hosed my boot partition on a flash and bricked my device and I had to get a replacement [This was a few versions ago].
Not saying you will get the same trouble just saying to me it is not worth the gamble when talking about my awesome T989 or Nexus 7.
Not to mention TWRP has a tendency when a JB ROM is installed to mirror the legacy mount points on to the /SDCard [in JB for backwards compatibility you get /storage/emulated/0/sdcard that has to be used by recoveries and when I used TWRP it would create that directory structure on to my SDCard when in fact it is only supposed to be a hard link [the directory /storage/emulated/0/sdcard exists but not on the SDCard it is just a pointer]
so essnetially you would end up with a double copy of your SDCard storage back on your SDCard [files still listed under /sdcard but then on sdcard would be a directory 0 that should not be there and in that would be /SDCard/ and another copy of what was on my SD]. I dunno if that bug has yet to be addressed or not [I think so but have not checked].
If you really want to flash TWRP just use market to download GooManager in Android and open and grant root
Once done hit settings button so you see its menu and tap Open Recovery and it will go through flashing TWRP [Similiar to how ROM Manager can flash CWM recovery for you from inside Android [must have Super User access first or they can't do so and you would then need to use Odin and flash it that way]]. Keep in mind your recovery should never freeze and CWM has never done so for me even as part of any install process.
RealPariah said:
Yeah but keep in mind myself and sevral others have had issues with TWRP not formatting partitions correctly [I almost threw a Nexus 7 through the wall for it] and it would boot loop over several different ROM flashes for a whole weekend.until I got tired of it and in a last ditch effort changed back to CWM [this was only a version or 2 ago, oh and one of the TWRP devs tried to convince me their /data wipe should also wipe /sdcard [/data/media in JB] and there was no way around that when in CWM I can go to mounts and storage and wipe /data without touching my user data on sdcard [I say SDCard to differentiate the user data housed in internal storage mounted as /sdcard and not just the user data in /data I know there is no actual SDCard in a Nexus 7] so that didn't inspire a ton of confidence in me.
I NEVER recommend TWRP to new users as it has also incorrectly hosed my boot partition on a flash and bricked my device and I had to get a replacement [This was a few versions ago].
Not saying you will get the same trouble just saying to me it is not worth the gamble when talking about my awesome T989 or Nexus 7.
Not to mention TWRP has a tendency when a JB ROM is installed to mirror the legacy mount points on to the /SDCard [in JB for backwards compatibility you get /storage/emulated/0/sdcard that has to be used by recoveries and when I used TWRP it would create that directory structure on to my SDCard when in fact it is only supposed to be a hard link [the directory /storage/emulated/0/sdcard exists but not on the SDCard it is just a pointer]
so essnetially you would end up with a double copy of your SDCard storage back on your SDCard [files still listed under /sdcard but then on sdcard would be a directory 0 that should not be there and in that would be /SDCard/ and another copy of what was on my SD]. I dunno if that bug has yet to be addressed or not [I think so but have not checked].
If you really want to flash TWRP just use market to download GooManager in Android and open and grant root
Once done hit settings button so you see its menu and tap Open Recovery and it will go through flashing TWRP [Similiar to how ROM Manager can flash CWM recovery for you from inside Android [must have Super User access first or they can't do so and you would then need to use Odin and flash it that way]]. Keep in mind your recovery should never freeze and CWM has never done so for me even as part of any install process.
Click to expand...
Click to collapse
Oh don't mistake my comment Lola I only said to flash TWRP over CWM just so he can have a fully working recovery again. Once that step is done flash back over to CWM 6 again. I myself prefer CWM or TWRP. This is just a method of dumping a borked CWM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Oh don't mistake my comment Lola I only said to flash TWRP over CWM just so he can have a fully working recovery again. Once that step is done flash back over to CWM 6 again. I myself prefer CWM or TWRP. This is just a method of dumping a borked CWM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Well Lola as you say, so would opening ROM Manager from inside Android and just tapping to flash the Recovery from the app without having to worry about ADB and manual commands and a run around [as long as you have root access of course].
RealPariah said:
Well Lola as you say, so would opening ROM Manager from inside Android and just tapping to flash the Recovery from the app without having to worry about ADB and manual commands and a run around [as long as you have root access of course].
Click to expand...
Click to collapse
Haha sorry about that. I meant lol if he can get into his ROM, then why hasn't he done so yet? I assumed what happened to him is what happened to me. Flashed dark side wipe, formatted phone, then every install afterwards failed.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Haha sorry about that. I meant lol if he can get into his ROM, then why hasn't he done so yet? I assumed what happened to him is what happened to me. Flashed dark side wipe, formatted phone, then every install afterwards failed.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I figured you meant LoL but Lola was funner so I used it again. I was not sure if originally he was one of the posts that siad he could have booted back or not [depends onn where the script froze in recovery as to whether Android boots].
If he can't then the easier way for most folks without having to go in to ADB running cmd as admin if using Windows, the commands and all
I would just say grab good ol Odin and CWM Recovery flash [Odin compatible usually is cwm-hercules-blah.md5 [in this case is not a text file with MD5 hash check it is the actual recovery] and have them flash it via Odin and fix it all up at once and besides they can get CWM touch for free if using Odin and searching the forums because if you dont mind flashing with Odin CWM touch is offered free here whereas if you use ROM Manager and try to flash Touch version of CWM that way it will charge you $2 per device [if you choose market pay option it should be tied to your account and that devices ID and allow future installs without charge [at least how it is for me had to pay once for my T989 once for my 8G Nexus 7 and the n once when I upgraded to 32G Nexus 7, but multiple installs on each individual device don't prompt me after I paid once [I have plenty of times where I may need to flash my recovery without computer access [and I know Koush myself so I like to donate his way he really does bust his ass ] so the ability to just flash the touch version via ROM Manager is great for myself.
I tried adb when I had the device. The Usb port I believe is damaged. I also tried using a flashable twrp and it stopped right before installation. When I restarted cwm was still there. Odin doesn't detect the phone even with the right drivers. It detects a gs3 and a skyrocket. To answer the question above there is a a cm10 stable for the Hercules. Do you think maybe I'm using the wrong flashable twrp. It just gets stuck on installing.
Sent from my Nexus 4 using xda app-developers app
Warbuff said:
I tried adb when I had the device. The Usb port I believe is damaged. I also tried using a flashable twrp and it stopped right before installation. When I restarted cwm was still there. Odin doesn't detect the phone even with the right drivers. It detects a gs3 and a skyrocket. To answer the question above there is a a cm10 stable for the Hercules. Do you think maybe I'm using the wrong flashable twrp. It just gets stuck on installing.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I believe I had TWRP 2.3.0.0. You should be able to find a zip somewhere or you can PM casonswag and ask him for it. He's the one who's been making flashable TWRP zips. Just make sure its for the Hercules.
One question though, does the phone have a ROM you can boot into or is it wiped.completely? Cuz if so, you can download goomanager or rommanager and flash a new recovery that way.
Sent from my SAMSUNG-SGH-T989 using xda premium
Only have access to the messed up recovery. No rom available to boot into.
Sent from my Nexus 4 using xda app-developers app
Warbuff said:
Only have access to the messed up recovery. No rom available to boot into.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try PMing casonswag for twrp 2.3.0.0. That's what I used and it worked. If not.. man I really don't know :-/
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks for your help. I've contacted him and awaiting reply. In the meantime my coworker already got a new gs2 from tmo through warranty.
Sent from my Xoom using xda app-developers app
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
jakubmi9 said:
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
Click to expand...
Click to collapse
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here
https://developers.google.com/android/nexus/images#razor
Make sure your boot loader is unlocked
Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.
If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.
http://www.wugfresh.com
I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
If it is recognize in fastboot you should be good to go, and yes it will wipe you data unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
If adb is working then you can adb pull your files assuming the file path it not corrupted
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
LinearEquation said:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.
mdamaged said:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
Click to expand...
Click to collapse
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work
Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.
Nexus 7 LTE
Carbon Rom
Faux Kernel
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA
Nexus 7 LTE
Carbon Rom
Faux Kernel
Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,
Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
TWRP will work like that.
fastboot boot twrp-whaetver.img
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yes, so does Nandroid Manager.
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Officially these: http://developer.android.com/sdk/win-usb.html#download
This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
Sent from my HTC One S using Tapatalk