[RECOVERY][flounder] TWRP 3.1.1-0 touch recovery [2017-05-19]

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,694
263
New York
Restoring an old vendor causes bootloop anyways. No need to ever do it. Once you update it, you never want to go backwards.
I think it has the option because it works on some devices.
I have zero issues restoring vendor AND never once have I had a bootloop because of it.. sooo yeaaaaaah :laugh:
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
I have zero issues restoring vendor AND never once have I had a bootloop because of it.. sooo yeaaaaaah :laugh:
It's temp bootlooped my n9 every time. Restored it on accident once, on purpose twice. So, different experience. Laugh all you want, facts are facts.
Has anyone else successfully restored vendor on n9? (Curiosity)
Maybe on a different device it works?
I haven't tried since lollipop though.
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,694
263
New York
It's temp bootlooped my n9 every time. Restored it on accident once, on purpose twice. So, different experience. Laugh all you want, facts are facts.
Has anyone else successfully restored vendor on n9? (Curiosity)
Maybe on a different device it works?
I haven't tried since lollipop though.
To be fair, just because something is happening to you -- doesn't make it a fact. You're probably having bootloops because whatever vendor you have backed up is older than what is required to run whatever ROM you're on. THAT is what can cause bootloops, but that has nothing to do with TWRP.

Don't spread misinformation because you aren't doing anyone favors here by doing so.
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
To be fair, just because something is happening to you -- doesn't make it a fact. You're probably having bootloops because whatever vendor you have backed up is older than what is required to run whatever ROM you're on. THAT is what can cause bootloops, but that has nothing to do with TWRP.

Don't spread misinformation because you aren't doing anyone favors here by doing so.
I didn't mean to imply it was something wrong with twrp, I meant the n9 doesn't like restoring it. Restoring all partitions, including vendor, won't boot. Restoring everything except vendor, boots fine.
Haven't tried restoring vendor along with flashing the matching bootloader.
Never really had a reason to restore an old vendor anyways.
And not spreading misinformation at all, sharing experiences. I've spoken to many people, none of whom could successfully restore vendor and bootup. I tried all this when I first got the nexus 9 and was curious about vendor.
 
Last edited:

Gold Ribbed

Senior Member
Sep 28, 2014
357
71
58
OK so not a big deal but on 2.8.7.1 I can save but TWRP cannot mount Vendor and so fails to restore.
Flashed 2 ROMS and had no issues. Now on AICP.
 

jskup

Senior Member
Sep 30, 2008
77
23
28
Anything we can do to help with a 3.0.0 build? Gerritt and Jenkins both seem to be having a lot of issues on flounder these days
 

jskup

Senior Member
Sep 30, 2008
77
23
28
Thanks much, I must have missed it. I appreciate the work and responsiveness.

Edited: Found it. I must have posted before it was up there.
 
Last edited:

DanteGR

Senior Member
Dec 14, 2010
3,771
1,389
253
Thessaloniki
www.facebook.com
Hello all.
So I just moved to v3 and tried to take a nandroid which seemed to complete ok despite saying at the end "unable to unmount system - device or resource busy".
Anyway, I then tried to wipe cache, dalvik and system and the exact same message as above came up and this time the system wipe could not be completed.
I cannot also flash anything at the moment the above error.
Tried googling it but to no avail.
Any ideas anyone?
Thank you in advance :)
 
Last edited:

maelfilk

Senior Member
Nov 17, 2010
830
119
0
Novosibirsk
Hello all.
So I just moved to v3 and tried to take a nandroid which seemed to complete ok despite saying at the end "unable to unmount system - device or resource busy".
Anyway, I then tried to wipe cache, dalvik and system and the exact same message as above came up and this time the system wipe could not be completed.
I cannot also flash anything at the moment the above error.
Tried googling it but to no avail.
Any ideas anyone?
Thank you in advance :)
You could try and got to previous twrp version. I suppose you rebooted recovery several times and it didn't help? Did you check/uncheck "mount system"?
 
  • Like
Reactions: DanteGR

fhem

Senior Member
Nov 4, 2013
880
1,573
93
Pittsburgh, PA
Hello all.
So I just moved to v3 and tried to take a nandroid which seemed to complete ok despite saying at the end "unable to unmount system - device or resource busy".
Anyway, I then tried to wipe cache, dalvik and system and the exact same message as above came up and this time the system wipe could not be completed.
I cannot also flash anything at the moment the above error.
Tried googling it but to no avail.
Any ideas anyone?
Thank you in advance :)
@Dees_Troy I am having the same issue w/ v3. It appears that when making or restoring a backup the system is not being unmounted. It requires rebooting back into twrp to unmount system.

Thanks for your hard work and continued support. If you need me to do any testing please ask.
Thanks again.
 
  • Like
Reactions: DanteGR

cpstar

Member
Aug 9, 2011
13
0
0
Use Flounder recovery. The trees are unified under Flounder. The only difference is your vendor.img
I've been using flounder version in my nexus 9 LTE, all work fine but only one thing. That's when using TWRP to make OTAs, it will get an error message about this is a flounder devices but flouder_lte are needed.
The log is here
Code:
I:operation_start: 'OpenRecoveryScript'
Running Recovery Commands
I:command is: 'install'
I:value is: '@/cache/recovery/block.map'
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
I:Installing mapped zip file '/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: mmapped 260 ranges
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
sysutil: mmapped 260 ranges
[B]script aborted: This package is for "flounder_lte" devices; this is a "flounder".[/B]
[B]This package is for "flounder_lte" devices; this is a "flounder".[/B]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file
I don't know whether I did the right thing and flashed the right recovery image. https://twrp.me/devices/htcnexus9.html?
 

DanteGR

Senior Member
Dec 14, 2010
3,771
1,389
253
Thessaloniki
www.facebook.com
@Dees_Troy I am having the same issue w/ v3. It appears that when making or restoring a backup the system is not being unmounted. It requires rebooting back into twrp to unmount system.

Thanks for your hard work and continued support. If you need me to do any testing please ask.
Thanks again.
My problem was also in wiping system. Same error occurred

Swiftkeyed from my 1+2 A2003
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone