Database Users

[HOW-TO] Safely Switch Back To Amon From Clockwork Recovery

********************DISCLAIMER********************
XDA-Developers & Myself are in no way responsible for any loss of information or damages to your device that may result from from the use (or misuse) of this process, though the process itself should not cause any such problems I feel it necessary to reinforce this fact.
********************DISCLAIMER********************​
-----Special Thanks-----
jcase
-For the methodology and providing the flash_boot and recovery image links in his eng bootloader thread-
Stick from IRC
-For his sacrifice and bringing this issue to our attention (R.I.P. sticks Eris)-
Suno and Mezy (also IRC)
-For being unwitting guinea pigs and verifying the process-
--------------------​
Overview:
It has recently come to our attention that a version of clockwork recovery included in rom manager can and has (sorry stick) caused problems for Eris. Clockwork (or more specifically this clockwork) does not play nice with the Eris and in at least one case has resulted in a corrupted userdata partition resulting in a brick. This is not necessarily going to happen in all cases but the possibility is there and as such it is better to be safe than sorry. If you are using clockwork without issue but wish to switch back to Amon Ra this thread can also help you meet that end.
NOTE: Users who cannot use Amon RA recovery due to trackball issues should attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)
What You Need:
Android SDK for adb - (alternatively this can be done PC-less but I will cover that later)
flash_image - www.multiupload.com/KS2JCAMGBH
recovery.img - www.multiupload.com/DXQVBXB93G
su - for root permissions
Astro or Root Explorer - (For PC-Less Only)
Terminal Emulator - (For PC-Less Only)
________________________________________________
This process is relatively straightforward and I'm going to cover both the adb method and the PC-Less method in case you for some reason can't get your device recognized by your system (or don't have access to one). I have also made this very detailed for inexperienced users.
The Process:
ADB Version-
1) Download both the flash_image & recovery.img files from the links above and place them in your android-sdk tools directory
2) Open a Command Prompt (or terminal) and navigate to the tools directory.
3) Connect your device (USB Debugging Must Be Enabled) and verify the PC can see the device - type:
Code:
adb devices
4) Push both flash_image & recovery.img to /data/local on your device:
Code:
adb push flash_image /data/local
adb push recovery.img /data/local
5) Change the permissions of flash_image:
Code:
adb shell chmod 777 /data/local/flash_image
6) Flash the recovery image to recovery:
Code:
adb shell
su /*this is for those who do not get dropped into a root shell automatically remember $ = user # = root */
/data/local/flash_image recovery /data/local/recovery.img
7) Give it a few seconds to run (just give it 10 or so seconds to be safe)
8) Issue the following to reboot the device into recovery mode to verify the flash took:
Code:
adb reboot recovery
PC-Less Version-
1) Download both files to your sdcard.
2) Use Astro or Root Explorer to move both of the files to /data/local (if you run into a read only error use this command in terminal emulator and try again)
NOTE: Root Explorer users can hit the rw/ro toggle button.
Code:
su
mount -o remount,rw /
If for what ever reason you either can't get Root Explorer and ASTRO is blocking you from navigating outside your SD go to terminal emulator and issue the commands:
Code:
su
mv /sdcard/download/flash_image /data/local
3) Open terminal emulator and issue this command to set permissions:
Code:
su
chmod 777 /data/local/flash_image
4) Still in terminal emulator flash the recovery image to recovery:
Code:
/data/local/flash_image recovery /data/local/recovery.img
5) When the prompt returns issue the command:
Code:
reboot recovery
Verification:
If you completed either method you should be greeted by a green text recovery menu. If so congrats Amon RA has blessed you with it's presence. go ahead and reboot system or flash a rom if you like.
If This was Helpful I only ask that you become an active member and contribute to the community in any way possible. The OpenSource community is what it is because of people like you giving freely of themselves for the benefit of the whole.

good stuff!
i've never used clockwork... and from my observations... GOOD!
in any case... this should help many users (i personally only recommend Amon).

What was the version the caused the issue? can't you also flash amons from clockwork in rom mgr then delete rom mgr? or would that not work? thank you.

