I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
resplin said:
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
Click to expand...
Click to collapse
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Still no stock recovery
wantabe said:
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Click to expand...
Click to collapse
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
resplin said:
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
Click to expand...
Click to collapse
I'm sorry about the link, not that it does any good now but the link is corrected. Using fastboot to flash the images is correct, I too often use adb as a generic term for both. When you boot into the stock recovery you will see the android with the exclamation mark and that is normal. Finally got the new 2012 N7 I bought as a gift and was updating it. Been a while since I've booted into a stock recovery. So... Boot into stock recovery, when the Android with the red exclamation mark appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. Whoop, Whoop! :laugh:
It works!
Thank you very much for your patient explanation. That helps a lot.
I hadn't realized that there was an additional step after the display of the warning android in order to enter stock recovery. All that time I spent trying to fix something that wasn't broken! <sigh>
I was unable to get the device to display the stock recovery menu, because it appears to require a very precise timing (I just keep rebooting it back to the system by accident). However, encryption did work fine. My confusion with the encryption was compounded by the fact that encryption of the Nexus 7 in 4.4 doesn't always work the first time (see this thread at android central: forums.androidcentral.com/google-nexus-7-tablet-2013/337078-experiencing-difficulty-encrypting-my-2013-n7-after-4-4-build-krt16s-upgrade.html). After trying 4 times in a row, the device encrypted. I was then able to put Team Win Recovery back on the device, and everything works perfectly.
Thank you again for your help. I don't see how to mark the thread as solved, but I am glad that everything appears to work now.
Related
I tried to root my N7 (2013) today and i ended up with a black screen.
I used these instructions, but got a bootloop on the Nexus Logo.
http://forum.xda-developers.com/showthread.php?t=2382051
So i tried to do a factory reset via TWRP, without luck (errors in twrp)
I couldn't even mount to get an ROM on the device.
Then i tried to do a factory restore with the *.img files from:
http://forum.xda-developers.com/showthread.php?t=2381582
Still no boot (only nexus logo).
So i tried to do a factory reset via the stock recovery.
After this all i got is an black screen.
First i thougt it was hardbricked. But i recognized that the device manager from windows 7 shows the device.
could not get adb to work while it shows "Android ADB Interface"
But if i turn it off and boot with volume down pressed i can get into bootloader ("android bootloader interface" at device manager)
And then i can connect via fastboot. but still nothing on the screen...
Is there more to restore than recovery/system/boot ? any display driver or kernel, so that the screen will start working again?
Otherwise i will go to the store and get me a new one.
Have you tried to reflash twrp? Or flash cwm instead? Mine didn't want to take twrp but flashed cwm without issues.
Sent from my SCH-I535 using Tapatalk 4
If you can get into bootloader (ie. fastboot sees the device), you should be able to at least throw the stock image back on there by running the included flash-all script provided by Google.
You should be able to replace the recovery as well. TWRP2 works nicely for me. Maybe download your copy again (http://techerrata.com/browse/twrp2/flo) and check the md5 has to make sure your download is good. Then flash with "fastboot flash recovery <*.img>". From there you can then install whatever you want.
As long as you can get into the bootloader, your options are many.
i just tried the flash-all script provided by google.
But still just a black screen...
I could flash a custom recovery, but i think this would not help the display problem.
if no one else have an idea for a solution i will lock the bootloader and bring it to the store tomorrow.
edit: got a new one. already rooted and with working twrp.
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.
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
Hi hoping someone can help, I accidentally wrote the wrong file to my system partition and am stuck at smartwatch 3 logo.
i tried pc companion and it tells be there "no software available for my device" all i can get to is fastboot mode stock recovery is gone too
I wrote twrp to it but as of yet have not been able to launch it. its running 5.1.1 os and i cant remember build number other than it began with an L
Please help
ZR1
if you read this and know i have no hope please let me know that too please
seems like if i had stock partitions images i could flash using adb i"d be good yes?? no?
I do not have time to help right now, but since you can get to fastboot, you are probably fine. Find the stock 5.1.1 recovery and boot to it. Then sideload the latest update. You will be good to go.
The command in a terminal window is...
Code:
Fastboot boot <stock recovery.img>
Alternatively, you can boot to twrp and install a twrp flushable zip.
Good luck.
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
zr1 said:
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
Click to expand...
Click to collapse
Have you tried Sony Companion to repair your watch?
If you were running 5.1.1, then the recovery you mention is for 5.0.1, so that might be the reason why you can not boot into it. See if you can find the stock recovery for 5.1.1
I have used the following method a couple of times now to get me out of trouble after playing around with my SW3
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
You can then use the stock recovery you already have and update via OTA files to get it back to the latest firmware or via Sony Companion.
I had the exact same issue after I did fastboot flash using corrupt system.img (which wasn't a snapshot that could be flashed but rather a tarball). Since you have TWRP installed you can confirm this by trying to mount system partition in recovery mode. After it fails, connect to recovery via adb and view latest kernel messages (dmesg). It should show something like "failed to locate ext4 filesystem".
If this is your case, you can use TWRP restore function to restore system from your TWRP backup. It will then erase the partition, mkfs.ext4 and write the files from tarball. This did the trick for me.
(If you don't have backup, try looking for downloads in other threads here)
Edit: Re-read your post. Since your TWRP is broken, try hotbooting it using fastboot boot new_boot.img (you can take it here)
ebones thank you thank you thank you
I had downloaded new_boot img already so im not sure what i was doing wrong but i did what you said and she booted right into TWRP i now have to sideload the right update.zip file and run it in twrp correct?
edit; having trouble sideloading wear-supersu.zip what is the correct command?
GOT IT!!! I installed stock rom from this thread http://forum.xda-developers.com/sma...rom-repacked-stock-rom-swr50-version-t2988087 through TWRP and it works cant thank you guys enough
Thanks ZR1
32gb variant (H790).
I tried most of the solutions I've seen on this subforum so far - including doing a full flash-all.sh command as well as the flashing of individual files into my system.
So far I've been able to do so using the stock images from Google (Android N). However, I can never get Recovery to boot and my phone will not boot past "Google." (Not even the colorful animations show).
I am not sure what I can do - I unfortunately got this phone via a 3rd party and not Google's Store, so I'm not sure if they would honor an RMA request (maybe if I said it was a gift they would relent?).
I was reading this thread: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 and realized that this might be my last alternative, but I'm a bit concerned about going through all of this without giving it one more chance having access to at least the bootloader screen.
Does anyone have any suggestions on what I might be doing wrong? Should I attempt to flash the latest Android 6.0 image instead?
Is your boot loader locked? How did you flash the stock images?
Reboot into fastboot, run the flash all, reboot back to your bootloader when it's done and it. These commands....
Fastboot format cache
Fastboot format userdata
Then restart the phone
Corrupted bootloader partition, your phone is little piece of brick. EXT4 is the motive, HAHAHA.
I lost a ****ty device like you too.
Now i learned: (IF IS EXT4 , NO!)
Sent from my XT687 using xda premium
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
I was able to reflash my rom again too, without errors, but the **** recused to boot up or boot recovery, your phone is death like the apocalyptical beast google inc!
Sent from my XT687 using xda premium
dcxgod said:
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
Click to expand...
Click to collapse
Can you get TWRP installed via fastboot and boot into that?
Sent from my Nexus 5X using Tapatalk
Use the lg tot file method to recover. It has worked for some.
Sent from my Nexus 5X using Tapatalk
Try to flash TWRP with fasboot and see if you can boot it. There's an actual problem with the last versions of TWRP (TWRP 3.0.2-1 and 3.0.2-2), where if you backup then restore an EFS partition you end up with a phone where it doesn't get past the Google Screen (or crashes in the first frame of the bootanimation), lk panic apparently due to EFS corruption.
If this is your case (derped restoring EFS like that) and you can flash and boot on TWRP, try to flash TWRP 3.0.2-0 and restore and old backup of EFS.
maybe same problem
I have the same problem.
Before i flash manually my phone into android 7(factory image) it was rooted and unlock bootloader. I locked the bootloader again and until here everything works fine. I flashed the stock recovery mode by TWRP. after that the phone won't boot android and stock recovery mode. everything was lost except the bootloader.
I tried lots of tricks but don't answer(sideload ota update, format cache and userdata). I tried to flash stock recovery or custom recovery but i couldn't because in the process the phone restart and restart again and again. Even doesn't work temporarily boot, custom and stock recovery mode and phone has no reaction.
I only have access to the bootloader.
Would you have any suggestion?
*ps: When phone is boot up just shows a white google logo and after that shows a green bot with red alert and a message(no command) . In this point phone restart suddenly and the same process is repeated.