Develop Bugs

[Q] Explanation Needed (Post-Root to Un-Root)

Okay, so I've just rooted my Nexus 7 tablet after being told a custom ROM would fix my GPS issues with my N7v2. I'm familiar with the rooting process, having done it to my HTC One. I rooted it successfully, installed the SuperSU and TWRP. Everything went smoothly, and then I realized, only minutes later, after browsing XDA, that Google JUST released an OTA to fix the issues.
So I browsed around and found this post: http://forum.xda-developers.com/showpost.php?p=44888268&postcount=97&nocache=1&z=675614455249160
I followed the instructions. I opened a CMD in the correct folder and ran the flash-all.bat. It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive. When I finally figured out how to use 7zip (never had a use for it before now), I ended up with a folder that looked like this (which is where I ran the CMD):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see the image-razor-jss15q.zip was still inside that folder. I did not unzip it because I didn't know if I was supposed to or not.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
2. If "no" to 1, what do I need to do to fix it?
Edit: It appears I've put this in the wrong section, I apologize. I'd appreciate it if a moderator moved it for me. Thanks!!

Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly

Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
http://forum.xda-developers.com/showthread.php?t=2404833

sfhub said:
Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly
Click to expand...
Click to collapse
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.

Username invalid said:
Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
Click to expand...
Click to collapse
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.

Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Edit: Just wanted to point out, this is obviously for those running stock ROM.

railed said:
Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Click to expand...
Click to collapse
Hey cool, thanks for that! I'm sure people will find this useful!

wolfbuck22 said:
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.
Click to expand...
Click to collapse
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
wolfbuck22 said:
It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
Click to expand...
Click to collapse

Username invalid said:
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
Click to expand...
Click to collapse
I only tried the flash-all.bat once. It ran with the errors. Tablet still worked even with errors. Had regular recovery back and everything.
Though, I wasn't satisfied so I went back and unzipped those files to the main folder and re-ran the flash-all.bat again. That time it gave me a different set of errors but the tablet seems to be working just fine so I'm not exactly worried about it.

wolfbuck22 said:
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.
Click to expand...
Click to collapse
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them

sfhub said:
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them
Click to expand...
Click to collapse
Great. Thank you so much, everything appears to be working fine at this point.
I may venture into the custom ROM realm later but for now I'm quite happy with the Nexus 7's stock ROM (never had a pure Android device before).

[Q] stuck on splash screen, can't enter recovery or unlock boot loader

The title says it all.
It was fine yesterday, I came home today and it was stuck on the splash screen. Cant enter the recovery to factory reset, and it wont let me unlock the boot loader. But I can still access the fastboot mode. Any tips?

Anyone have any ideas what might be wrong?

fielddb said:
Anyone have any ideas what might be wrong?
Click to expand...
Click to collapse
use fastboot to restore a stock image.

This is what I get when I try to wipe the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Bump
Sent from my HTC One using xda app-developers app

Someone must know something

I saw this on one tablet. My guess is there is some emmc corruption. I was able to get around it by doing the factory flash over and over until it eventually went away, possibly because the emmc firmware locked some bad sectors out.

so my best bet would be to download the factory image from Google and spam the flash-all.bat file?

Looking back at my notes, the error was like yours and prevented unlock, which made flashing factory impossible. According to my notes I booted into recovery and wiped a few times.
Can you be more specific with the part about not being able to enter recovery?
What buttons did you press and what were the results?
Also have you rebooted your PC?

When I press enter recovery. The device goes to the Google splash screen and freezes.
And I have rebooted my PC, as well as trying two different PC with different OS's

fielddb said:
When I press enter recovery. The device goes to the Google splash screen and freezes.
And I have rebooted my PC, as well as trying two different PC with different OS's
Click to expand...
Click to collapse
Can you try
fastboot erase userdata
fastboot erase cache
fastboot oem unlock

D:\Program Files\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 411.474s
D:\Program Files\Android\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 541.982s
D:\Program Files\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 315.871s
D:\Program Files\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
The device gets locked up here

I think your emmc is corrupted, possibly affecting the partition info.
There isn't a whole lot of info on how to recover from this.

sfhub said:
I think your emmc is corrupted, possibly affecting the partition info.
There isn't a whole lot of info on how to recover from this.
Click to expand...
Click to collapse
I'll just send it through RMA. Since it's not unlocked or rooted.

I just ran into the same issue. I think my memory is dead but I am in slightly deeper poop. I posted on another forum since XDA was down for a bit but here is what I wrote.
Hi everyone! My device just ran into some trouble and I couldn't find any other thread on here to help out so I am starting a new one. Here is what happened:
I was sitting on the computer and at the corner of my eye I saw my Nexus 7 (2013) reboot. After which it got stuck on the Google logo. Tried rebooting multiple times but still stuck at the logo (not the X screen but the screen that says Google in white letters). I had flashed TWRP so i decided to just factory reset the device. That was a no go as TWRP hangs on TEAMWIN screen.
At this point i said 'fuggit' and decided to restore factory images. I downloaded the two available images from google and both fail to restore as the flash-all throws up an error saying that it can't write to flash memory. I tried manually flashing with fastboot boot, recovery and system and got the same message.
Then I remembered that locking and unlocking the bootloader forces the factory reset so I decided to do that. While locking was successful I was unable to unlock the device as it tried to erase user data but it gets stuck with the message: 'erasing userdata...' and it doesn't go any further.
At this point I am out of ideas. I called a Google rep and tried to talk to a person but the representative I got was strictly working by the script and after I explained the issue I had (pretty much verbatim on whats above) she asked me if I had tried to reboot the device and then proceeded to ask me to reboot again. After we went through all the steps she was stumped and told me to contact manufacturer. Given that I had flashed a custom recovery and my bootloader is now locked and I can't flash stock recovery what are my options? Any ideas?
Click to expand...
Click to collapse

I called Asus and spoke to a rep that seemed to know of this issue and told me that the memory module might be bad. I am sending the unit in to be serviced or replaced. I'll post when I have any more info on this.

h77ps said:
I called Asus and spoke to a rep that seemed to know of this issue and told me that the memory module might be bad. I am sending the unit in to be serviced or replaced. I'll post when I have any more info on this.
Click to expand...
Click to collapse
Hey I have the same issue here... did you fix the problem or what happened?

h77ps said:
I called Asus and spoke to a rep that seemed to know of this issue and told me that the memory module might be bad. I am sending the unit in to be serviced or replaced. I'll post when I have any more info on this.
Click to expand...
Click to collapse
i have the same problem! just made a "ticket" about it on their website. unable to call support bc they're closed at the moment. did they replace your device?

Same problems for me now
Yesterday, touchscreen stopped responding, then a reboot and now it is stuck @ "Google Logo"
I tried flashing the factory image without wipe, then with wipe, then with erase + update + wipe. But i had no luck. Device seems to be dead. I will try to get a new N7 from the shop I bought it.

I've been battling this same issue for a couple days. Weird, have had mine since last August(!) with no real problems. Rooted but pretty much running stock since day one. Suddenly started being unresponsive after flashing CleanRom (not that I blame ROM), was able to get to TWRP to restore a stock backup, but then again no touchscreen response. Tried to reboot and now all I ever get is GOOGLE screen with unlocked bootloader symbol. I can boot to bootloader screen and have tried every imaginable way to wipe and flash stock again to no avail. Can't boot to recovery, nothing. Its ridiculous, but I'm screwed so far. No way I can return it now...unless maybe I relock bootloader and ASUS will do something for me. Please keep us posted any of you who resolve this!

FED-Patcher for the Robin (ForceEncrypt Disable Patcher)