midnight assassin said:
What was the version the caused the issue? can't you also flash amons for clockwork in rom mgr then delete rom mgr? or would that not work? thank you.
Click to expand...
Click to collapse
Not sure of the exact version as I don't personally use rom manager (kinda a manual guy) but I think it has been fixed in the most recent release. As for using Rom Manager to reflash I can't say for sure either but this method is pretty simple and already resolved two cases. I believe stick may have tried it he was in IRC with us for hours and we were bouncing everything we could think of at him but he got sig verification failure in a flash using it not knowing the issue and corrupted his userdata partition.
If there are any more questions I will have to answer them when I wake up because I'm nearly sleeping in my chair right now

thanks for the answer and putting this together. I know there are a lot of noobs like myself around here lately who may benefit from this and the time you put into it. thanks for makin it simple.

Thanks for the great post.
I just have to say theres an easier/alternate way to do it
1)download rom manager.
2)at the bottom of rom manager click flash alternate recovery.
[PC WAY]
As pointed out by bftb0 the below method will only work for those on HBOOT 1.49.2000 S-OFF bootloader. (those who flashed the original root rom)
1) download amon's recovery from this thread http://forum.xda-developers.com/showthread.php?t=648025
2) (if you don't already have the android sdk, download it) If your in Windows fastboot is included in the android sdk, if your in mac or linux go here http://developer.htc.com/adp.html and scroll down a bit, click download and move fastboot to your /sdk/tools folder.
3) with your phone connected to your computer and off hold the power and send buttons at the same time until fastboot comes up on the screen.
4) open cmd/terminal and cd to your /sdk/tools folder, and type in "adb flash recovery <path to amon's recovery>"(if your in linux or mac type ./ in front of fastboot).
5)reboot your phone.
I personally use clockwork recovery and have had no problems, though I do not suggest it for anyone. (unless your trackball is as messed up as mine is, I can't even scroll down in amon's recovery)

A couple of comments.
Stick's phone
A corrupted "userdata" (/data mount point) alone might prevent the OS from booting, but that should not effect the ability to start the phone in HBOOT, FASTBOOT, or RUU (oem-78) mode. I didn't sit in on the IRC, so maybe I'm missing something, but there really are only three things which will completely brick the phone:
- screwing up a flash of the (512 kB) bootloader
- screwing up the NVRAM area
- (maybe) screwing up the misc partition
You can screw the pooch in /boot, /recovery, /system, and /data (aka "userdata") - even all four of them at the same time, if you please - and your phone should still not be bricked.
If the bootloader can not be started (in any mode), then that is absolutely a bricked device; OTOH, if you can start up the bootloader in HBOOT mode, the only thing that would prevent you from re-flashing the Leak-V3/"Official" PB00IMG.ZIP file is corruption of either the /misc partition or NVRAM. None of the dev ROMs touch those areas though. So, it is very strange that someone using any custom recovery would cause corruption of those partitions. Is Stick really bricked?
I once corrupted my /system partition which caused it to be unmountable (in Amon_RA) by doing something dumb (twice!) - but re-flashing the entire ROM (HBOOT+PB00IMG.ZIP) overcame that and gave me an earlier starting point from which to re-root and recover via Nand. There is evidence, from looking at the string data contained within the bootloader that it knows how to recreate the partition tables in flash memory - presumably this would be needed if HTC shipped a ROM which needed more space in the /system or /data partitions than existed in prior ROMs. Whether it does that for normal PB00IMG.ZIP-style ROM flashing, I can't say - but there are hints that the HTC bootloader knows how to deal with flash memory in which the entire partition table has been destroyed.
PC-based method
Step #6 in the first set of instructions will not work for rooted (dev) ROMs which do not start adbd as root (that is, "adb shell" from the PC does not launch a root shell). Most dev ROMs do that, so perhaps this is a nit-picking point. If "su" is available in the ROM, prefixing the command with "su" should work, though - just as in the PC-less example.
Use of fastboot
homewmt should probably edit his post to add the disclaimer that using fastboot for flashing of recovery will only work for folks who gained root by flashing the "Root-ROM" (or post-installing it after root was gained), which gave them the 1.49.2000 S-OFF bootloader. None of the other bootloaders will let fastboot do this. I think it is important to mention this because a lot of the new rooters are using either the "One-Click" or "Dummies" (AF) methods to install a custom recovery - and so they never touch their bootloaders.
bftb0

