I'm a newbie and I am in trouble. I have a rooted Nexus 7 2013 and I have a TWRP Nandroid backup which I had copied to my WIndows PC.
Now my Nexus 7 crashed and won't go beyond the X on bootup. The Nandroid and Titanium backups are on my windows PC.
How do I restore the Nexus 7 to working status by restoring from the Nandroid backup and data I have copied to the PC?
Please help. Thanks.
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Bill235 said:
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Click to expand...
Click to collapse
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
sfhub said:
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
Click to expand...
Click to collapse
But will it remove the root I worked so hard to get?
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
raptir said:
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
Click to expand...
Click to collapse
Easy for an expert. I'm a newbie. I used the WUGfresh toolkit and it took multiple frustratng attempts and forever for it to finally download the correct adb drivers that would recognize the Nexus 7. Then all went smoothly.
But back to the present. I'm all fine now (till the next time the Nexus 7 crashes on me). For other newbies like me who run into this problem and need simple instructions here is what I did.
The first time this crash with the boot stuck on the X screen happened, going to the recovery screen (Power button + Volume up simultaneously) showed me the android on his back with a red triangle. Pressing power button and briefly volume up gave me the option to reset the tablet without removing root. Because I was traveling and did not have my TWRP backups with me (they were on my laptop 1,000 miles away) this removed all my data and I had to re-install all my apps and everything again.
The second time this happened, the recovery screen took me to the TWRP recovery screen. TWRP recovery had apparently survived the crash. I needed to save my data before reseting the tablet again. By trial and error I discovered that the TWRP menu has under the Advanced Tab a file manager. also discovered that if you connect a flash device to the tablet's usb port the TWRP file manager could read and write to it (!!!) in a folder called usb-otg (but not to my windows laptop). I copied what I wanted to save to the flash drive. Then I used the "wipe" tool to return the tablet to android.
I installed a free app, Recovery Manager, to reinstall TWRP recovery. Copied my previous TWRP nandroid backup to the tablet and restored everything as it was.
Easy as pie if you know how. I hope this helps some other befuddled user.
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Bill235 said:
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Click to expand...
Click to collapse
I can't say for sure what is happening in your case, but in my experience getting stuck on X means your user data got corrupted. The cases I've seen fall into 2 categories:
1) faulty EMMC flash memory. Sometimes if you wipe a couple of times the bad blocks get locked out and you don't see the problem anymore. Other times, they keep coming back. In the latter case, return/exchange/rma the unit
2) android crashes (random reboot) and unfinished writes are not completed corrupting the user data. They put in code in the latest ROM to mitigate this so if you think you are suffering from this type of corruption, install the latest ROM if you haven't done so already.
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Bill235 said:
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Click to expand...
Click to collapse
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Bill235 said:
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Click to expand...
Click to collapse
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
RMarkwald said:
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
Click to expand...
Click to collapse
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Bill235 said:
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Click to expand...
Click to collapse
Review the General forum for the N7 2013 here, as there are threads stickied to the top of that forum which has write-ups and video how to's that'll explain it all. I suggest to review those FIRST before you try doing things just so you can get a picture of what's going on. It may seem like a lot, but once you do it, it really is not.
The Android SDK is installed on your computer.
Related
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
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
Hi. First of all congratulations on you exceptional work and great forum, I am a frequent reader!
Since yesterday when I turned it on I have not network connection on my phone (HTC One X). I tried the same sim card on a different device and it works, so I guess is something with the device, not the SIM or the carrier. As I recently (2 months ago) rooted and installed a custom ROM (cyanogenmod) following this tutorial (http://forum.xda-developers.com/showthread.php?t=1660807) I thought it could be something with the ROM and tried to went back to my original HTC version (before I install the cyanogenmod version I did what I think is a backup of my original ROM).
As it says in the tutorial I am using teamwin recovery project, so I used this software to backup, install the new ROM and now I am trying to restore the backup, but it is not working - it looks like it completes restore with success, then I reeboot the phone and it stays forever in the HTC splash screen...
Can anyone please help me with that?
Thanks!
Just a note: before it reboots the phone it says you device does not appear to be rooted and prompt me to install SuperSU now. I tryed it both doing it and not, dont know if it helps.
uaeted said:
Hi. First of all congratulations on you exceptional work and great forum, I am a frequent reader!
Since yesterday when I turned it on I have not network connection on my phone (HTC One X). I tried the same sim card on a different device and it works, so I guess is something with the device, not the SIM or the carrier. As I recently (2 months ago) rooted and installed a custom ROM (cyanogenmod) following this tutorial (http://forum.xda-developers.com/showthread.php?t=1660807) I thought it could be something with the ROM and tried to went back to my original HTC version (before I install the cyanogenmod version I did what I think is a backup of my original ROM).
As it says in the tutorial I am using teamwin recovery project, so I used this software to backup, install the new ROM and now I am trying to restore the backup, but it is not working - it looks like it completes restore with success, then I reeboot the phone and it stays forever in the HTC splash screen...
Can anyone please help me with that?
Thanks!
Just a note: before it reboots the phone it says you device does not appear to be rooted and prompt me to install SuperSU now. I tryed it both doing it and not, dont know if it helps.
Click to expand...
Click to collapse
flash SuperSU
restore our backup and dont forget to flash the backup's boot.img also.
robchongke said:
flash SuperSU
restore our backup and dont forget to flash the backup's boot.img also.
Click to expand...
Click to collapse
Thanks robchongke!
So I instaled the SuperSU (I still had it on a folder in the phone), then I went into restore, selected the older folder (which should countain my original ROM), all the process went ok with no errors in the console (restore completed in 149), then restart (again asking if I want to root my phone or not), I said no this time and then the same is happening, the phone starts with but stays forever in the splash screen. When you say "dont forget to flash the backupĀ“s boot.img also what do you mean exaclty? You mean in the restoring screen, after select the backup folder, select both Boot and System? That's is selected by default so I just "swipe to restore"...
Thank you for you help!
uaeted said:
Thanks robchongke!
So I instaled the SuperSU (I still had it on a folder in the phone), then I went into restore, selected the older folder (which should countain my original ROM), all the process went ok with no errors in the console (restore completed in 149), then restart (again asking if I want to root my phone or not), I said no this time and then the same is happening, the phone starts with but stays forever in the splash screen. When you say "dont forget to flash the backupĀ“s boot.img also what do you mean exaclty? You mean in the restoring screen, after select the backup folder, select both Boot and System? That's is selected by default so I just "swipe to restore"...
Thank you for you help!
Click to expand...
Click to collapse
you have to flash the boot.img so it wont bootloop. if you have a copy of your backup in your computer copy the boot.img and place it inside your fastboot folder if you do not have a copy you can mount your phone in recovery. boot into bootloader then enter this command in command prompt.
fastboot flash boot boot.img
flash erase cache.
robchongke said:
you have to flash the boot.img so it wont bootloop. if you have a copy of your backup in your computer copy the boot.img and place it inside your fastboot folder if you do not have a copy you can mount your phone in recovery. boot into bootloader then enter this command in command prompt.
fastboot flash boot boot.img
flash erase cache.
Click to expand...
Click to collapse
Oh that's a different think then... Thank you very much for your reply! Meanwhile I installed the ROM I had in my folder again - the version I installed first - and it worked fine and I have phone signal again! So everything is solved, not with the first solution I thought, but at least is working now. Now the pain of get all the apps installed again and configure everything...
Anyway, thank you very much robchongke, your help was great and I am sure if I had the knowledge to follow your instructions I would have the stock version installed right now.
uaeted said:
Oh that's a different think then... Thank you very much for your reply! Meanwhile I installed the ROM I had in my folder again - the version I installed first - and it worked fine and I have phone signal again! So everything is solved, not with the first solution I thought, but at least is working now. Now the pain of get all the apps installed again and configure everything...
Anyway, thank you very much robchongke, your help was great and I am sure if I had the knowledge to follow your instructions I would have the stock version installed right now.
Click to expand...
Click to collapse
No problem. it's good that you have a nandroid backup.
hi, recently i decieded to install CM11 on my samsung galaxy nexus, i downloded it and then i reset facotry my phone, but when i wanted to install it from Bootloader i got an error, then i thohgt it cause of old bootloader so i wanted to update it but THE problem showed up, i cant come into my android it wont be come, please help me out
If all you did was a normal factory reset, it should boot up fine. If you did something like wiped system, then you need to get to a computer and use ADB. If you wiped system then you have nothing to boot to
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
the error is: set_metadata_recursive: some change failed
E:erro in /sdcard/0/0/cm-11-20131130-UNOFFFICAL0maguro.zip
(stat7)
insstalation aborted.
the.farbod said:
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
If you have a backup though, why cant you just restore the backup? Can you not get into the recovery anymore?
kinda curious, OP why didnt you just wipe everything in recovery mode and flash it??
1) adb reboot bootloader
2) fastboot flash recovery ***recovery.img*** (i like to rename the image to "recovery" for the ease of my own useage)
3) press vol rocker to recovery mode and flash away!
I personally use TWRP, but a lot of people prefer CWM, they are both amazingly easy to use.
worst case, you flash the stock 4.3 image from google to get everything back on track.
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