This tool was created for the nexus 9 by @gladiac to get rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
This is a better implementation then having to manually patch every boot.img especially once custom aosp roms come along because cyanogenmod will have force encrypt enabled just like the nexus's. It also makes it easy to patch ota boot.img's by yourself.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 9 (aka flounder) it's the CPU's task. Even though the nexus 9's CPU has 2 pretty fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an old discussion about this topic in cyanogenmod's gerrit. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
What do I need to make this work?
A supported device (Your Robin)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like stock or cyanogenmod)
A recovery that includes busybox (TWRP)
How do I use it?
Make a through, conservative backup of your data if there is any on your device.
Go into your recovery (TWRP)
Flash fed_patcher_robin.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on the first ota for example and you used the patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Download:
https://www.androidfilehost.com/?fid=24459283995312942
Credits
* @gladiac he did all of the work for this i just edited a few things for it to work on the robin Link to his original thread

Mine just in case

Hi @deadman96385,
I could have added "ether" support to the generic version of FED-Patcher which is available at [http://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422]. However, I don't mind you having your own version here in the Robin-forum . I was planning to put FED-Patcher up on github to give it a more "open" touch and enable others to do modifications to it anyway. Anyhow, do you mind if I merge your changes in the generic version?
cheers glad

gladiac said:
Hi @deadman96385,
I could have added "ether" support to the generic version of FED-Patcher which is available at [http://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422]. However, I don't mind you having your own version here in the Robin-forum . I was planning to put FED-Patcher up on github to give it a more "open" touch and enable others to do modifications to it anyway. Anyhow, do you mind if I merge your changes in the generic version?
cheers glad
Click to expand...
Click to collapse
Sure go for it

Works great, thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Robin using XDA-Developers mobile app

So I have twrp and I have to wipe internal storage as its prompting for a password.
Do I wipe internal storage, boot into the phone. Download this. Flash, wipe phone again?
For some reason adb in twrp isn't working for me to push files

Is this working with 7.0? Thank you.

hololodilolo said:
Is this working with 7.0? Thank you.
Click to expand...
Click to collapse
No it is not. The only way to disable forced encryption on official Nougat for the Robin currently is with SuperSu and Magisk.

Saythis said:
No it is not. The only way to disable forced encryption on official Nougat for the Robin currently is with SuperSu and Magisk.
Click to expand...
Click to collapse
Not true. I've used this FED Patcher with stock 7.0 and 7.1.1 and it works fine. I've never had to use Magisk.

Phone won't boot past Robin logo once i flash this
I can't figure out why this isn't working for me since no one else seems to be reporting my problem..
I'm running Nougat 7.1.1 (Build N108).. When i flash this mod, it seems to flash correctly, but the phone never goes past the nextbit logo.. And yes, of course i've tried wiping, both before and after.. I've tried after a fresh install without booting at least once. I've tried after a fresh install after its booted at least once, then wiped, then flashed, but no go.. I've tried everything i could think of, but it just won't boot..
I bought a new phone, booted once and it asked to download updates (which let me know it didn't come with N108)..
So i rebooted into fastboot, unlocked it, and flashed the factory N108 build.. Everything worked fine and my phone booted into Nougat
So i rebooted into recovery (which was factory), wiped the phone, rebooted into fastboot and flashed twrp 3.1.1, and allowed it to replace the recovery img on the system partition so it wouldn't be replaced upon future reboots. i rebooted the phone and it worked fine..
So yes, everything, fastboot, twrp, and a functioning up to date Nougat works fine, but flashing this before or after a wipe, or even a "wipe>flash>wipe>reboot" just hangs at the robin logo forever (well, at least an hour.. i tried letting it sit thinking i wasnt waiting long enough)..
Am i mistaken in thinking that ONLY data, and the "sd-card" are encrypted? Should i wipe everything except the boot partition after i flash this, and then reflash every partition except boot?
Also, possibly related, is when i preform a factory reset WITH the newest twrp, it also hangs at the robin logo.. But a wipe with the factory recovery image works fine.. So, with all the flashing ive been doing between trying to get this to work, and then recovering the phone from a semi-bricked state, ive modified the "flash-all.bat" so that when i recover my phone, im only reflashing boot/system/recovery.. and different combinations of those images as ive been trying to pinpoint the problem.. but obviously, im out of ideas..
help?
EDIT: I also just installed linux and setup adb/fastboot, so i could start pulling apart boot images and manually modifying the changes, reflashing just the image, etc (since all my dev knowledge is on a linux system), but im having some issues with working wifi drivers on this machine.. so i havent tried to dissect the boot image manually yet.. just to eliminate potential issues, simply because im desperate).. I just want to get this mf unencrypted :'(

NEVERMIND!!
I'm really not sure why it didn't work, at all, following the description and 100 other variations of it.. Maybe there's a glitch in twrp 3.1.1-0? But this is what worked for me when all else failed.. And a description of my setup.. JIC anyone else has this problem one day..
Unlocked Bootloader
-Flashed the factory stock image N108 to bring everything "back to 0"
-Booted 1 time, jic boot.img was setting up any mount points or modifying itself after 1st boot..
( I did that because if you install twrp 3.1.1-0 right after flashing the factory 7.1.1 (N108) images, and boot into recovery without booting at least 1 time into the rom, it errors when trying to do a factory reset because it claims it cant find any of the mount points.. it also prevented me from pushing fed-patcher to the phone
-After its fully booted, i reset into recovery (factory recovery still) and wiped it
-I then rebooted into fastboot from recovery and flashed twrp 3.1.1-0
-i kept system read only for now since the next step would undo any changes, and then flashed fed-patcher
-i rebooted from recovery back to fastboot and reflashed the system image with the wipe flag "fastboot -i 0x2c3f -w system system.img"
-reboot.. success!! (keep in mind that you havent reinstalled twrp yet)
Basically, all i did different here when compared to the original instructions, and the other several hundred things i tried, was the "fastboot -i 0x2c3f -w system system.img" command after patching the boot image.. Which wiped system, and also wiped "everything else" with fastboot instead of twrp..
So again, i'm not sure if i was messing up by not wiping the system partition, or if it was a bug in twrp 3.1.1-0.. but im gonna play around some more..

soulife said:
NEVERMIND!!
..
So again, i'm not sure if i was messing up by not wiping the system partition, or if it was a bug in twrp 3.1.1-0.. but im gonna play around some more..
Click to expand...
Click to collapse
First - For TWRP to work correctly you need a pin setup for unlock. That way fastboot boot twrp.img will boot fine and allow you to decrypt with the pin you just set. If you want to force it anyway. You can format data (wipe everything) followed by push TWRP and magisk and flash the force-encrypt disabled boot image.
Second. After decryption you can push anything fed-patcher included.
Third - there was however another option. You could very well have flashed the dm-noverity and force encrypt disabled ROM also in this same section
Lastly I'd exercise caution on this device with the -w command. Some of the partitions are not clearly visible and many a user has had to replace their robin.

valhallen.282 said:
First - For TWRP to work correctly you need a...
Click to expand...
Click to collapse
Thanks man, i'll keep that in mind for if i ever decide to turn encryption on again and want recovery to play nice with the rom..
The problem i was having pretty much had everything to do with the fact that this is the first device i've owned with encryption enabled, and so i didn't have a clear (enough) understanding for how it worked.. and i still don't completely. But this particular problem was because i thought that the encryption was file based, which as you already know, it is not. It's closer to a filesystem based encryption, which is why i needed to reformat for it to work instead of just factory resetting or basic wiping..
I suppose i could have let it boot completely and setup a pin, and then formatted and removed encryption, but it seemed redundant.. I mentioned how reflashing the system image with the wipe flag fixed my problem, which i now know is because it reformatted the data partition as well, which i could do from within twrp (i think).. If not, the -w fastboot flag should be fine. I appreciate your word of caution though, but when you use the batch script provided by Nextbit to flash your device, it uses the -w flag after it flashes everything else. So it should be fine to use if twrp cant reformat an encrypted userdata (which i have no idea why it wouldnt work, but i feel like i tried that already)..
ill know more, and update my post for other new users once i start using other roms.. Which might be sooner than later since substratum wont change my notification shade on stock, and its too damn bright. Which is bugging the crap outta me. I'm using a systemless substratum legacy magisk module atm, maybe thats my problem, or maybe i need oms support, i donno yet.. Nougat is new to me, im learning its new features as i go..

Unable to do the initial fastboot boot "twrp.img" file

Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)

https://imgur.com/a/w4DWq
If the attached images do not load, then I have uploaded the images on Imgur

did you unlock the critical partition as well? Maybe that's the problem?

anthony.moua95 said:
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
Click to expand...
Click to collapse
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??

Badger50 said:
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Click to expand...
Click to collapse
I am on 8.1 and updated it via OTA.

anthony.moua95 said:
I am on 8.1 and updated it via OTA.
Click to expand...
Click to collapse
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:

Have you tried a different cable yet?

Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Oh geeze, this is something I can't be bothered with at the moment with my current situation (living and working in Thailand). I appreciate all the input that you have given on this thread though! I think I will just keep my phone where it is at now then (unlocked bootloader, 0 modifications, 8.1.0). But I will continue to follow and see if there are any definitive or streamlined solutions to this potential problem in the (near) future. Adaway and Viper4Android are still very important enough reasons for me to root.
I will also add that when I tried rooting via the magisk method (patch_boot.img), I kept getting a message along the lines of
"target didn't report max-download-size
sending 'boot' (x KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.123s"
Although even though despite always getting a message like this, I was able to somehow get root successfully one time. I decided to unroot and try to duplicate the root result but to no avail. Also got that annoying "internal problem with your device" message and followed @topjohnwu's tutorial only to get the "target didn't report max-download-size...FAILED (remote: Requested download dize is more than max allowed)" message again.
My laptop is currently running Manjaro (based on Arch Linux) but I can't imagine it being the reason I keep getting that "target didin't report max-download-size" message.

ilal2ielli said:
Have you tried a different cable yet?
Click to expand...
Click to collapse
Unfortunately I only have one USB-A to USB-C cable (a Sony one).

equlizer said:
did you unlock the critical partition as well? Maybe that's the problem?
Click to expand...
Click to collapse
I've tried numerous times and it always gave me a fail message or acknowledgement that my phone was already unlocked I'm giving up until I see a more streamlined answer to this potential problem

Make sure you adb/fastboot is up to date, it has caused many headaches for people trying to use older versions.

Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going

anthony.moua95 said:
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
Click to expand...
Click to collapse
I'd say try to get another cable ASAP, especially if anything else you do doesn't work.
When I first was attempting to unlock my bootloader, nothing worked when I was using third-party cables.
Luckily, my laptop had a USB-C port, so I was able to use the stock USB-C cable and I haven't had any problems since.

trim81 said:
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
Click to expand...
Click to collapse
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:

Badger50 said:
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Click to expand...
Click to collapse
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.

trim81 said:
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
Click to expand...
Click to collapse
Ok cool, that's the only way I know how to do it as well. Cool beans, thanks bro :good:

Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it

cavolo said:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
Click to expand...
Click to collapse
Dude, if that's the answer, which it probably is, I'm gonna pull my hair out. Been trying everything I can to these folks out. And it's a flippin 8 dollar cable! Oh well, live and learn

I know tou probably did this already but I did not see it posted.
You did enable developer settings and enable oem unlock in developer settings?

Is there a solution to this issue? I have followed every set of directions I can find on XDA and beyond, wiped and wiped, locked and unlocked my phone a few different times. Tried different cables and different ports on my computer. No matter what I do, I am stuck at the "downloading boot" after trying to flash TWRP. Thanks in advance for any help.

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
Note - download twrp according to your phone security patch
1 . Download twrp-3.4.0-0-DDV_sprout_sprout.img copy in one folder
2. connect phone to pc boot your phone to bootloader mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot flash boot twrp-3.4.0-0-DDV_sprout.img
6. now get back to phone select recovery mode and now your phone boots in to twrp
7. now flash magisk or what ever your wish and press reboot system
bugs- none
well still you people can flash magisk.zip using sideload
just download magisk.zip & and click on sideload in twrp and open cmd and type adb sideload magisk.zip and after completion reboot system
Download Android 9 Twrp-3.3.1-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
​For More Information About Status Official Click Here​
​Join Nokia 7.2 Community​
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.2
Contributors
Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Source Code: https://github.com/omnirom/android_bootable_recovery
Device Source Code: https://github.com/TeamWin/android_device_nokia_DDV_sprout.git
Version Information
Status: beta
Created 2019-11-07
Last Updated 2020-06-25

Thanx.
Thanx for the effort and hope this phone will have good Custom
ROMs too

nuwanmw1988 said:
Thanx for the effort and hope this phone will have good Custom
ROMs too
Click to expand...
Click to collapse
Soon roms will be out

Does anyone have a stock recovery.img? In case that i will install OTA.

pinh3ad said:
Does anyone have a stock recovery.img? In case that i will install OTA.
Click to expand...
Click to collapse
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.

KohGeek said:
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.
Click to expand...
Click to collapse
The reason behind this we need a proper kernel sources from hmd Nokia . For that reason i used prebuilt kernel from stock rom and that rom is based on August so here August kernel & wifi modules signed with different keys and September kernel & wifi modules signed with different keys so here August kernel and September wifi modules signatures are different that's why wifi got broken

Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s

JoSoFer said:
Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
You have to flash twrp According to your security patch
For example September security patch download from 2019-09-19
For example August security patch download from
2019-08-19
And also if you want to boot back to twrp after flashing twrp and rebooting in to system
Just power off your phone and reboot to download mode and press reboot to recovery now you will boot in to twrp.
If you know what exactly you are doing you won't get confused just follow steps
If you still can't able to boot then you are unlucky because all of the people who viewed this thread successfully booted as well

Hi, I tried to flash this TWRP 2 times, and in all cases the touch does not work. Nokia 7.2 TA-1196. Any ideas how to fix this?

Which TWRP to Flash?
i have model TA-1193 on november 5 security patch, os version is 00ww_1_200_SP01.
was able to successfully un lock bootloader today. Which TWRP should i flash? there are multiple images in https://sourceforge.net/projects/ddv-sprout/files/TWRP/PIE/2019-11-05/\
tried Flashing all the recoveries from the folder, wifi doesnt work.! any help how to fix it?

I wiped my SD card, now instead of 256GB it shows as 16MB, any ideas? Crap, now when i boot into Recovery, i just get a dead robot and 'No Command".

Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)

CGarz said:
Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)
Click to expand...
Click to collapse
Well even I appreciate the work of this guy, you have to be careful. 1st - if you on Nokia 7.2 keep in mind that all his stuff based not on Nokia 7.2 sources because Nokia not released any souses yet. 2nd - he warned about it if read carefully. 3rd - all his ROMs for Nokia 7.2 have same trouble as LineageOS and treble. I prefer stay on stock with MicroG, at least all stuff works. 4th - for internal access from twrp you have flash DisableForceEncryption_Treble. Don't use Disable_Dm-Verity_ForceEncrypt_10.20.2019 it has bugs and not works. Just look for same name as I give Disable_Forse_Encryption_Treble. Careful with, it removes encryption but leaves verity in tact. Read all warning about using it, google in help. After reboot in twrp you would read internal and data. Hope that helps. Also check version twrp that he uploading, they base on security patch and I guess it have to match your system. But I'm using fine 11/28 on august security patch.
O, and one more thing - don't relay completely on twrp backups, they not working in 100%, just try restore before. Good luck.

Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.

CGarz said:
Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.
Click to expand...
Click to collapse
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.

boomo15 said:
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.
Click to expand...
Click to collapse
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.

Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.

VictorAcid said:
Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.
Click to expand...
Click to collapse
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
CGarz said:
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.
Click to expand...
Click to collapse
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.

boomo15 said:
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.
Click to expand...
Click to collapse
Okay lets not try it this is my main phone :/

I tried to build TWRP myself using your device tree and the latest stock kernel that I extracted from the OTA. The result was a working wifi module, but whenever I set a device unlock PIN, entering the correct PIN doesn't unlock the device. It just says "Wrong PIN". Do you have any thoughts about what could be happening? I'm at a loss.