So as long as you can get the boot loader up (power + volume down) then you can still use the 2.1 RUU (for those with HBoot s-on) to get the phone back working?
I think people assume that since the moded recovery image is fried that means the phone is bricked since you can't get into recovery on the phone to restore a backup.
Myself I've been using Clockwork Mod Recovery for 3 months without any problems and I've flashed a lot of ROMS and restored a lot of backups. Both using the recovery console and ROM Manager. I'll never go back to Amon's as I see no point and Koush is at least updating Clockwork on a regular basis.

bftb0 said:
A couple of comments.
Stick's phone
A corrupted "userdata" (/data mount point) alone might prevent the OS from booting, but that should not effect the ability to start the phone in HBOOT, FASTBOOT, or RUU (oem-78) mode. I didn't sit in on the IRC, so maybe I'm missing something, but there really are only three things which will completely brick the phone:
- screwing up a flash of the (512 kB) bootloader
- screwing up the NVRAM area
- (maybe) screwing up the misc partition
You can screw the pooch in /boot, /recovery, /system, and /data (aka "userdata") - even all four of them at the same time, if you please - and your phone should still not be bricked.
If the bootloader can not be started (in any mode), then that is absolutely a bricked device; OTOH, if you can start up the bootloader in HBOOT mode, the only thing that would prevent you from re-flashing the Leak-V3/"Official" PB00IMG.ZIP file is corruption of either the /misc partition or NVRAM. None of the dev ROMs touch those areas though. So, it is very strange that someone using any custom recovery would cause corruption of those partitions. Is Stick really bricked?
I once corrupted my /system partition which caused it to be unmountable (in Amon_RA) by doing something dumb (twice!) - but re-flashing the entire ROM (HBOOT+PB00IMG.ZIP) overcame that and gave me an earlier starting point from which to re-root and recover via Nand. There is evidence, from looking at the string data contained within the bootloader that it knows how to recreate the partition tables in flash memory - presumably this would be needed if HTC shipped a ROM which needed more space in the /system or /data partitions than existed in prior ROMs. Whether it does that for normal PB00IMG.ZIP-style ROM flashing, I can't say - but there are hints that the HTC bootloader knows how to deal with flash memory in which the entire partition table has been destroyed.
Click to expand...
Click to collapse
Yes stick is really bricked. He had access to the recovery but got a sig failure which terminally corrupted his userdata partition and the only option available to him was fastboot which would throw a sig failure at any attempt to flash over (even tried PB00IMG and RUU at the end)
NOTE: Good catch on #6 I edited the OP to drop into a shell then su in.
kzoodroid said:
So as long as you can get the boot loader up (power + volume down) then you can still use the 2.1 RUU (for those with HBoot s-on) to get the phone back working?
Click to expand...
Click to collapse
This is inadvisable as stick tried the RUU which is what killed off his ability to enter hboot

edge.thefly said:
Yes stick is really bricked. He had access to the recovery but got a sig failure which terminally corrupted his userdata partition and the only option available to him was fastboot which would throw a sig failure at any attempt to flash over (even tried PB00IMG and RUU at the end)
Click to expand...
Click to collapse
That is truly bizarre. I don't know what Clockwork does for checks, but Amon_RA performs (in the verification step) the equivalent of a "jarsigner --verify" operation: it computes the SHA1 hash of every last file in the .zip archive, and compares those sigs to the manifest. If even a single file is wrong, it won't proceed to the install, but just bombs out on a verification failure. The upshot of that is - in the Amon_RA (or stock recovery update.zip) case - it is literally impossible to install a corrupted ROM file.
In the case of HBOOT and PB00IMG.ZIP installs, a "whole-archive" signature is performed - the individual images are not inspected, but that doesn't matter: if you touch a single bit anywhere, even in the .zip file directory, that verification step will also fail.
So - in both of those examples, the only way to burn something wrong onto the phone is if the files get corrupted internally to the phone, after they have already passed signature checks - or if they are read off the SD card differently between the verification pass and the install pass!
Do you know if Stick has a S-OFF bootloader? (i have a tricky idea, if so) I suspect he doesn't, because if fastboot passes a privilege check, I don't think there are ever any sig checks performed by the phone when the bootloader is in FASTBOOT mode - all you have to do is have a S-OFF bootloader, and you can write total crap to the phone.
bftb0

I'm almost certain he had S-ON but hes not around right now so I can't verify.
I should also note that while he can still power on the device he only has fastboot access it wont even get into bootloader or recovery at this point.

thanks edge this work like a charm

edge.thefly said:
I'm almost certain he had S-ON but hes not around right now so I can't verify.
I should also note that while he can still power on the device he only has fastboot access it wont even get into bootloader or recovery at this point.
Click to expand...
Click to collapse
Ugh. Vol-Down won't get him from FASTBOOT-USB mode to HBOOT?
Sux.
I was going to suggest - only if he had the S-OFF (1.49.0000) bootloader - that he could boot to a recovery image without ever flashing it to the device, e.g.
Code:
[B]C:\blech> [COLOR=green]fastboot boot recovery-RA-eris-v1.6.2.img[/COLOR][/B]
Even if he had S-OFF, and can get a recovery boot up on it's legs, it might still be a long uphill climb if e2fsck/mke2fs can't repair/rebuild /dev/block/mtdblock5 (for instance if the mtd device is so corrupted that the partition map got thrashed).
But that route is a no-go if he has a S-ON bootloader.
bftb0

What's the difference between Amon and Clockwork?

Good question. I personally dont use clockwork but...
the navigation interface is different (uses volume keys to select instead of trackball)
Amon_RA is far more tested and reliable on Eris
and of course the general consensus that clockwork should NOT be used on the eris.
NOTE: I am sure there are other internal differences someone like bftb0 or koush would be more apt to give a detailed explanation.

edge.thefly said:
Good question. I personally dont use clockwork but...
the navigation interface is different (uses volume keys to select instead of trackball)
Amon_RA is far more tested and reliable on Eris
and of course the general consensus that clockwork should NOT be used on the eris.
NOTE: I am sure there are other internal differences someone like bftb0 or koush would be more apt to give a detailed explanation.
Click to expand...
Click to collapse
I've been using clockwork for a while now... I haven't had issues yet. What kind of problems have people had with this, anyway? There is an option in rom manager to flash back to Amon ra...
Sent from my Buuf Froyo using XDA App

The usual, failed flashes failed nandroid backups i heard something about a random reboot issue but that could be unrelated and of course the one case of corrupted partition/inability to get into hboot or recovery resulting in a brick.
I will note some people are using clockwork without issue and for them great but it is not advisable on the Eris at this time though I do realize some people have trackball issues and have to in which case best of luck to those few brave souls.
NOTE: If you have trackball issues i advise you to attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)

edge.thefly said:
The usual, failed flashes failed nandroid backups i heard something about a random reboot issue but that could be unrelated and of course the one case of corrupted partition/inability to get into hboot or recovery resulting in a brick.
I will note some people are using clockwork without issue and for them great but it is not advisable on the Eris at this time though I do realize some people have trackball issues and have to in which case best of luck to those few brave souls.
NOTE: If you have trackball issues i advise you to attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)
Click to expand...
Click to collapse
maybe you should post this on OP the trackball issue that is

so...I'm not at my normal computer(and I can't get Root Explorer because my card always screws up when it converts from US to any other currency) and am trying the On-Phone method via Astro. The issue I'm having is I cannot get it to show me the /data/local folder. I can't find any tweak for it in settings or anything. There's no read only error or anything like that, so I don't think that mount command in the first post will help very much. I'm fairly new to Android hacking, so this could easily be something I just don't know yet. My gut says it's a permissions thing, and that since Astro is meant for normal users it just doesn't set itself to show the restricted stuff by default.
So I guess does anyone know how to make this folder appear in Astro?
(I've been meaning to change back to Amon_Ra for a while ever since I noticed that RomManager deleted the other recovery program. Just can't trust something that does that.)
[edit] tried the command to remount as a rewritable et all that jazz(mount -o remount, rw /) and no change.

Do you have Superuser installed? My astro sees those extra files and it isnt in my Superuser permissions list.
However if you cant get past this issue go ahead and use the terminal emulator to perform the move.
Code:
su
mv /sdcard/download/flash_image /data/local

not sure what to call this problem

Ok, so rooted (razorclaw) ics 4.0.3 tf-101.
fully charged
when powering on, stalls at the eee pad screen. (sounds like a boot loop, but it doesn't go to recovery)
Cold boots fine, works great, no random reboots (yet)
Will not boot into recovery, has ww_epad-9.2.1.11-20120221 bootloader
stalls at "booting kernel image" I assume there is no recovery installed.. Tried to get cwm onto it but I cant get apx working, it wont recognize the device at all.
I didn't root it, someone else did and I have no idea what recovery is/was on it.
I bought the tablet used, and would like to fix it.
Once recovery is installed would this boot normally.
Ive been searching on here/transformer forums for a couple weeks and have thought I found the answer multiple times. I need a push in the right direction.
Tried to fix this for a while a couple months ago when ics first launched and gave up. (did the same thing when It had honeycomb on it)
edit::
the only solution I can come up with is using NVFLASH to try to restore it. Working on this right now, hopefully this is a sbk1//not working, cant seem to get the computer to recognize the device in apx mode. (win 7)

If your TF is rooted, you may want to give the RecoveryInstaller app a go.
http://forum.xda-developers.com/showthread.php?t=1346180&highlight=recovery

I forgot to add that I have tried that (tried it again just now.. twice, just incase it happened to work but it didnt.)
following these instructions:
"click the button and the Superuser app will ask for permissions. Then the tablet reboots and to enter it you have to keep the Volume - key pressed and when it the TF writes "Booting into recovery" on the screen press Volume + once"
also tried it without holding volume buttons when it reboots.
When I run it, and click the button to install recovery, it grants superuser permissions and then reboots, sticks at the eee pad screen again and it stalls at booting recovery kernal image. Anything Im missing?

Reflash a recovery image .sos and bootloader .ebt if the recovery image doesn't work.
Download any cwm flashable recovery and extract it twice to get the recovery blob out:
put the recoveryblob on your computer somewhere.
adb push C:\Location\Of\Blob\blob.blob /sdcard/
adb devices
adb shell
su
dd if=/sdcard/blob.blob of=/dev/block/mmcblk0p4 -
reboot
--
this should fix recovery.

Thanks for breaking that down! Im going to try this once I can get adb working.
Going to try another computer now. I'm beginning to wonder if the usb cord for my tf has gone bad.

You can do it on your tf too, via terminal emulator app since you can coldboot.
Download blob somewhere on tf, download term em. and run this part:
su
dd if=/Path/to/recoveryblob of=/dev/block/mmcblk0p4 -notice path/to is where you placed on Tf's INTERNAL storage.
reboot

Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"

Is BusyBox installed?

That it is, just reinstalled 1.20.. should i use a different version perhaps?

Ro.secure set to 0?
see the guide to flashing an insecure boot.img if it isn't, this may be the problem.
if you're on a rom this isn't the issue..
Try a different version of BB I suppose

simplywinter said:
Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"
Click to expand...
Click to collapse
Suggest you try method 3 in the following post.
http://forum.xda-developers.com/showthread.php?t=1622628
It does not require rooted TF. If you do everything right but still not working, you may have a faulty device.

^^ My peri runs that method, so that didn't work. :/
I think borked hardware, try NvFlash

just did this
ls - l /system/xbin/su
getprop ro.secure
returned: 0
So it is indeed set to 0.
NVflash.. well I would do that if I could get the usb connection to the computer working.. Still trying that.
Also, kokopopz
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.

simplywinter said:
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.
Click to expand...
Click to collapse
The following guide will be useful for setting up ADB.
http://forum.xda-developers.com/showthread.php?t=1071584
For the USB driver, you can try the naked driver.
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked
Note: I am a linux user. I set up ADB on my linux box. I did not try the above myself. I just came across them. They maybe useful to a Windows user.

Windows drivers are finicky, make sure you totally uninstall and reinstall them too. Took forever to get right on my computer.

no go with windows. I still cant seem to make this work... I have ubuntu on my laptop though. Can I even do this on Ubuntu? its 11.04

You can do this with Ubuntu no drivers required, just pick up the Nvflash wheelie for linux and get yourself a reflashed ROM.
Also you can still do this on TF. I had a very similar issue that I was able to fix by using Rayman's Blobtools (you can pickup blobunpack for windows in my bootsplash screen change guide).
Download the latest stock ROM for your device, and extract the 'blob' file out of it.
Put the blob in the same folder as blobunpack.exe, then open a command prompt and cd to the directory, then run:
Code:
blobunpack blob
After that you will see that there are now many blobs, one of them is called blob.EBT, this is your bootloader blob. What you want to do is copy that to /sdcard/ on your tf via mass storage or 'adb push blob /sdcard/' (You Have to remove the .ebt extension, it's just there as an ID, so it should just be 'blob')
Once that's there flash it through the staging partition (In terminal emulator or adb shell):
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
Then it shouldn't get stuck at the Eeepad screen anymore!
If it still does, you might have that weird problem where nothing flashed through staging partition sticks, so you'll need to run Roach2010's fix.

after trying that.. twice. It doesn't seem to stick. Roaches 2010 fix it is, searching for it right now.

If you can get adb shell access (I'm assuming yes) PERI has the fix bootloop option. Otherwise run roaches fix AFTER flashing a new recovery and EBT partition but BEFORE rebooting.

how do i run roaches fix. i Dont understand that part. I understand the rest though.

Boot Loop after update -multiple attempts shows different screens after 2hours

Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks

erico.albino said:
Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
Click to expand...
Click to collapse
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.

v12xke said:
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
Click to expand...
Click to collapse
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.

erico.albino said:
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
Click to expand...
Click to collapse
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E

v12xke said:
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
Click to expand...
Click to collapse
thanks for all the word, V12...!
dont have english as my mother language is complicated. specially when you need help on some topics that is not available or dont have good places to go here! (brazil).
anyway, i'm following your first suggestions, and i'm going to share the results soon.
the nexus screen on recovery mode shows:
Console:NULL
Battery OK
Device is LOCKED
Qfuse status ENABLED
off-mode Chager ENABLED
download mode DISABLED.
on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop.
the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
thanks a lot for the help, bro!
:good:

erico.albino said:
thanks for all the word, V12... Device is LOCKED.... on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop. the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
Click to expand...
Click to collapse
Because your bootloader is locked, the only real option is to sideload an OTA from the stock recovery. Not possible to flash a full image. You will need to find an OTA that is newer than your current build. If it won't boot, try a factory reset and boot again. If that doesn't work, try fastboot formatting (only) userdata and cache partitions and try the OTA again.

ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out

erico.albino said:
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
Click to expand...
Click to collapse
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.

v12xke said:
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
Click to expand...
Click to collapse
-Factory reset/wipe data goes OK. if i restart the system, it back to bootloop.
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(

erico.albino said:
-
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
Click to expand...
Click to collapse
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?

v12xke said:
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
Click to expand...
Click to collapse
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
R:\Desktop\nexus\Fastboot\Fastboot>adb devices
List of devices attached
84B7N15C21000379 host
R:\Desktop\nexus\Fastboot\Fastboot>adb sideload angler-n4f26o-factory-c53f0a50.z
ip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
here some images: https://goo.gl/photos/zLZ9CEh1dtpgPJf17

erico.albino said:
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
Click to expand...
Click to collapse
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler

v12xke said:
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
Click to expand...
Click to collapse
forget the long post, i was missing the quotes on the image file name.
i'll run your suggestion now...

erico.albino said:
i cant access internal storage. so i cant run step 1 on that page.
Click to expand...
Click to collapse
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.

v12xke said:
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
Click to expand...
Click to collapse
thanks at all for all the help. unfortunately, after successfully sideload the OTA file, boot loop still here

Sorry to hear that. See if you are allowed to fastboot FORMAT userdata and cache from your PC and try the OTA again. You may get an error formatting userdata. Remember, next week brings a new March security update, and if you haven't given up on your device you can try to flash that OTA when it is posted by Google. You can now get back to your math homework...
Before you go, does your Recovery screen still say NRD90T or did it update to N4F26O?

i can see 7.1.1 N4F26O on recovery screen.
you can bet i will not git it up on this, lol. it was a very good deal based o the value of the device here in brazil.
i'll keep this post up to date about this and let you know about any news.
thanks again for all the help bro, much appreciate it!
cheers from brazil!

erico.albino said:
i can see 7.1.1 N4F26O on recovery screen.
Click to expand...
Click to collapse
March Security Update OTA's posted on Google. Boom!

v12xke said:
March Security Update OTA's posted on Google. Boom!
Click to expand...
Click to collapse
no chanfes unfortunately

There is any specific variant of nexus that can be down for this kind of brick?
Sent from my iPhone using Tapatalk

How to backup data from a 1+5 with broken touchscreen ?

Hello guys,
Unfortunately I broke my 1+5's screen recently. I can barely see things on the bottom half of the screen and the touchscreen is not responding correctly so I can't unlock my phone anymore (cuz password is needed :good.
I would like to ship it back to 1+ factory so they can repair the screen but they will factory reset my device, this is why I'm requiring your help : I want to get some files which are inside my phone, but I don't know how to do it. I tried some things :
I have access to adb recovery but I'm unable to get su working : adb shell can't mount anything and ls shows nothing in data sdcard and so on.
I have access to adb unauthorized (unlock screen) and I tried to push adbkey.pub into /data/misc/adb/adb_keys with no success, still unauthorized.
In these 2 states adb pull /sdcard does nothing.
Any ideas ?

any solution?
gosuleaf said:
Hello guys,
Unfortunately I broke my 1+5's screen recently. I can barely see things on the bottom half of the screen and the touchscreen is not responding correctly so I can't unlock my phone anymore (cuz password is needed :good.
I would like to ship it back to 1+ factory so they can repair the screen but they will factory reset my device, this is why I'm requiring your help : I want to get some files which are inside my phone, but I don't know how to do it. I tried some things :
I have access to adb recovery but I'm unable to get su working : adb shell can't mount anything and ls shows nothing in data sdcard and so on.
I have access to adb unauthorized (unlock screen) and I tried to push adbkey.pub into /data/misc/adb/adb_keys with no success, still unauthorized.
In these 2 states adb pull /sdcard does nothing.
Any ideas ?
Click to expand...
Click to collapse
did you send it ?did they make factory reset to your phone?did you find any solution?

custom recovery ...
custom recovery have adb enabled, so boot twrp (it will ask for your password to decrypt data if their is encrypted, unfortunately : if so, I don't know sorry).

Nothing2Do.eu said:
custom recovery have adb enabled, so boot twrp (it will ask for your password to decrypt data if their is encrypted, unfortunately : if so, I don't know sorry).
Click to expand...
Click to collapse
You can decrypt the /data partition via adb, without using the touch screen.
The command you need is there:
https://forum.xda-developers.com/showthread.php?t=2484380
You can then adb pull /data/media to get your data.

[guide] Recover data from unencrypted S7 with broken screen

Hi,
I got help from ivan_meler and I couldn't find the steps here, so I thought I would post them for reference.
If you have an unencrypted S7 with a broken screen, you can get your data back from adb commands in a terminal (tested on my phone with TWRP, but I guess it should work with other recoveries)
The trick is to get it to boot in recovery mode, which is not easy if the phone is on (which it will most probably be, since you can't turn off the phone without the screen). To do that, press volume down + power for long enough to force a reboot, and, as soon as the phone reboots change to volume up + power + home.
That will get it in recovery.
After that, your phone should be recognized with $ adb devices as recovery instead of unauthorized. Then, $ adb shell mount will mount the filesystem in an adb shell, and you can browse the filesystem with $ adb pull /sdcard/.... to get your data back ! Most files will be in /sdcard/ or /data/
That said, encrypt your phones, and keep backups, that's a better way to go !